In addition, what is the temperature and atmospheric conditions at the default runway?
I'd
like to run a test with known conditions - i.e. I'd like to use our JSBSim internal
atmosphere. I suspect that the atmospheric conditions are getting passed in by default,
true?
Jon
Jon Berndt writes:
In addition, what is the temperature and atmospheric conditions at the default
runway? I'd
like to run a test with known conditions - i.e. I'd like to use our JSBSim internal
atmosphere. I suspect that the atmospheric conditions are getting passed in by
default,
true?
6:29 PM
To: FlightGear developers discussions
Subject: RE: [Flightgear-devel] Defaults
Jon Berndt writes:
In addition, what is the temperature and atmospheric conditions at the
default runway? I'd
like to run a test with known conditions - i.e. I'd like to use our JSBSim internal
Norman Vine writes:
Hmm... maybe this would help
untested - but it 'looks' like this will fix 'this' problem,
don't thin it will cause any new ones
It won't work because the properties in the *-set file will override
anything specified on the command line. I'm going to go in today and
The preferences.xml file specifies the c172 as the default. It
appears that even if you request a different aircraft as the default,
the c172 config files get loaded first anyway, then the alternate
config file is loaded with the correct aircraft. This means that if
the c172 specifies any
Curtis L. Olson wwrites:
David Megginson writes:
Curtis L. Olson writes:
The preferences.xml file specifies the c172 as the default. It
appears that even if you request a different aircraft as the default,
the c172 config files get loaded first anyway, then the alternate
