On 2/28/2011 3:46 PM, Robi wrote:
unless using it just to get/set configuration,
in which case, speed should hardly seem an issue.
Right, I'm using it that way, I get/set properties changing them in
real time (I whish!).
...
My conclusion being, fgfs cannot answer back quicker than this: 20Hz.
I suspect that is by design, so as to not interfere with the simulation
itself.
This is quite poor for a quasi-realtime hardware interface (which is
in my intention).
I suggest you discuss your use case on a FlightGear mailing list
(mirrored on gmane as newsgroups) or forum.
--
Terry Jan Reedy
--
http://mail.python.org/mailman/listinfo/python-list
