Hello, I have a problem with autosave when using the same property in a variant/livery file and with the <aircraft-data>-mechanism.
Let's assume that in the livery.xml-File the properties A=3 and B=5 are set. During flight I manipulate property B to B=10. Property B is autosaved with the <aircraft-data>-mechanism in myaircraft-set.xml. After restart I get B=5 instead of B=10. I found out that in the aircraft-autosave-file ~/.fgfs/aircraft-data/myaircraft.xml property B AND the variant name are stored. I assume that at restart first the <aircraft-data> properties are read (B=10) and subsequent the variant name, which overwrites B with the value in the variant.xml-File. Question 1: Is there a possibility to define the order properties are read from the autosave-file at restart? I think in my case first read the variant name and then the properties would do the job. Question2: Alternatively I could live without storing the variant name in the autosave-file. Unfortunately I'm not able to do this with the archive/userarchive-method ( I set the following in all my variant-files: <sim> <model> <livery> <name type="string" archive="n">Default</name> </livery> <myaircraft> <name type="string" archive="n">Default</name> ). What's wrong with this? Do I have to do something else? Question 3: Maybe there is an other solution to my problem? Thanks in advance! Best regards D-NXKT ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
