Navigation display: Difference between revisions

Jump to navigation Jump to search

Navigation display (view source)

Revision as of 19:41, 30 January 2014

684 bytes removed ,  30 January 2014
m
→‎Configuration Examples
No edit summary
Line 58: Line 58:


In general you will write some Nasal or XML to update these properties each frame (eg, reading the simulated INS position or calculated top-of-climb position) and write that into a property node, supplying the type and state values. Symbol rules with then be applied as normal.
In general you will write some Nasal or XML to update these properties each frame (eg, reading the simulated INS position or calculated top-of-climb position) and write that into a property node, supplying the type and state values. Symbol rules with then be applied as normal.
== Configuration Examples ==
It is currently implemented for the A380 and the Citation-Bravo aircraft (see [[$FG_ROOT]]/Aircraft).
The Bravo now contains a non-Airbus example of using the NavDisplay texture to show traffic, the route-path, and nearby data. The Bravo is definitely the best example in FGDATA right now. There's some docs on the Wiki about using the NavDisplay. The git commit containing the NavDisplay implementation details is available here: http://gitorious.org/fg/fgdata/commit/dcc9efd9de194316a06b6a1801e147e3b023d6cc
http://gitorious.org/fg/fgdata/blobs/master/Aircraft/Citation-Bravo/Systems/nav-display.xml
<syntaxhighlight lang="xml">
</syntaxhighlight>


== Related ==
== Related ==
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/66835"

Navigation menu