Emesary notifications: Difference between revisions
m (→Related) |
(reserve id 22 for EFISNotification) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Nasal Navigation}} | {{Nasal Navigation}} | ||
This page defines the '''Emesary 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 === | ||
PropertySyncNotificationBase_Id = 16 | 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. | 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. see $FGdata/Nasal/notifications.nas | ||
=== AircraftControlNotification === | === AircraftControlNotification === | ||
AircraftControlNotification_Id = 17 | 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. | 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. see $FGdata/Nasal/notifications.nas | ||
=== GeoEventNotification === | === GeoEventNotification === | ||
GeoEventNotification_Id = 18 | 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. | 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. see $FGdata/Nasal/notifications.nas | ||
=== ArmamentNotification === | |||
ArmamentNotification_Id = 19 | |||
== Related == | Used to indicate when an some sort of armament has impacted another model. See f-14b/Nasal/ArmamentNotification.nas | ||
=== PFDEventNotification_Id === | |||
PFDEventNotification_Id = 20 | |||
Use to transmit PFD events for a particular device. see $FGdata/Nasal/notifications.nas | |||
=== ArmamentInFlightNotification === | |||
ArmamentInFlightNotification_Id = 21 | |||
This is a notification that a particular type of armament is in flight. see f-14b/Nasal/ArmamentNotification.nas | |||
=== EFISNotification_Id === | |||
EFISNotification_Id = 22 | |||
Use to transmit EFIS events. Work in progress, see $FGdata/Nasal/notifications.nas later | |||
== 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 56: | ||
* 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:31, 22 May 2020
 |
The FlightGear forum has a subforum related to: Nasal Scripting |
 |
| Nasal scripting |
|---|
 |
| Nasal internals |
|---|
| Memory Management (GC) |
This page defines the Emesary 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. see $FGdata/Nasal/notifications.nas
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. see $FGdata/Nasal/notifications.nas
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. see $FGdata/Nasal/notifications.nas
ArmamentNotification
ArmamentNotification_Id = 19
Used to indicate when an some sort of armament has impacted another model. See f-14b/Nasal/ArmamentNotification.nas
PFDEventNotification_Id
PFDEventNotification_Id = 20
Use to transmit PFD events for a particular device. see $FGdata/Nasal/notifications.nas
ArmamentInFlightNotification
ArmamentInFlightNotification_Id = 21
This is a notification that a particular type of armament is in flight. see f-14b/Nasal/ArmamentNotification.nas
EFISNotification_Id
EFISNotification_Id = 22
Use to transmit EFIS events. Work in progress, see $FGdata/Nasal/notifications.nas later
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