20,741
edits
m (http://www.mail-archive.com/flightgear-devel@flightgear.org/msg06785.html) |
No edit summary |
||
| Line 1: | Line 1: | ||
= The Problem = | |||
The addition of Presets has caused a plethora of problems and many regressions, including breaking support for reset/re-init, but also for saving/loading flights. | |||
= Background = | |||
At one point we decided that it would be useful to reset the aircraft position to someplace else while running FlightGear. JSBSim was modified so if it sensed that any of the position properties where changed it would retrim to those values. This was a start, but the problem was that we were using the same set of properties to report fdm position/orientation as we were using to request a change. This turned out to be a little hard to work with, especially if you wanted to change several parameters ... you got reset 1 time for each parameter you changed. | At one point we decided that it would be useful to reset the aircraft position to someplace else while running FlightGear. JSBSim was modified so if it sensed that any of the position properties where changed it would retrim to those values. This was a start, but the problem was that we were using the same set of properties to report fdm position/orientation as we were using to request a change. This turned out to be a little hard to work with, especially if you wanted to change several parameters ... you got reset 1 time for each parameter you changed. | ||
| Line 25: | Line 29: | ||
The way this was intended to work is that if you want to start on the ground, you should set the altitude to -9999. | The way this was intended to work is that if you want to start on the ground, you should set the altitude to -9999. | ||
Exposing the raw /sim/presets properties to the end user leaves a lot of room for them to make mistakes. | Exposing the raw /sim/presets properties to the end user leaves a lot of room for them to make mistakes. | ||
= Issues = | |||
{{cquote| | {{cquote| | ||