20,741
edits
Fixing presets: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 77: | Line 77: | ||
{{cquote| | {{cquote| | ||
There's also more to the problem. If we're restoring a saved flight then everything's fine, since all of the FDM state is already valid. If, on the other hand, we're starting in the air, then we need a general trimming routine like the one Tony wrote for JSBSim and LaRCsim to avoid violent oscillations at startup.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg09856.html |title= Presets menu|author=David Megginson |date=Mon, 18 Nov 2002 14:44:41 -0800}}</ref>|David Megginson}} | There's also more to the problem. If we're restoring a saved flight then everything's fine, since all of the FDM state is already valid. If, on the other hand, we're starting in the air, then we need a general trimming routine like the one Tony wrote for JSBSim and LaRCsim to avoid violent oscillations at startup.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg09856.html |title= Presets menu|author=David Megginson |date=Mon, 18 Nov 2002 14:44:41 -0800}}</ref>|David Megginson}} | ||
{{cquote| | |||
I've actually added a general reinit facility for FlightGear subsystems, but most subsystems haven't been modified to support it yet. In time, we should be able to reinitialize anything - 3D models, keyboard bindings, radio frequencies, or even scenery - without stopping the program. <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@flightgear.org/msg11597.html |title= GUI|author=David Megginson |date=Fri, 24 Jan 2003 04:41:29 -0800}}</ref>|David Megginson}} | |||