20,741
edits
Dual control: Difference between revisions
Jump to navigation
Jump to search
→Developer information
| Line 68: | Line 68: | ||
}} | }} | ||
}} | }} | ||
{{FGCquote | |||
|1= it's roughly like this. | |||
The nasal modules in f-14b-bs-set.xml are loaded and do the work of connecting the RIO to the pilot's aircraft. However the mp-network cannot be loaded until the model is loaded (can't remember exactly why, but it has to be done this way). | |||
So the approach to take is to ensure that you use /sim/multiplay/generic/float or /sim/multiplay/generic/int (0..19 of each) to share the important properties over mp. This is the easiest way. If you look at the F-14 you'll see that a whole heap of animations and gauges are connected to the multiplay properties, because these will work either when flying or as an MP aircraft. If you don't want to change the animations then a nasal module inside the co-pilot to copy the multiplay/generic into the right place will work. See backseat instruments for an example of how this is done. | |||
It gets more difficult if you need to transmit more than the permitted amount of parameters (40). Then you either have to start packing using bits, or use one of the string parameters to share the rest. Using the string parameters (as in the F-14 and the F-15) is quite inefficient and it is something that I'm working on fixing so that we have much better interaction between the front and back seats - but the first thing I'll do is to get the key properties transmitted using ints or floats, and then do the rest probably using the Emesary multiplayer bridge that I'm working on. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=282793#p282793 | |||
| 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 | |||
}} | |||
}} | |||
<!--of caution --> | |||
}} | }} | ||