Inaccurate G readings on landing

[Subdartha]

Please see the real hard landing result in your Inspector:

I think we will both agree that such negative FPS cannot have just 1.21 G acceleration.
The same landing registered by OnAir:

G is 3.56. I believe it's much closer to real, given how badly I dealt with the plane here.

Something's not quite right...

[mracko]

Thanks for the feedback. I've also seen similar inaccuracies with G forces like you've experienced. This tool currently uses the Python SimConnect library to get G force readings. There can be several reasons for the G force inaccuracies including - from inaccurate split-second G force calculation in MSFS to slow Python SimConnect readings. I've done several tests including slowing the MSFS simulation rate down, but the G force readings were inconsistent. I've also looked at Vertical Acceleration Numbers during landings and they were equally inaccurate.

I don't know what G force numbers OnAir uses. It could be SimConnect or it could be their own calculation. I'll be looking into this bug this week and let you know as soon as I have a solution. The idea so far is to make a custom G force calculation based on vertical speed at touchdown that would be used if the SimConnect reading is off.

[Subdartha]

Awesome, looking forward. :)
Also (if you have any difference in the data provided by sim) the usual G-s registered by real planes are the G-s around the mass center with average load. Dunno though if the sim gives you different values; but maybe you are only picking the value somewhere around the nose and OnAir - around the middle? Just a wild guess.