TestFlightFailure_LockGimbal has no effect

[Starstrider42]

While it appears as a failure, TestFlightFailure_LockGimbal does not actually impair an engine's functionality in any way.

The bug can be reproduced in KSP 1.2.2, with ModuleManager 2.7.6, TestFlight 1.8.0.1, and this config file instead of the default stock ones. I started a sandbox game, cheated the Orbiter 1A into orbit, and disabled the reaction wheels in the command pod and the inline stabilizer (located between the three engine outriggers). I used the yaw/pitch/roll keys to confirm that the engine gimbals responded as expected.

I burned the engines at low thrust until one of them failed. Using the yaw/pitch/roll keys still moved all three nozzles, including the one that was allegedly broken. Likewise, I could continue to maneuver the ship using only thrust vectoring even if I waited until all three engines were broken.

For comparison, TestFlightFailure_GimbalCenter does work correctly, so something is different about how these two failures are handled.

[anxcon]

unrelated to this specific case - but easier tests can be done with changing TestFlightReliability module out for TestFlightReliability_TestFail module, adds a button to part right click menu to force failures on-demand