JD Fenech writes: > I know this is slightly off topic, but what is the possibility of having > a "one aircraft, one file" type configuration. The idea is basically to > put all of the requisite files for a particular aircraft into some kind > of archive file, such as a tarball, and then drop the archives into one > directory. Of course, each archive would need some kind of .info file > in it to tell fg what the aircraft name is, etc. Optimally, a command > line option would override any faults set in the archive.
The difficulty with a single file approach is in the handling of the aircraft 3d model and textures. We use plib and depend on it's model/texture loaders so we would have to rewrite all those plib loader routines to know about our special file conglomeration format ... and that would get really messy really fast. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
