On 6 Jun 2013, at 11:10, Alan Teeder wrote:
> Has anything been changed in flightgear which could cause this to no longer
> work?
>
> The log file C:/Users/Alan/Appdata/Roaming/flightgear.org/fgfs.log
> unfortunately does not include the JSBSim output that I am interested in at
> the moment, even though I can see it flash past my eyes in the console window.
>
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.
There's a couple of fixes:
- figure out what I've (accidentally!) touched which breaks logging to
a pipe from the console. There is presumably some subtlety of stdout on
Windows, but since the output to the DOS box *is* working, I'm not sure what it
is.
- convert JSBSim *when running inside FG* to also log to the standard
backend.
(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)
I can look at the second part over the weekend, the first part (and in general,
improving how our log support interacts with the Visual Studio and DOS box) can
only be done by someone on Windows.
Regards,
James
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
