20,741
edits
Nasal for C++ programmers: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (http://www.mail-archive.com/flightgear-devel@flightgear.org/msg18693.html) |
mNo edit summary |
||
| Line 33: | Line 33: | ||
There are two aspects to Nasal: that of interaction with itself and with the property tree. | There are two aspects to Nasal: that of interaction with itself and with the property tree. | ||
For instance, to control an aircraft in a scripted fashion, the property tree is going to be your communication with the wider FlightGear code. | For instance, to control an aircraft in a scripted fashion, the property tree is going to be your communication with the wider FlightGear code. See the following video of a fully scripted f14b carrier approach, using just Nasal scripting and the property tree: | ||
{{#ev:youtube |cvbtSG9cy20}} | |||
In such a scenario, you will mainly use the autopilot to control the aircraft (since it has a real FDM it's kinda hard to control), and we would definitely recommend one with a well-developed autopilot (the 777s are really excellent with everything and has a good autopilot with all features you want). One option with the 777 is that you could potentially use Nasal to dynamically edit routes that the aircraft just flies via the route manager – not much work there. Another approach would be manually adjusting the autopilot parameters (like heading hold, bank angle, and stuff like that) through Nasal feedback algorithms for aircraft that don't have a.route manager. You could also couple this with the XML autopilot (now called "property rule") system to have real PIDs, easy lowpass, etc. | In such a scenario, you will mainly use the autopilot to control the aircraft (since it has a real FDM it's kinda hard to control), and we would definitely recommend one with a well-developed autopilot (the 777s are really excellent with everything and has a good autopilot with all features you want). One option with the 777 is that you could potentially use Nasal to dynamically edit routes that the aircraft just flies via the route manager – not much work there. Another approach would be manually adjusting the autopilot parameters (like heading hold, bank angle, and stuff like that) through Nasal feedback algorithms for aircraft that don't have a.route manager. You could also couple this with the XML autopilot (now called "property rule") system to have real PIDs, easy lowpass, etc. | ||