308
edits
Multiplayer protocol: Difference between revisions
Jump to navigation
Jump to search
→Properties transmitted over MP
| Line 324: | Line 324: | ||
A subset of the following properties are transmitted in the order below. Properties marked as V1_1_2_PROP_ID will only be sent when the 2017.2 protocol (or later) is selected. '''Transmit As''' is also only relevant for 2017.2 or later. | A subset of the following properties are transmitted in the order below. Properties marked as V1_1_2_PROP_ID will only be sent when the 2017.2 protocol (or later) is selected. '''Transmit As''' is also only relevant for 2017.2 or later. | ||
Although the MP protocol can transmit many different packets mostly a '''T_PositionMsg''' identified by MsgId of '''POS_DATA_ID (7)''' in the header. Refer to {{flightgear file| | Although the MP protocol can transmit many different packets mostly a '''T_PositionMsg''' identified by MsgId of '''POS_DATA_ID (7)''' in the header. Refer to {{flightgear file|src/MultiPlayer/mpmessages.hxx|l=48}} for the PROTO_VER that is in use, currently this is ''0x00010001'' which is '''1.1''' | ||
The '''T_PositionMsg''' contains the standard MsgHdr, with position and motion information next and then a set of properties. Within the protocol ''1.1'' there is a secondary version that applies to the way that the properties are encoded, and this secondary version is either 1 or 2 (2017.2) | The '''T_PositionMsg''' contains the standard MsgHdr, with position and motion information next and then a set of properties. Within the protocol ''1.1'' there is a secondary version that applies to the way that the properties are encoded, and this secondary version is either 1 or 2 (2017.2) | ||