Emesary notifications: Difference between revisions

From FlightGear wiki
Jump to navigation Jump to search
(added new notification types.)
No edit summary
Line 6: Line 6:
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 ===  
Line 22: Line 22:


Used to indicate when an some sort of armament has impacted another model. See f-14b/Nasal/ArmamentNotification.nas
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 ===
ArmamentInFlightNotification_Id = 20
ArmamentInFlightNotification_Id = 21


This is a notification that a particular type of armament is in flight. see f-14b/Nasal/ArmamentNotification.nas
This is a notification that a particular type of armament is in flight. see f-14b/Nasal/ArmamentNotification.nas

Revision as of 14:22, 5 May 2020


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

Related content

Wiki articles

Forum topics

External documentation