Howto:Transmit properties over MP: Difference between revisions

Howto:Transmit properties over MP (view source)

575 bytes added , 17 February

m

Adding a small section on sub-models.

19

edits

@@ Line 8: / Line 8: @@
    |script_version = 0.40
    }}</ref>
-}}{{Warning| Any effects defined in a xml file which are declared as "submodel" won't be exported to a multiplayer session. The method described here cannot be applied to these. If you need some effects visible in multiplayer sessions, they must not be sub-modelled, or sub-sub-modelled.}}
+}}{{Warning| Any effects defined in a xml file which is declared as "submodel" won't be exported to a multiplayer session. The method described here cannot be applied to these. If you need some effects visible in multiplayer sessions, they must not be sub-modelled, or sub-sub-modelled.}}
 This wiki article will teach you '''how to transmit properties over a network'''.
@@ Line 86: / Line 86: @@
 <property alias="../../params/lighting/landing-light-l/property"/>
+== XML files used in sub-models ==
+Sub-models are AI models and they use MP/AI properties. They are totally different to a regular model attached to another model, because they can be detached and be independently simulated<ref>James (dev mailing list)</ref>. As such, their relative path in the property tree are deeper than usual models. All effects defined within sub-models are currently skipped from multiplayer sessions and bombs, boosters, detachable parts of aircraft remain invisible in MP sessions<ref>https://gitlab.com/flightgear/flightgear/-/issues/3063</ref>.
 == Related content ==