[EMAIL PROTECTED] wrote:
Does this mean that we would have the ability to save and load flight data so as to reproduce, say, a taxi, take off, pattern and landing at KSFO or another airport automatically (i.e., as a demo or as a training exercise). Perhaps a short flight around the SF area also showing off the new scenery?I think that the ability to "play" a flight recorded by an external source is different from the ability to save/load a flight from FG.
Could we ship such flights around scenic areas (Mount Ranier, Crater Lake, the Grand Canyon) for new users in the base package or as downloadables off of flightgear.org?
How big would such files be? How much data needs to be kept, how much can be calculated on the fly? Do weather conditions need to be saved also?
Would flights around scenic areas be done better as flight plans with waypoints or tied into this new playback method somehow?
Can this playback tool be used as a training method for new simulator pilots?
If we are not saving a real recorded flight, perhaps we can use a similar method to extract either entire flights or the last XX number of seconds of a flight to save to disk for later replay?
MS FlightSimulator has an extensive tutorial that involves pre-saved flights which the users can break into at certain points in the flights. How difficult would it be to add something similar to FG and where would one begin (if no one is already working on something like this).
Thanks!
Ima
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
In other words, I don't think we should save any state variable - ie parts of totality of the property tree.
We have an initial state when FG is launched with a specific set of parameters. Now how do you fly ? You use your joystick, mouse,
keyboard et al to interact with the simulator. So a recorded fligth could be defined as a list of user interactions paired with a time stamp,
and to be more accurate a very limited set of properties could be added lets say every 10 or 20 seconds (position, heading, etc).
The advantage would be :
- short record file size
- accurate property tree because the simultor would run exactly with the same imputs
- easy to implement because it is not tied to the internals of the simulator (like fdm).
Harald.
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
