I'm currently trying to 'reverse engineer' the "native-ctrls" wire format by writing to a file:
--native-ctrls=file,out,10,Bla This is quite interesting, but far from being 'readable' :-) Aside it crashes 'fgfs' when combined with other command line switches. But the latter is not the issue here. My first try to get a clue about the wire format was by reading lots of source code, but as I'm not fluent at C++ this didn't deliver the desired result. Now I thought I'd write to a file and have a look at what's going on there. This is not human readable (at least not for me). Is there hope to find a human readable (except from RTSL) documentation on what FlightGear expects on a socket, file (pipe) or serial port for being controlled externally ? Also I'm not quite shure if I can confine on feeding only the 'usual' manual controls into FlightGear to control the flight ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
