Merlin negative G cutout too quick?

[klem]

Originally Posted by 41Sqn_Banks

IIRC in the release version cut-out was at 0.5 G and was reduced to 0.1 G with a patch. Luthier stated these values.

There is way to much "feeling" in bugtracker issue. I think it should be possible to get the G force using a mission script to verify the values. It's possible to log the position (x, y, z), speed and the time, should be enough to calculate the G forces, shouldn't it?

Someone should collect the reference material to find out at which value the engine should cut. Someone else should test the implementation by doing flight test and calculate the G force.

Then we have something to compare and don't need to talk about feelings and opinions.

"Someone should collect the reference material to find out at which value the engine should cut."

That data is given (linked) in the original Tracker request.

"Someone else should test the implementation by doing flight test and calculate the G force."

That is precisely what the Bug Tracker entry asks the devs to do.

I don't want to offend you but did you read the Bug Tracker entry and Description?