* Jon S. Berndt -- Saturday 28 July 2007:
It was asked in the German fgfs forum[1] if it's possible to log
internal data to an XML file. Sure is! :-)
There are probably several ways within Flightgear to do this. If one is
interested in flight dynamics parameters you can also do this in
* Jon S. Berndt -- Saturday 28 July 2007:
[...] or to output to socket
To be fair: this is also something that the one from the German forum
asked for, and what the Nasal version doesn't do. Well, except if
don't mind abusing the system:
$ fgfs \
--prop:sim/sound/voices/enabled=1 \
But it doesn't look like this logs to an XML file, which is what that
user wanted, and what the Nasal file does. (See subject.) Also, I'm
not sure if he'd be happy about a JSBSim-only solution, which wouldn't
even cover half of our aircraft. :-}
m.
I was just mentioning another option,
* Melchior FRANZ -- Saturday 28 July 2007:
It was asked in the German fgfs forum[1] if it's possible
to log internal data to an XML file. Sure is! :-)
And now it's also possible to do via regular generic protocol.
Writing XML is a trivial thing (unlike readingparsing), but the
generic protocol
It was asked in the German fgfs forum[1] if it's possible
to log internal data to an XML file. Sure is! :-)
The attached file put into $FG_ROOT/Nasal/ starts logging
to /tmp/data.xml as soon as the FDM is up (one data set per
second) and stops when fgfs is closed. Because the 1 second
interval
It was asked in the German fgfs forum[1] if it's possible to log
internal data to an XML file. Sure is! :-)
There are probably several ways within Flightgear to do this. If one is
interested in flight dynamics parameters you can also do this in JSBSim in
the aircraft configuration file with an
6 matches
Mail list logo
