20,741
edits
(Created page with "{{Stub}} {{See also|Howto:Understand console output}} To show the console it is now necessary to start from the command line. The full method that I use is as follows. I wi...") |
No edit summary |
||
Line 16: | Line 16: | ||
All of the flightgear and fgrun log messages will now apear in the "DOS" window. | All of the flightgear and fgrun log messages will now apear in the "DOS" window. | ||
The reason for changing to this system and getting rid of the old --console option, was to make the error reporting (STDERR) work properly. <ref>{{cite web | The reason for changing to this system and getting rid of the old --console option, was to make the error reporting (STDERR) work properly. <ref>{{cite web | ||
|url = https://forum.flightgear.org/viewtopic.php?p=293571#p293571 | |url = https://forum.flightgear.org/viewtopic.php?p=293571#p293571 | ||
Line 25: | Line 26: | ||
}}</ref> | }}</ref> | ||
The reason is that a console window opened by an application (e.g. running fgfs --console) is not the same as a native windows command window from which an application (e.g. fgfs) is started typing a command at the prompt.. It was discovered that error reports were not being sent to a console window that was opened with the --console option. Also it was not possible to pipe output to a file from the window that was opened by the fgfs --console method. For historical reasons the fgfs log file is not (as many folk believe) the same as the log printed in the console window.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=293574#p293574 | |||
|title = <nowiki> Re: Running FlightGear with console showing </nowiki> | |||
|author = <nowiki> Alant </nowiki> | |||
|date = Sep 3rd, 2016 | |||
|added = Sep 3rd, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
{{Appendix}} | {{Appendix}} |