20,741
edits
Autopilot configuration reference: Difference between revisions
Jump to navigation
Jump to search
Autopilot configuration reference (view source)
Revision as of 14:55, 23 November 2015
, 23 November 2015→Proposed extensions
| Line 878: | Line 878: | ||
== Proposed extensions == | == Proposed extensions == | ||
This sections contains new features for the autopilot to be implemented. Nobody knows if and when this will happen. Consider this as a collection of ideas as a base for discussion on the mailing list, the forum or IRC. | This sections contains new features for the autopilot to be implemented. Nobody knows if and when this will happen. Consider this as a collection of ideas as a base for discussion on the mailing list, the forum or IRC. | ||
=== Expose to Nasal === | |||
Given that Nasal is a widely-known bottleneck, people should not use it for implement FDM/AP or route-manager functionality in scripting space. However, for the time being, the underlying C++ code is not exposed to scripting space, so that aircraft developers tend to reinvent the wheel. Thus, it would make sense to expose the AP/property-rule/state machine subsystems to scripting space using the [[Nasal/CppBind]] framework, to ensure that existing C++ code can be used for such purposes: | |||
{{FGCquote | |||
|1= I have recently committed some code to allow runtime loading of <strike>autopilots</strike> property rules and have a Nasal binding for that in mind. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=149376#p149376 | |||
| title = <nowiki>Re: 2 Questions: vacuum & electrical</nowiki> | |||
| author = <nowiki>Torsten</nowiki> | |||
| date = Feb 2nd, 2012 | |||
}} | |||
}} | |||
== Related content == | == Related content == | ||