Merlin negative G cutout too quick?

Originally Posted by klem

The chart I made is based on acceleration measurements taken from the game and are effectively a G-meter (accelerometer):
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 0); is acceleration in the fore/aft plane
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 1); is acceleration in the lateral plane
cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2); is acceleration in the vertical plane, renamed G-force on the chart.

At the moment of the 0.5G cut there were very small fore/aft and lateral g-forces of -0.04g and +0.02g respectively (slight speed reduction and slight sideslip). Its close enough to indicate that the cutout occurs well before 0.1G.

Readings were taken every 300 mSecs. Unfortunately we cannot add instruments to the cockpit so we can only draw data from the game parameters.

Ok that already helps a lot. But I still do not know which point the acceleration provided by cur_Plane.getParameter(part.ParameterTypes.Z_Overl oad, 2) corresponds to (I assume z-axis here is body axis not lift-axis which should have to be confirmed by devs too). Does it really correspond to the acceleration measured by the g-meter in the flight tests that stated a 0.1g threshold for the second stage cut-out? It is important to make sure that we do not compare apples with pears.