6,566
edits
Canvas ND framework: Difference between revisions
Jump to navigation
Jump to search
Switch from {{fgaddon url}} to {{fgaddon aircraft source}}.
(Switch to {{gitorious url}} to fix the broken Gitorious links.) |
(Switch from {{fgaddon url}} to {{fgaddon aircraft source}}.) |
||
| Line 27: | Line 27: | ||
Note that the latest ND code is currently only available in Git and not in the latest stable release. | Note that the latest ND code is currently only available in Git and not in the latest stable release. | ||
# Add a surface object to your 3D model and apply a place holder texture to it. You can refer to the 747-400 and 777 for examples. | # Add a surface object to your 3D model and apply a place holder texture to it. You can refer to the 747-400 and 777 for examples. | ||
# Copy the ND.nas file of the Boeing 777 into your own aircraft directory ( | # Copy the ND.nas file of the Boeing 777 into your own aircraft directory ({{fgaddon aircraft source|777|Models/Instruments/ND/ND.nas|text=Aircraft/777/Models/Instruments/ND/ND.nas}}). | ||
# Add the file to the <nasal> block in your aircraft's [[Aircraft-set.xml|-set.xml]] file. | # Add the file to the <nasal> block in your aircraft's [[Aircraft-set.xml|-set.xml]] file. | ||
# In order to customize the ND for your specific aircraft, change a few options in your ND.nas file: | # In order to customize the ND for your specific aircraft, change a few options in your ND.nas file: | ||
## the node behind <code>addPlacement</code> is the name of the object in your 3D model. For multiple independent NDs, each ND should have its own object (and thus placement node). The 777 for example has a "ndScreenL" and a "ndScreenR". | ## the node behind <code>addPlacement</code> is the name of the object in your 3D model. For multiple independent NDs, each ND should have its own object (and thus placement node). The 777 for example has a "ndScreenL" and a "ndScreenR". | ||
## Rename the properties in the "myCockpit_switches" hash at the top of the ND.nas file to match your own properties (range selector, mode selector etc.), see | ## Rename the properties in the "myCockpit_switches" hash at the top of the ND.nas file to match your own properties (range selector, mode selector etc.), see {{fgaddon aircraft source|747-400|Models/Cockpit/Instruments/ND/ND.nas|text=Aircraft/747-400/Models/Cockpit/Instruments/ND/ND.nas}}. You're advised to use the defaults (and change other systems of your aircraft accordingly). For an overview of switches, see [[#Cockpit switches]]. | ||
# Add knobs/buttons to the 3D model of your cockpit to control the various options of the ND. See | # Add knobs/buttons to the 3D model of your cockpit to control the various options of the ND. See {{fgaddon aircraft source|777|Models/Instruments/EFIS/efis-ctl1.xml|text=Aircraft/777/Models/Instruments/EFIS/efis-ctl1.xml}} for an example. | ||
# Add a binding to your screen(s) to open the ND in a popup dialog. See | # Add a binding to your screen(s) to open the ND in a popup dialog. See {{fgaddon aircraft source|777|Models/Instruments/ND/ND_L.xml|text=Aircraft/777/Models/Instruments/ND/ND_L.xml}} for an example. | ||
That's the only thing you need to do right now. future changes will be in navdisplay.mfd and will be automatically available to you once they're committed/merged, no changes needed in your ND.nas at all, except for additional switches/buttons that may be created, and which would obviously need to be mapped to your cockpit hot spots. | That's the only thing you need to do right now. future changes will be in navdisplay.mfd and will be automatically available to you once they're committed/merged, no changes needed in your ND.nas at all, except for additional switches/buttons that may be created, and which would obviously need to be mapped to your cockpit hot spots. | ||