I think we could concentrate our effort to evaluate some parameters in way
to verify a good or bad landing and so we can also generate a sort of damage
relatory acording to situation.
Sergio Roth
- Original Message -
From: Thales de Lima Ferreira [EMAIL PROTECTED]
To: [EMAIL
David Megginson wrote:
Graphic Artists
---
We also need a couple of good icons, one for the application and one
for its data files. I made a crappy one depicting a 3/4 view of a
inexplicably greenish Cessna 310 in a steep turn, and will use it if
no one develops anything
It's now possible to pass property files as simple command-line
arguments to the FlightGear application, as in
fgfs start-at-lax.fgd
The start-at-lax.fgd file would probably look something like this:
PropertyList
sim
startup
airport-idKLAX/airport-id
/startup
/sim
David Megginson writes:
Norman Vine writes:
The general rule of thumb for portable applications is to use
the lowest common denominator or in the case filenames
use the 8.3 rule
max 8 letters for a file or directory name
max 3 letters for a file extension
do not use case
* [EMAIL PROTECTED] (throttle1000) [2002.01.04 21:26]:
That would add about 2000 different aircrafts
in one night to the FGFS. There should only be
an additional FGFS file which would give those
parameters that are not found in MSFS files.
And that could be some default file for most
new
