On 11/10/2007, Hans Fugal <[EMAIL PROTECTED]> wrote: > This isn't the only plane that starts in cold configuration. I think > it would be best to be consistent - either leave it up to the plane > designer in every case (I believe in this case at least it was a > conscious decision on the part of the designer), or decide on a policy > that every aircraft should start hot and try to make that consistent > throughout.
I was the aircraft designer, though others have done a lot of excellent work on the Warrior since. One problem with starting in cold configuration by default is that in-air starts won't work. For example, if you use FlightGear to practice IFR approaches (like I do), you want to start in the air about 10 miles from the runway, not in the tie-down area. There was no way to do that using command-line options with the previous version of the config files. I recommend that we start all aircraft running and ready to roll, but provide an easy way for advanced users to start cold if they want to. I know that aircraft designers work hard on the switches and systems and want to show them off, but forcing people to use them every time might not be the best choice, especially for new users (and when the default start is on a runway threshold, where the engine should be running). All the best, David ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
