On Sunday 10 November 2002 2:21 pm, Michael Selig wrote: > At 11/10/02, Jim Wilson wrote: > >David Megginson <[EMAIL PROTECTED]> said: > > > Thank you very much. It might be a good idea in the future to put 3D > > > models directly into Aircraft/*/Models/ rather than > > > Aircraft/*/Models/uiuc/, since 3D models are usable by all FDMs (all > > > four major ones use the same C172 model, for example). > > > >Agreed, there need not be a one to one relationship between fdm models and > > 3D models and the path implies there is. If there are differences in fdm > > data output that require multiple 3Dmodel xml files for animation, they > > can still be named according to the fdm they work with and still live in > > the same directory as a single mdl or ac file and texture set. > > > >Best, > > > >Jim > > Since these are imports courtesy of developers working with MSFS, would it > be a good idea to keep a copy of their models in original form in a > separate directory? That way they could always come to FGFS and fly their
I vote no. We can archive 'em someplace, but why should we use the extra bandwidth distributing something thats not used? > original models as well as any enhancements to them? In each case, the > original model developers have expressed some interest in FGFS. > > We don't keep on the cvs legacy code as we develop it, but it might make > sense to keep working legacy models when they are native to MSFS with their > associated credits. > > If this does make sense, I am not attached to the "uiuc" dir name. We > could call it "OEM", "orig", the author's name or something like that. > I understand where you are coming from, wanting to keep all uiuc enchancements segregated, but graphic and cosmetic stuff really should be consistently stored project wide. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
