> > ... And as always, I will voice my oppinion that aircrft files > > should never override configuration settings unless they absoloutely > > have to. > I agree: we shouldn't fiddle unnecessarily with a user's settings. If an > aircraft file does so for good reason, then this should be readily apparent > to the user.
I disagree. I think the aircraft should do *more* to set up scenarios that show off capabilities, both aircraft and simulator capabilities. I think the carrier-based aircraft should start on the carrier, for instance. The gliders should start in the air with thermals present. GA aircraft should start with ATC and GA traffic enabled. Airliners should start with AI traffic enabled. Fighters should start up with tankers or other fighters flying around so you can fly formation. This is the philosophy I used when setting the T-38 up with airborne radar to demonstrate that capability. I know the T-38 doesn't really have radar, but since I first put the model into FlightGear I figured nobody would object. Same with the OV-10 and weather radar and storms, and the Schweizer 2-33 and thermals. I bet there is a lot of things that FlightGear can do that nobody knows about. Maybe we need a new document, "Cool things that FlightGear can do that you probably didn't know about". And the various aircraft can help you with the tour. Dave _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
