Re: [Flightgear-devel] 3D Model Configuration Changes
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 of FGFS the user has? Bye bye, Wolfram. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3D Model Configuration Changes
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 the models. The Python script sets these parameters: /sim/model/path /sim/model/r-rotation /sim/model/z-offset What does the file version say for the current CVS version? If it says 0.8.0 or 0.7.10 or 0.7.9a or something like that, then I could update my script so that my planes work with 0.7.9 and the current CVS version. All the best, David Bye bye, Wolfram. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3D Model Configuration Changes
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 -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] 3D Model Configuration Changes
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 /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 The path to the model, relative to the XML file (not FG_ROOT). /offsets/heading-deg The heading rotation for the model, in degrees. /offsets/pitch-degThe pitch rotation for the model, in degrees. /offsets/roll-deg The roll rotation for the model, in degrees. /offsets/x-m The x-axis transformation, in meters. /offsets/y-m The y-axis transformation, in meters. /offsets/z-m The z-axis transformation, in meters. Here's an example for my C172 model: ?xml version=1.0? PropertyList pathc172-dpm.ac/path offsets heading-deg270/heading-deg z-m-1/z-m /offsets /PropertyList This uses the file c172-dpm.ac in the same directory as the 3D model, rotates the model 270 degrees around the z-axis (the heading rotates around z=0), and lowers it 1 meter along the z-axis. Very, very soon, the file will also contain information on animating parts of the model (propellers, ailerons, flaps, etc.) based on property values. This will work with *any* 3D format that allows objects inside the 3D model to be named (including ssg, VRML, AC3D, and, I think, MDL formats). All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 3D Model Configuration Changes
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 The path to the model, relative to the XML file (not FG_ROOT). /offsets/heading-deg The heading rotation for the model, in degrees. /offsets/pitch-degThe pitch rotation for the model, in degrees. /offsets/roll-deg The roll rotation for the model, in degrees. /offsets/x-m The x-axis transformation, in meters. /offsets/y-m The y-axis transformation, in meters. /offsets/z-m The z-axis transformation, in meters. Great improvement! One thing I noticed as soon as the c172 model went in was that the offsets affected every model that didn't have offsets defined in the aircraft-set.xml file, simply because they were included in the c172-set.xml file that always gets processed by default, even if another aircraft is selected. Does this address that issue? If I switch to a different model in my command line will the offsets for the default model go away? Another question that came to mind (and I apologize in advance if it's a stupid one!): Is it possible to eliminate the requirement of offset values with models built for the base package distribution...ie can we convert all the vertices in the *.ac files so that it isn't necessary to use them? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
