Hi Melchior, Melchior FRANZ schrieb am 03.10.2007 11:38: > There's a TODO message in multiplaymgr.cxx that says: > > // A static map of protocol property id values to property paths, > // This should be extendable dynamically for every specific aircraft ... > > This static list grows and grows and that's becoming a problem. I > hardly ever take part in MP, because the amount of incoming data > is just too big for my connection. And that's no surprise when > even an UFO sends rotor angles, gear compression, tailhook angle, > etc. > > The actual MP code does not send all properties of the static list. It only sends those properties, which are existing at initializing of the MP-code. Thats why you need to define some properties within the -set.xml file to get them transferred over the net. Therefore the UFO is not sending rotor angles and so on. I think you find these properties in the property tree for every MP-aircraft, but they are set to a default value if not transferred. Therefore it does not hurt to enlarge the static list. But it is very unconformable.
Maik ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
