I've got an aircraft that will have about 6 variations on the external model, and two variations on the VC model. So I say to myself "Isn't it great that in FSX we have separate models for the exterior and VC - I don't need 6 redundant copies of the VC; I just need the two." But in looking at the docs and some existing aircraft, it looks as though I'll have to have a folder for each of the six variations, each one with a repeat copy of the VC."Well, at least texturing will be more efficient", I'm thinking. The VC textures can all go in a generic "Texture" folder, and don't need to be repeated. Except that the military variations have orange seats in the cockpit, and the civillian ones have more design-friendly blue seats. So any texture that has seats in it will have to be copied into every texture folder that requires that seat color.So, doing the math, I calculate that the approximate time it will take someone to download the project is...Forever! Am I missing a trick here, or is the process really this inefficient?-Mick

Er, that's not quite correct...As long as your textures are DDS/DXT format, use the texture.cfg file to provide "fallback" paths to the actual folders where the common textures are located.

For model...You can place mdl and cfg files in different folders and use path with model filename in model.cfg file.For example, place all mdl files (VC_1.mdl, VC_2.mdl, exterior_1.mdl, etc.) into '..aircraftnamemodels', and cfg files into '..aircraftnamemodel.1model.cfg', '..aircraftnamemodel.2model.cfg', etc.In first model.cfg:normal=../models/exterior_1interior=../models/VC_1(same for other model.cfg's)L.

It works! I never would have figured that out without you guys...makes my brain hurt just thinking about it. Thanks!

>It works! I never would have figured that out without you>guys...makes my brain hurt just thinking about it. Thanks!Ya think! Even after nearly five years at this I manage to learn at least one "new thing" each day... ;)