20,741
edits
Dual control: Difference between revisions
Jump to navigation
Jump to search
→Developer information
(→Aircraft: Switched to {{gitorious source}} to abstract the Airbus A320 Family URLs for Gitorious.) |
|||
| Line 56: | Line 56: | ||
== Developer information == | == Developer information == | ||
{{Caution| | |||
{{FGCquote | |||
|1= Normally the only Nasal available will be loaded from the model xml. The -set is effectively a placeholder for an invisible craft as you'll be sitting inside someone else's MP aircraft. The normal -set file isn't loaded at all. All properties need to be transmitted over MP, so if /instrumentation/cdu/serviceable is missing it'll need to be sent. It's a really strange concept that all of the normal stuff isn't where it usually is. It took me a while to figure out this for the F-14 RIO which I think is done in the same way | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=282765#p282765 | |||
| title = <nowiki>Re: Dual control for Boeing 777</nowiki> | |||
| author = <nowiki>Richard</nowiki> | |||
| date = Apr 17th, 2016 | |||
| added = Apr 17th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
}} | |||
}} | |||
The main part of the Dual Control system is a set of generic [[Nasal scripting language|Nasal]] modules and modified instrument files that form the core of the networked shared control functionality. See the link below for some more information. | The main part of the Dual Control system is a set of generic [[Nasal scripting language|Nasal]] modules and modified instrument files that form the core of the networked shared control functionality. See the link below for some more information. | ||