On 21 Sep 2011, at 11:12, Melchior FRANZ wrote: > > <sim> > <aircraft-data> > <path>/sim/dimensions/radius-m</path> > <path>/sim/dimensions/parkpos-offset-m</path> > <path>/sim/aircraft-class</path> > </aircraft-data> > </sim> > Alright succes!!! Adding this section did the trick of saving aircraft-class and aircraft-operator properties, after they were were changed by the livery select mechanism.
But, then my trouble wasn't over yet: It turned out the data from fghome/aircraft-data/[aircraft].xml haven't been processed yet, at the time fgInitialPosition is called. But it looks like I can work around this by prefetching this file. reading it into a local property tree and fetching the data from there. The code needs some more cleaning up, and I have two additional questions: 1). Is there a 1 to 1 correspondence between the value of the /sim/aircraft property and the name of the xml file where aircraft specific properties will be saved in? 2). Is there a command line option to specifically tell FlightGear which livery should be loaded? cheers, Durk P.S., Muchos gracias to Melchior and Torsten for pointing me in the right direction! D. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
