At 11/30/02, Erik Hofman wrote:
Hi,I forgot to comment out the record lines w/ the last update to the Sopwith Camel. I just posted an update to the cvs to stop this recording w/ the Camel. From what I see, none of the other UIUC airplanes have recording turned on, so it only should have happened w/ the Sopwith Camel assuming you have an update-to-date base package cvs (and assuming I'm not missing anything, which is what happened in the first place!).
After recent changes the UIUC aircraft seem to generate a uiuc_record.dat file. I would like to ask the UIUC developers to leave this option(?) off for production files included in the FlightGear base package.
They are left in the current directory where FlightGear is called from, which causes the files to get scattered all over the system.
:-(
FYI - With the UIUC planes, the default is no recording. Recording options can be turning on w/ lines inside the aircraft.dat files (e.g. see lines after the '*' in ~/fgfsbase/Aircraft/UIUC/sopwithCamel-v1-nl/aircraft.dat). When it is on, running fgfs will produce a stream of sim data to the file uiuc_record.dat to the current dir. I always run from the same dir, so there's only one file. This way files don't end up "all over the system", which would be a bummer.
Regards,
Michael
**************************************************
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:[EMAIL PROTECTED]
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
