20,741
edits
Emesary: Difference between revisions
Jump to navigation
Jump to search
→Intro
(→Intro) |
|||
| Line 31: | Line 31: | ||
This is in Richard's git repository in his commit, together with the changes to the AI carriers to add ACLS (carrier ILS): https://sourceforge.net/u/r-harrison/fgdata/ci/54165c213f03638a4cb02c848c4f2b234c537f66/ | This is in Richard's git repository in his commit, together with the changes to the AI carriers to add ACLS (carrier ILS): https://sourceforge.net/u/r-harrison/fgdata/ci/54165c213f03638a4cb02c848c4f2b234c537f66/ | ||
There are many possible applications for Emesary within the system, it solves the problem of how to connect generic instruments to aircraft that have different implementations and properties that need to be used. | There are many possible applications for Emesary within the system, it solves the problem of how to connect generic instruments to aircraft that have different implementations and properties that need to be used. Richard has been looking at how to abstract out the interface to the MFD and [[NavDisplay]]. | ||
Richard has plans to extend this to be able to transmit over {{Abbr|mp|Multiplayer}} (probably layered ontop of mp-broadcast). It would also probably work quite well with the [[High-Level_Architecture#Federate_Object_Model|HLA FOM]] to give us a way for models to communicate with other models.<ref> {{cite web | Richard has plans to extend this to be able to transmit over {{Abbr|mp|Multiplayer}} (probably layered ontop of mp-broadcast). It would also probably work quite well with the [[High-Level_Architecture#Federate_Object_Model|HLA FOM]] to give us a way for models to communicate with other models.<ref> {{cite web | ||