At 11/10/02, Jim Wilson wrote:
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 original models as well as any enhancements to them? In each case, the original model developers have expressed some interest in FGFS.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
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.
Regards,
Michael
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
************************************************** Prof. Michael S. Selig Dept. of Aero/Astro Engineering University of Illinois at Urbana-Champaign 306 Talbot Laboratory 104 South Wright Street Urbana, IL 61801-2935 (217) 244-5757 (o), (509) 691-1373 (fax) mailto:m-selig@;uiuc.edu http://www.uiuc.edu/ph/www/m-selig http://www.uiuc.edu/ph/www/m-selig/faq.html (FAQ) ************************************************** _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
