789
edits
Howto:Transmit properties over MP: Difference between revisions
Jump to navigation
Jump to search
Clarified the difference between mp_broadcast and ordinary MP enabled properties. It is not like one replaces the other unconditionally.
No edit summary |
(Clarified the difference between mp_broadcast and ordinary MP enabled properties. It is not like one replaces the other unconditionally.) |
||
| Line 1: | Line 1: | ||
{{stub}} | {{stub}} | ||
Certain [[Property Tree|properties]] (eg. rudder deflection, flaps setting and gear position) are transmitted by default over the [[Howto: Multiplayer|multiplayer network]]. However there are still lots of (mostly [[aircraft]] specific) properties that are not. Due to this limitation, certain animations (eg. opening of a door or landing lights) won't be visible for a pilot's virtual-colleagues. | Certain [[Property Tree|properties]] (eg. rudder deflection, flaps setting and gear position) are transmitted by default over the [[Howto: Multiplayer|multiplayer network]]. However there are still lots of (mostly [[aircraft]] specific) properties that are not. Due to this limitation, certain animations (eg. opening of a door or landing lights) won't be visible for a pilot's virtual-colleagues. | ||
This wiki article will teach you '''how to transmit properties over a network'''. | This wiki article will teach you '''how to transmit properties over a network'''. | ||
The number of properties that can be sent over MP is limited. If you have properties that do not need to be sent frequently (e.g. only when a certain event happens) these can be sent more efficiently using mp_broadcast.nas in $FG_ROOT/Nasal, please see [[Howto:Using mp_broadcast.nas]], or using the time-sharing (TDM) or bit-packed components (SwitchEncoder/Decoder) for booleans in Aircraft/Generic/DualControl/dual-control-tools.nas. | |||
The method described here will send the properties in question in every multiplayer packet. This is appropriate for parts that need continuous animation but wasteful for many other uses. On the other hand, the method described here is easy to use so if you only have a small number of properties to share it may still be preferable. | |||
== -set.xml == | == -set.xml == | ||