Generic Protocol Output limit

[joef1993]

I'm just curious as to whether anyone knows the limit to the number of variables that can be output via generic protocol? Through trial and error I'm currently finding that FG will start with an generic protocol XML containing around 1700 but anymore and it wont start or will crash shortly after. I've had a search but could not find anything documented.

[Johan G]

That is a lot of properties to log. Is there something in particular you need all of those logged for?

I am not aware whether or not there is a limit or some throttling involved.

If you would not mind reading source code, I have tried to link to the relevant header and source files at the end of the FlightGear wiki article Generic protocol (perm).

[Hooray]

Given that number of variables, it would make more sense to consider using a binary, and hard-coded, protocol - e.g. refer to $FG_SRC/Network
Apart from that, there's apparently ongoing work to provide a web socket based wrapper to retrieve a whole property tree according to this: https://sourceforge.net/p/flightgear/fl ... d5cd1f422/

Note that regardless of what you end up using, most I/O is taking place in the fg main loop - thus, even if you find that you are able to send hundreds of properties per frame, doing so will inevitably affect your framerate, too.

In general, I guess it would make more sense to tell us exactly what you are doing - for instance, usually, it might be much better to selectively send properties, e.g. only if they've been updated - see the telnet subscribe/unsubscribe commands for example. Those would be easy to re-implement on top of a binary UDP based protocol to implement a simple PUB/SUB mechanism.