Emesary notifications: Difference between revisions
m (→Related) |
(+-lead section: Removing heading; +-related: Splitting links in sections; Hiding the mailing list search, currently Template:Search only support forum searches, see template doc) |
||
| Line 1: | Line 1: | ||
{{Nasal Navigation}} | {{Nasal Navigation}} | ||
This page defines the '''Emissary Notifications''' that are available in the base package; but also a reference of all currently active notification ID's that can be transmitted over MP. | |||
This page defines the Notifications that are available in the base package; but also a reference of all currently active notification ID's that can be transmitted over MP. | |||
=== PropertySyncNotificationBase === | === PropertySyncNotificationBase === | ||
| Line 19: | Line 18: | ||
This is a notification, usually from one craft to another, over MP, that something happened at a certain position (lat,lon,alt). This can be used to drop tanks, paratroopers, launch X-15's or anything that happens that one craft needs to tell another about. | This is a notification, usually from one craft to another, over MP, that something happened at a certain position (lat,lon,alt). This can be used to drop tanks, paratroopers, launch X-15's or anything that happens that one craft needs to tell another about. | ||
== Related content == | |||
=== Wiki articles === | |||
* [[Emesary]] | |||
* [[Emesary MFD Bridge]] | |||
=== Forum topics === | |||
* {{Search|mode=forum|keywords=emesary}} | |||
<!-- | |||
=== Mailing list === | |||
* {{Search|mode=list|keywords=emesary}} --> | |||
== | == External documentation == | ||
* http://chateau-logic.com/content/emesary-multiplayer-bridge-flightgear | * http://chateau-logic.com/content/emesary-multiplayer-bridge-flightgear | ||
* http://chateau-logic.com/content/emesary-nasal-implementation-flightgear | * http://chateau-logic.com/content/emesary-nasal-implementation-flightgear | ||
| Line 26: | Line 35: | ||
* https://emesary.codeplex.com/documentation | * https://emesary.codeplex.com/documentation | ||
* http://chateau-logic.com/content/emesary-efficient-inter-object-communication-using-interfaces-and-inheritance | * http://chateau-logic.com/content/emesary-efficient-inter-object-communication-using-interfaces-and-inheritance | ||
Revision as of 09:33, 29 March 2020
 |
The FlightGear forum has a subforum related to: Nasal Scripting |
 |
| Nasal scripting |
|---|
 |
| Nasal internals |
|---|
| Memory Management (GC) |
This page defines the Emissary Notifications that are available in the base package; but also a reference of all currently active notification ID's that can be transmitted over MP.
PropertySyncNotificationBase
PropertySyncNotificationBase_Id = 16
This is used to transmit a set of properties from one craft to a multiplayer instance of itself. The contents of the notification are variable and defined by the model.
AircraftControlNotification
AircraftControlNotification_Id = 17
This is used to allow any number of elements to be controlled, such as cockpit switches, but theoretically anything on the model that needs to be controlled either as a single player ownship, or as a multiplayer dual control type of scenario. NOTE: Properly coded aircraft models using Emesary to implement bindings require no extra code to work in multiplayer, all that is required is to bridge the control notifications over MP using the Emesary MP bridge.
GeoEventNotification
GeoEventNotification_Id = 18
This is a notification, usually from one craft to another, over MP, that something happened at a certain position (lat,lon,alt). This can be used to drop tanks, paratroopers, launch X-15's or anything that happens that one craft needs to tell another about.
Related content
Wiki articles
Forum topics
External documentation
- http://chateau-logic.com/content/emesary-multiplayer-bridge-flightgear
- http://chateau-logic.com/content/emesary-nasal-implementation-flightgear
- http://emesary.codeplex.com/
- https://emesary.codeplex.com/documentation
- http://chateau-logic.com/content/emesary-efficient-inter-object-communication-using-interfaces-and-inheritance