20,741
edits
Fixing presets: Difference between revisions
Jump to navigation
Jump to search
→Issues
m (de-quoting) |
(→Issues) |
||
| Line 95: | Line 95: | ||
== Issues == | == Issues == | ||
{{FGCquote | |||
|1= It is probably helpful to review the presets code that sorts out all the different preset options depending on the values in this tree. That will give you an idea of what values you should leave empty, and what values to set to -9999.0 (for example) in order to effect the right startup mode. (The logic is a bit complex, so have patience when you work your way through that code.) Note, it appears (as best as I can see) that in air startups are broke and probably haven't worked for a while with JSBSim and YASim. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/24436310/ | |||
| title = <nowiki>Re: [Flightgear-devel] Setting position via property tree</nowiki> | |||
| author = <nowiki>Curtis Olson</nowiki> | |||
| date = Jan 26th, 2010 | |||
| added = Jan 26th, 2010 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
{{cquote| | {{cquote| | ||
Here's my current hypothesis: when FlightGear is reset, some modules are replaced with new ones (the old ones may or may not be deleted, but are never unbound). We end up with all kinds of dangling references, especially (but not exclusively) for bound properties, and eventually things grind to a halt. | Here's my current hypothesis: when FlightGear is reset, some modules are replaced with new ones (the old ones may or may not be deleted, but are never unbound). We end up with all kinds of dangling references, especially (but not exclusively) for bound properties, and eventually things grind to a halt. | ||