Custom Query (336 matches)

20:16:31: Traceback (most recent call last): 20:16:31: File "mlx\gui\flight.pyc", line 988, in _connectClicked 20:16:31: File "mlx\gui\flight.pyc", line 3166, in _connectSimulator 20:16:31: File "mlx\gui\gui.pyc", line 833, in connectSimulator 20:16:31: File "mlx\acft.pyc", line 61, in create 20:16:31: File "mlx\acft.pyc", line 608, in init 20:16:31: NameError: global name 'cflight' is not defined

For planes that have no strobe lights, the takeoff procedure should be handled differently:

If GS exceeds 50 knots during taxi, the state of the aircraft is saved. The GS checker does not produce an error message, but maintains the value of the highest speed achieved. If the stage is still TAXI after 20 seconds, or GS decreases below 50 knots, a "GS exceeded" fault will be logged with the highest speed.

In the latter case, the user can tick an "RTO" checkbox on the takoff page, in which case the error message(s) will be removed from the log and replaced by the text "RTO from XXX knots", where XXX is the highest speed achieved. If this happens while the stage is still TAXI, it will switch to RTO. The checkbox is active only if the contents of the Remarks window is not empty. If it becomes empty later on, the checkbox should become inactive and unmarked, and the "RTO from XXX knots" message should be replaced by the fault message about the highest GS speed.

If the plane becomes airborne (onTheGround becomes False) within 20 seconds of exceeding 50 knots, the stage is switched to TAKEOFF, and the takeoff data is logged using the state saved when exceeding 50 knots.

The RTO checkbox is inactive for planes that have a strobe light.

The original value should be remembered, and if it set back to that value before the timeout occurs for a change, it should be considered as if nothing had changed. Consider this as a general feature for the delayed change mixin, but an optional one.