20,741
edits
Talk:Aircraft checklists: Difference between revisions
Jump to navigation
Jump to search
situations
m (limits.nas should be using the new xml checklists ... (DRY)) |
(situations) |
||
| Line 6: | Line 6: | ||
: Ah, that's a much more contentious one. The problem, from my point of view, is that our -set.xml files only encode one aircraft state (usually cold-and-dark). To encode (accurately) engines-running or in-flight as the start state, needs some kind of profile system where properties can have different values, and XML / Nasal can be initialised differently. That would make nice in-air starts possible (gear already up, throttles at sane position), as well as offering 'cold, dark and parked' or 'on the active and ready to go' as options. (And end all the per-aircraft 'auto-start' menu options - since they'd become standardised). <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html |title= Crazy usability suggestion of the day|author=James Turner |date= Tue, 05 Mar 2013 03:39:23 -0800}}</ref>|James Turner}} | : Ah, that's a much more contentious one. The problem, from my point of view, is that our -set.xml files only encode one aircraft state (usually cold-and-dark). To encode (accurately) engines-running or in-flight as the start state, needs some kind of profile system where properties can have different values, and XML / Nasal can be initialised differently. That would make nice in-air starts possible (gear already up, throttles at sane position), as well as offering 'cold, dark and parked' or 'on the active and ready to go' as options. (And end all the per-aircraft 'auto-start' menu options - since they'd become standardised). <ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg39672.html |title= Crazy usability suggestion of the day|author=James Turner |date= Tue, 05 Mar 2013 03:39:23 -0800}}</ref>|James Turner}} | ||
{{cquote|Unfortunately the underlying FDMs (JSBSim and Yasim) also have some limitations in this area - some won't correctly trim the aircraft unless it starts on the ground and stationary. Thorsten Brehm has done some improvements in this area but you still need to experiment to find all the settings for a particular aircraft, unfortunately. | |||
The real solution is each aircraft needs some additional code, which represents the 'in-air' state, or at least some sensible values) - engines running, gear up, fuel pumps on, etc. And then we need a way to request that state. This would be a fairly major addition, but it's something to consider after the next release.<ref>{{cite web |url=http://flightgear.org/forums/viewtopic.php?f=25&t=18466&p=171983&hilit=yasim+jsbsim+thorsten#p171983 |title= Re: starting in the air|author=Zakalawe |date= Fri Dec 07, 2012 12:19 pm}} </ref>|James Turner}} | |||
<references/> | <references/> | ||