Anyway, back on topic. Please devs consider these changes in your next update, after all realism is the main purpose of a simulator, especially when it’s relatively easy to implement . You can ignore the debated bits, like fpm change when gears down (which I’m still pretty sure about), until more research is done into them.
Latest posts made by SCU316
-
RE: A few more HUD inaccuracies.
-
RE: A few more HUD inaccuracies.
I’m pretty sure the fifth thing you mention (FPM snapping to gun cross) is not tied to NWS engage/disengage but to a certain (ground?) speed being sensed by the INS/EGI. Not sure what the exact value is though, might be different for different blocks/tapes
Interesting note, seems pretty much like how it’s modelled in DCS’s A-10C. You’re probably right about that.
-
RE: A few more HUD inaccuracies.
Yes he does pull it up to 4, but that’s after the gears are down and locked & the airspeed drops quite a bit resulting in flight path decline which I’m not denying… I’m only stating the 2ish seconds period when the FPM rises, which isn’t modelled in game.
-
RE: A few more HUD inaccuracies.
Heya Blu3wolf, still in the argumentative spirit eh :P. Well lets just say I am as well, we’re just not seeing this the same way, hehe.
In the dutch vid the plane was slightly above 5° (about 6°’s), when pitching down he got down to about 1° or slightly above. 2nd vid it kinda doesn’t move, but the pilot pitches down a couple of degrees. 3rd it can’t be a coincidence in the 3-4+ times he lowers the gears each time the fpm goes up. I have loads of other HUD tapes that show this behaviour, those 3 were just an example. -
RE: A few more HUD inaccuracies.
Bump! I’ve updated the post to make it more readable and more organised and also added one more point. Congratulations everyone and BMS team on the deal with Tommo! :).
I’m a bit sad my notes on the HUD were not implemented in the update though I hope you guys do consider these on your to do list. -
RE: 4.33.1 will release shortly: what you need to know and how to be prepared
Congratulations on the deal. I’d like to comment on the update & fixes part of this announcement, please don’t forget about these: https://www.benchmarksims.org/forum/showthread.php?23825-A-few-more-HUD-inaccuracies&p=341737#post341737
-
RE: A few more HUD inaccuracies.
I’m describing the brief state mainly as well :P. The steady state needs more studies/calculations than simply noticing behaviour on HUD tapes, which would need a lot more time and more knowledge than I have obviously ;).
Summary: Pilot lowers the gear handle: Velocity Vector Rises up in a matter of one or two seconds. -
RE: A few more HUD inaccuracies.
just watch the videos at the times I linked to see what I mean: gears down above 225 or so knots, the FPM/Meatball/VV rises up.
-
RE: A few more HUD inaccuracies.
Well by nose I mean the movement of the nose of the aircraft…
If you see the nose raise during LG extension below 240 knots, that proves that the change in nose position is not due to the TEFs, as they dont get extended any further when the gear are extended below 240 knots.Nope, I meant, and always have, that the FPM position changes with gears down, and not the nose ;).
-
RE: A few more HUD inaccuracies.
I’m now getting confused by what you mean by “nose”. If by nose you mean the FPM and not the Gun cross, then I don’t understand how the FPM moves due to FLCS programming & not due to the actual change in the Flight Path of the jet.
(Minutes, Seconds linked), which I’m assuming is an American F-16, but I have no clue if it’s CCIP upgraded.
Also the behaviour in the Dutch jet also happens in this one