At 3/15/02, you wrote:
>David Megginson wrote:
>>Erik Hofman writes:
>>  > To get it working the UIUC code should populate the property tree 
>> with  > at least the following properties (for a piston engine driven 
>> aeroplane):
>>  >  >  > starting/stoping the sounds:
>>  > ---------------------------
>>  > /engines/engine/cranking
>>  > /engines/engine/running
>>  > /gear/gear[]/wow
>>  > /surface-positions/flap-pos-norm
>>  > /sim/aero/alarms/stall-warning
>>Since UIUC doesn't have any engine start-up code or stall-detection
>>code, it's probably good enough just to set /engines/engine[0]/running
>>to true (repeat for additional engines), and to copy the value of the
>>flap control directly to /surface/positions/flap-pos-norm.
>
>Or create a sepperate config file which does use the correct properties 
>for UIUC (without modifications to the code).


Thanks for all the input on this.  It helped get us going.  The properties 
structure is pretty neat!

If few questions (probably too many):

[1] Does it sense to define and set our properties inside LaRCsim.cxx and 
not further down in the uiuc_ code?  Does it matter?  I can certainly 
envision cases where we will want to set properties inside our uiuc_ code.

If we do add the myriad properties for many aircraft configuration types to 
LaRCsim.cxx it means adding lots of code I think.

[2] Where should we put the sound files.  Right now the files are in 
~fbfsbase/Sounds.  But different aircraft will have different 
sounds.  Should these sound files go in the respective ~fgfsbase/Aircraft 
directories?

[3] The properties structure is pretty general.  It seems like it would be 
pretty easy to trample over someone else's property definitions and/or make 
poor/improper usage of them?  Is there a standard list of reserved properties?

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

Reply via email to