Re: [Flightgear-devel] 3D Model Configuration Changes

2002-02-26 Thread Wolfram Kuss
What do you suggest that I do to the models on my homepage? Is it somehow possible to create a model that works with the old and the new FGFS version? I fear you will tell me to use XML instead of Python? Maybe use both and generate a XML on the fly by Python? Can I easily find out what version

Re: [Flightgear-devel] 3D Model Configuration Changes

2002-02-26 Thread Wolfram Kuss
David wrote: Wolfram Kuss writes: What do you suggest that I do to the models on my homepage? If I recall correctly, the models on your page are already oriented correctly; if so, then they should continue to work fine. You don't need to write any XML unless you need to reorient or animate

Re: [Flightgear-devel] 3D Model Configuration Changes

2002-02-26 Thread David Megginson
Wolfram Kuss writes: The Python script sets these parameters: /sim/model/path /sim/model/r-rotation /sim/model/z-offset The last two changed quite a few months ago, to z-offset-meters and pitch|roll|heading-offset-deg. They will be that way in 0.7.9, at least. All the best, David

[Flightgear-devel] 3D Model Configuration Changes

2002-02-25 Thread David Megginson
I've just made some changes to how 3D models are configured. The following properties are no longer used: /sim/model/heading-offset-deg /sim/model/pitch-offset-deg /sim/model/roll-offset-deg /sim/model/x-offset-m /sim/model/y-offset-m /sim/model/z-offset-m Instead, if the

Re: [Flightgear-devel] 3D Model Configuration Changes

2002-02-25 Thread Jim Wilson
David Megginson [EMAIL PROTECTED] said: Instead, if the /sim/model/path property points to a file ending with .xml, the FGAircraftModel class reads a property file at that location to get information about the 3D model. Initially, the following properties are recognized: /path