Merlin negative G cutout too quick?

[von Brühl]

Originally Posted by trademe900

Why do I get no engine cut out at all? Some setting that I have somehow missed?

Make sure all relevant engine settings (CEM especially) are on.

[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.

[SEE]

Originally Posted by Blackdog_kt

Well, it seems more forgiving than IL2 to me, at least the engine doesn't completely turn off. ......

I actually like it quite a lot the way it's done in CoD. Between the individual aircraft quirks, the extra details and restrictions and the all-around higher level of challenge in all flyables.

+1