If you just need a flight track, you can use the igc gps track, but i guess it's lacking some of the properties you want
- Code: Select all
fgfs --igc=file,out,1,OutputFile.igc
Using the generic protocol to write a file seems better, just
write the properties you need in a protocol file and fly ...
- Code: Select all
--generic=file,out,1,/tmp/data.xml,myproto
I don't know which logging frequency you want, but i think you can log as fast as your screen fps with the generic protocol, and maybe at the fdm frequency using jsbsim logging, if using JSBSim (usually it's 120hz but sometime it's better to change this frequency to a multiple of the screen refresh rate if FG can maintain the fps)
About the timestamp, you can consider using "sim/time/mp-clock-sec" which is the utc time with the hour truncated at startup. Using PC with NTP give good result over mp, and you'll have a "time unity" for your logs (modulo 3600s depending when you started the FG sessions).
the sim time is fine for a standalone FG, but can be prone to pauses if frame time is too big.
jano