Startup Profiles: Difference between revisions

Jump to navigation Jump to search
Line 24: Line 24:
</ref>
</ref>


One thing I spent some idle time thinking on, was adding meta-data to states, to allow the system to select one based on startup location criteria. The most obvious examples being to look at altitude and requested IAS, and exclude / select certain states. This would be a way for the 777 to select cruise vs climbout states based on altitude requested, for example. And select flaps up or down, IAS vs Mach, STD vs actual pressure altitude and assorted other nuances. However, this will rapidly become an explosion of states. So I avoided mentioning this in my initial proposal - I’d rather go with simple and robust than clever-and-confusing. Of course the startup parameters are available in /sim/startup as they always have been, so aircraft can still make tweaks from Nasal based on those values, if they wanted to adjust mixture, flaps or whatever based on the actual altitude. I forgot to mention this in my proposal, but I figure once we have a few examples covering Yasim and JSBSim for normal aircraft (sorry Torsten, probably not the Shuttle…), we can see which per-aircraft pieces can actually be generalised / standardised to reduce the amount of copy-and-paste duplication. I don’t imagine we’d get to a point where a particular aircraft needsero customisation to work (same as the generic autopilot always needs tuning), but we might save 75% of the boilerplate. Again, I’d want to get experience with the basic setup I proposed, and then refactor once we have a good range of examples.
<ref> {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34983912/
  | title  = <nowiki>Re: [Flightgear-devel] In-air vs on-ground starts</nowiki>
  | author = <nowiki>James Turner</nowiki>
  | date  = Apr 1st, 2016
  | added  = Apr 1st, 2016
  | script_version = 0.25
  }}
</ref>


<references/>
<references/>

Navigation menu