FSUIPC: Difference between revisions
Jump to navigation
Jump to search
(http://forum.flightgear.org/viewtopic.php?f=18&t=29250&p=281461#p281461) |
No edit summary |
||
Line 4: | Line 4: | ||
--> | --> | ||
People familiar with Microsoft-based flight simulators, and addons, will typically expect a middleware like FSUIPC to be also required for working with FlightGear (FSUIPC is a mechanism to access simulator internals in FSX/MS FS). | |||
People familiar with Microsoft-based flight simulators will typically expect a | |||
However, FlightGear is open source and does not need such a middleware. In fact, most of FlightGear's internals are made accessible in the form of the so called [[Property tree]]. | However, FlightGear is open source and does not need such a middleware. In fact, most of FlightGear's internals are made accessible in the form of the so called [[Property tree]]. | ||
Furthermore, the [[Property Tree]] can be exposed/accessed via various interfacing mechanisms, such as for example: | Furthermore, the [[Property Tree]] can be exposed/accessed via various interfacing mechanisms, such as for example: |
Revision as of 17:57, 3 April 2016
Work in progress This article or section will be worked on in the upcoming hours or days. See history for the latest developments. |
People familiar with Microsoft-based flight simulators, and addons, will typically expect a middleware like FSUIPC to be also required for working with FlightGear (FSUIPC is a mechanism to access simulator internals in FSX/MS FS).
However, FlightGear is open source and does not need such a middleware. In fact, most of FlightGear's internals are made accessible in the form of the so called Property tree. Furthermore, the Property Tree can be exposed/accessed via various interfacing mechanisms, such as for example:
- a built-in web-server
- a built-in telnet (props) server
- an XML configurable generic protocol
- custom binary protocols
(to name just a few).