Ff you could have one thing in the next update it would be…
-
It was already mentioned, but I would also like to have a debriefing screen for TEs
-
I would love to see basket and drogue refueling. With that, naval ops feels more authentic.
-
+1 for accurate Navy refueling simulation.
-
This post is deleted! -
Missile Cruisers (Ticonderoga) actually using cruise missiles Destroyers also. I always see in the 2D That Naval ships bombarded DPRK troops or battalions if close enough to the coast but If I go ingame I dont see them do the same. Much like If I used to task an AC-130 in 2D. They will go devestate the enemy in 2D but in 3D they take off and land immediately.
-
Better avionics simulations for non-US aircraft. Hands down.
-
Here something very needed; multiple tacan stations working on same channels, west coordinates working.
-
Better avionics simulations for non-US aircraft. Hands down.
Better avionics and systems sims for ALL non-F-16 aircraft - hands down! Or a defined/specified way for 3rd parties to produce such as add-ons or mods…that would really be great.
-
I finally realized 1 glaring need for improvement for the next chapter in FBMS,
AI needs improvement. I know it has been said that the AI would be difficult to address but one can wish for it. I am referring to AI at just about every level. A lot of work involved to be sure, but that is something I would like to see done. Maybe someday……
-
A wider variety of OPFOR modeling/cockpits.
-
Please line up the HUD in the non-viper cockpits. For instance altitude and speed is obscured by the frame in the f-18 HUD
-
UHF vs VHF distance modeling and clarity differences, haven’t noticed a difference in big mp events yet but maybe it is already modeled, but subtle.
-
My 2 cents would be to hold off on IFF for now and instead slowly start implementing Link 16. It would eventually cover some of the same ground but also add a huge amount of extra SA and functionality compared to IFF.
To fully implement it would still be a monstrous effort but you could do it piece by piece, e.g. Start with just implementing the ability to have your 4 ship on link and see their positions.
Of course I don’t know what real world documentation the team has available (any pilot guides past M3?) in order to get it right (nor do I know how they acquired it but that’s not my problem ).
I’m sure this discussion has been had before without me, I don’t want to offend anybody, just saying what I think would be hugely awesome in the long run
-
Its been discussed on this forum. In terms of getting it right, enough public documents exist to piece it together. Enough unclassified and leaked documents exist to do it correctly.
The problem is that to make it work, you have to alter the behavior of the AI. If you dont, its basically the same as flying with labels on. IRL, its a massive boon to SA - but its drawback is that its not perfect. IRL you still need to follow your ROEs.
Implementing TDL J without all its functionality would basically just be copying the current datalink, the IDM. You would have to do it right. To do it right, you would need to make changes to lots of things. Radar modeling, AWACS, the 2D map, the DTC save format, lots of things in lots of places. To do it right, and make it not just be the same functionally as turning labels on, would be even harder (but not I think, impossible. It could be done, it would just be a massive effort that would make changes everywhere).
-
1. Fully clickable F-16 cockpit (like the DCS A10 fidelity)
2. Better haze and ground haze
3. Terrain self shadows - e.g. mountains that produce shadows
4. Open Falcon - make the source code open source so the community can help in development.
5. Building / City autopen - includes roads models, lamp posts, trees, parks, buildings etc…
-
F-16 pit is full clickable…
-
F-16 pit is full clickable…
I mean all buttons/switches working (or at least pretend to be working)
-
1. Fully clickable F-16 cockpit (like the DCS A10 fidelity)
2. Better haze and ground haze
3. Terrain self shadows - e.g. mountains that produce shadows
4. Open Falcon - make the source code open source so the community can help in development.
5. Building / City autopen - includes roads models, lamp posts, trees, parks, buildings etc…
N°4 would mean the death of falcon 4
just in case you didnt notice we dont seek help… and when we need help we have no problem to find some…
-
1. Fully clickable F-16 cockpit (like the DCS A10 fidelity)
… make the source code open source so the community can help in development.I’m genuinely surprised this hasn’t happened by now. My body is ready… to submit pull requests.
-
Well, Im pretty sure that the leaked FF code is still on github. Fork that and PR away.
Not gonna be a lot of support for that after the stunt FFosc pulled, though.