TMD files, apart from the main / default one, can be used to express flight dynamics properties under three states - ground, approach, clean.
I've been thinking about this approach and the limitations it can impose.
For a start, how do these states blend as transition from clean to approach takes place ?
And, why was it necessary to separately / so discretely, define the flight dynamics according to these three states only ?
Just open any ground, approach and clean file and you'll understand approach and clean are only presets configurations. For instance flaps extended, gear down, landing lights on, etc. for approach ; gear up, flaps up, n% power, lights setting, etc. for clean.
So, no different dynamics or flight model, and no blending necessary, just presets applied depending on whether you start a flight on ground, in-flight or in approach...
Cheers
Antoine
Just open any ground, approach and clean file and you'll understand approach and clean are only presets configurations. For instance flaps extended, gear down, landing lights on, etc. for approach ; gear up, flaps up, n% power, lights setting, etc. for clean.
So, no different dynamics or flight model, and no blending necessary, just presets applied depending on whether you start a flight on ground, in-flight or in approach...
Cheers
Antoine
Right! That's it - how stupid of me :-/ Should have opened one before posting, but just read the Wiki, and it somehow suggest it's used for the flight Dynamics too.
Thank you!
As mentioned correctly: the three states are just states, not a full flight dynamic definition. They are used to extend the flaps fully when the aircraft is loaded for example. That way there is no transient in flaps when you click on the icon in the final approach from the location dialog. First the aircraft tmd file is loaded then one of the three configuration files is loaded and the state is injected to the loaded aircraft. It's just for the initialisation of the aircraft, doesn't really change anything in terms of physics.
