Namespace globals emesary_mp_bridge
--------------------------------------------------------------------------- Title : EMESARY multiplayer bridge File Type : Implementation File Description : Bridges selected emesary notifications over MP : To send a message use a Transmitter with an object. That's all there is to it. References : http://chateau-logic.com/content/emesary-nasal-implementation-flightgear Author : Richard Harrison (richard@zaretto.com) Creation Date : 04 April 2016 Version : 4.8 Copyright © 2016 Richard Harrison Released under GPL V2 ---------------------------------------------------------------------------*/
Classes
IncomingMPBridge
one of these for each model instantiated in the model XML - it will route messages to
Variables
EmesaryMPBridgeDefaultPropertyIndex
The incoming bridge will usually be created part of the aircraft model file; it is important to understand that each AI/MP model will have an incoming bridge as each element in /ai/models needs its own bridge to keep up with the incoming sequence id. This scheme may not work properly as it relies on the model being loaded which may only happen when visible so it may be necessary to track AI models in a seperate instantiatable incoming bridge manager. The outgoing bridge would usually be created within the aircraft loading Nasal.