David Culp wrote:What if we even have flight model in an archive from now on? Also, do we have any structures prepared for the skins of the aircraft (so each aircraft could have sets of skins in .xml format pointing to the .rgb files (this would be in model file wrapper). Of course mapping coords would stay the same, only the texture would differ). IMO, the complete structure for my J-22 model should look like this: $FG_ROOT/Aircraft/j22.tar.gz: /j22 --/j22-set.xml --/Model // The aircraft models and textures - skins ----/j22.xml ----/j22.ac // Currently, ac3d file format. Maybe some other (even our own?) some day ----/pilot.rgb ----/gear.rgb ----/skin-green-gray-wing_above.rgb ----/skin-green-gray-wing_under.rgb ----/skin-green-gray-tail-yugo.rgb ----/skin-green-gray-tail-roman.rgb ----/skin-green-gray-main.rgb ----/skin-arctic-wing_above.rgb ----/skin-arctic-wing_under.rgb ----/skin-arctic-tail-yugo.rgb ----/skin-arctic-tail-roman.rgb ----/skin-arctic-main.rgb --/FDM ----/j22-yasim.xml // Flight model file in J22 package from now on --/HUDs ----/j22-generic.xml --/Sounds ----/j22-sounds.xml // Wrapper file for the sounds ----/button1.wav ----/button2.wav ----/knot1.wav ----/geardn.wav ----/gearup.wav You could place the j22.tar.gz file in the /Aircraft folder, or you could extract the contents to the /Aircraft/j22 folder (the same name folder). FG should automaticly find the aircrafts then. Just some ideas. - Matevz |
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
