20,741
edits
No edit summary |
No edit summary |
||
Line 36: | Line 36: | ||
}}</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 <code>--console</code> 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 | 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 <code>--console</code> method. For historical reasons the [[Fgfs.log|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 | |url = https://forum.flightgear.org/viewtopic.php?p=293574#p293574 | ||
|title = <nowiki> Re: Running FlightGear with console showing </nowiki> | |title = <nowiki> Re: Running FlightGear with console showing </nowiki> |