20,741
edits
| Line 63: | Line 63: | ||
4) The function now being called turns off the magnetos. This is clearly not desired behavior if all I'm trying to do is relocate. This is a low-priority bug, because I can work around it by saving and restoring the magneto settings. | 4) The function now being called turns off the magnetos. This is clearly not desired behavior if all I'm trying to do is relocate. This is a low-priority bug, because I can work around it by saving and restoring the magneto settings. | ||
5) The function now being called zeros the settings for aileron trim, elevator trim, and rudder trim. Again, this is clearly not desired behavior. <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20095.html |title= location-in-air| | 5) The function now being called zeros the settings for aileron trim, elevator trim, and rudder trim. Again, this is clearly not desired behavior. | ||
I have a pretty-much workable workaround for the worstof these bugs. | |||
The big clue is that "presets-commit" apparently just deletes the old FDM instance and creates another. | |||
To make the new FDM happy, I had to delete a bunch of nodes from the property tree. Some other nodes needed to be set to -9999; merely deleting them | |||
was not good enough. This allows me to relocate-in-air once without getting flipped upside down (or worse). | |||
There is still some opportunity for improvement in connection with presets-commit and with FDM init in general.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20095.html |title= location-in-air| | |||
author=John Denker|date=Sun, 07 Jan 2007 09:20:14 -0800}} </ref>|John Denker}} | author=John Denker|date=Sun, 07 Jan 2007 09:20:14 -0800}} </ref>|John Denker}} | ||
{{cquote|As previously reported, the corresponding presets have no effect during a re-init, e.g. via fgcommand("presets-commit").<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20095.html |title= a few more bugs|author=John Denker|date= Tue, 30 Dec 2008 09:50:28 -0800}} </ref>|John Denker}} | {{cquote|As previously reported, the corresponding presets have no effect during a re-init, e.g. via fgcommand("presets-commit").<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20095.html |title= a few more bugs|author=John Denker|date= Tue, 30 Dec 2008 09:50:28 -0800}} </ref>|John Denker}} | ||
{{cquote|Once the users intentions have been communicated to the FDM module, it's really up to the particular FDM, (JSBsim or YAsim) to do the right thing with the provide information. That does seem to have broke down at some point. I used to be able to happily start both YAsim and JSBsim aircraft in flight, but had zero luck last time I tried. | |||
<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20132.html |title= amazing FDM initialization bug|author=Curtis Olson |date=Wed, 31 Dec 2008 10:43:18 -0800}} </ref>|Curtis Olson}} | |||
{{cquote|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. They do however continue to work fine with an external proprietary fdm I've been using for another project.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25882.html |title= Setting position via property tree|author=Curtis Olson |date= Tue, 26 Jan 2010 07:54:25 -0800}} </ref>|Curtis Olson}} | {{cquote|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. They do however continue to work fine with an external proprietary fdm I've been using for another project.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg25882.html |title= Setting position via property tree|author=Curtis Olson |date= Tue, 26 Jan 2010 07:54:25 -0800}} </ref>|Curtis Olson}} | ||