Startup log file

See also Commonly used debugging tools#fgfs.log.

This article is a stub. You can help the wiki by expanding it.

Note  In its current form, this section/article is largely based on quotes collected from various related discussions/channels (devel list, forum etc) using the Instant-Cquotes script. Wiki users and other contributors are encouraged to help rewrite/edit contents accordingly to help get rid of unnecessary quoting (i.e. while the wiki is not intended to be a collection of quotes, quotes are sometimes the best/easiest way to bootstrap new articles, while also providing a good way to link back to related discussions in the archives). While rewriting usually only entails changing first person speech to 3rd person. However, please try to retain references/links to the original discussion whenever possible.

Location in $FG_HOME

I was hoping the enhanced log support would be a step towards killing off the DOS-box for release builds in Windows, since it looks rather retro - and on the basis that we frequently want the log file after-the-fact, the file on disk seemed more useful — James Turner (2013-06-06). Re: [Flightgear-devel] Windows Log file pipe/redirect. (powered by Instant-Cquotes)

What's changed is the addition of that log file :) (Well, and the capability to show portions of the log in the GUI) I was unaware JSBSim output wasn't being captured there, but it makes sense since I'm only capturing SimGear log output, which JSBSim doesn't use. There is a mechanism to send other log streams to the same backend, including partial code to do this with OSG messages. — James Turner (2013-06-06). Re: [Flightgear-devel] Windows Log file pipe/redirect. (powered by Instant-Cquotes)