2,733
edits
No edit summary |
Red Leader (talk | contribs) No edit summary |
||
Line 2: | Line 2: | ||
{{See also|Howto:Understand console output}} | {{See also|Howto:Understand console output}} | ||
In FlightGear 2016.3, the console and <code>--console</code> option were removed. However, some users may still want the console to debug errors, etc. This article will show how to '''show the FlightGear console on Windows'''. | |||
Running flightgear from an already open command window has one small advantage - when flightgear exits (or crashes) the command window, complete with the log messages, stays open. Running from a batch file (unless one puts a "press any button to continue" trap at the end of the batch file) closes the window, and you don´t know what lead to the crash.<ref>{{cite web | Running flightgear from an already open command window has one small advantage - when flightgear exits (or crashes) the command window, complete with the log messages, stays open. Running from a batch file (unless one puts a "press any button to continue" trap at the end of the batch file) closes the window, and you don´t know what lead to the crash.<ref>{{cite web |