Before we get too far down this path, there's one major wrench I needWhat if we create "generic" folder for texture, sound, HUD, FDM and whatever part of the aircraft and include it in the base package. The aircraft model would have only 2 options then: read data from its own package, or read the generic ones (something like this already exists for HUDs and electrical systems AFAIK).
to throw into the gearing. Consider that much/most/all of our model
loading is done through plib's loaders. Some model formats allow you
to reference models in other files (kind of like #includes.) Just
about all 3d model formats allow you to reference textures. Whatever
scheme we come up with would also have to modify or overload all of
plib's model and texture loading functions with the additional
functionality they would need to be able to also read from our archive
format. I'm not sure that would be an easy or straightforward thing
to do.
I don't know how often will we use cross-package textures or other references anyway? If there are some very similar aircrafts or vehicles, we should join them into one package then (for e.g. F16 A, B, C and D variants should be all joined into one package, although they use different loadouts, models, textures, flight models and even some sounds).
Or, we have a central list of the aircrafts and their data. This would build up a major property tree (containing pointers to all of the files of all the aircrafts). Then each aircraft could easily access to other packages by naming the data it needs (some unique names for every texture, sounds, HUD etc.). FG would look into this property tree and load this element from the corresponding package then.
- Matevz
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
