David Megginson <[EMAIL PROTECTED]> said: > Fortunately, it's much simpler than that, since Blender has built-in > Python scripting -- I just export the file to AC3D format from within > Blender using a 3rd-party export script, and the object names, texture > mappings, and material colours are preserved automatically. Usually, > however, I have to do about 30 seconds of post-processing in a text > editor: > > 1. Rearrange some objects (like the propeller disk) to work around > plib's alpha-handling limitations. > > 2. Manually change the emissive properties for coloured materials > (like nav lights), since the current AC3D export script doesn't > save them (fixing that would take about 15 minutes of Python > coding, but I'm lazy). >
Ok good, for some reason I thought the object names weren't getting carried through the conversion script. It is still a bit kludy though. Popping a complex model into a text editor can involve a little more than 30 seconds. It certainly isn't difficult though. My main concern is that if we use Blender, then files that will read into Blender should be maintained CVS as source data. We might even want to maintain our own version of the python script and at least Best, Jim _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
