20,741
edits
Navigation display: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 6: | Line 6: | ||
You should be able to get the ND showing TCAS, waypoints, the route path, VORs and airports. I would hope the symbol definitions and textures you need can be borrowed from the A380 and converted, otherwise I have the 777 versions (which are definitely different!) or they're in the main 777 repo. | You should be able to get the ND showing TCAS, waypoints, the route path, VORs and airports. I would hope the symbol definitions and textures you need can be borrowed from the A380 and converted, otherwise I have the 777 versions (which are definitely different!) or they're in the main 777 repo. | ||
The '''navigation display''' (ND) instrument provides a texture resembling the display of the navigation or map displays found in many digital cockpits and GPS units. The instrument tries to be sufficiently generic, to approximate many different real-world displays. Fortunately, most real-world displays are quite similar to each other, with some systems offering additional features that will be added later. | The '''navigation display''' (ND) instrument provides a texture resembling the display of the navigation or map displays found in many digital cockpits and GPS units. The instrument tries to be sufficiently generic, to approximate many different real-world displays. Fortunately, most real-world displays are quite similar to each other, with some systems offering additional features that will be added later. | ||
| Line 63: | Line 54: | ||
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> | |||