20,741
edits
FSUIPC: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
(to name just a few). | (to name just a few). | ||
== Bridging == | |||
There have been several more or less complete attempts at creating middleware to turn a fgfs client into a FSUPIC client, i,e, a working framework for allowing add-ons that use FSUIPC to talk to FlightGear. A a client program that will pretend to be Microsoft Flight Simulator from the standpoint of the FSUIPC interface. The code is based on the open source XConnect project that does the same thing for X-Plane.<ref>{{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/32255576/ | |||
| title = <nowiki>[Flightgear-devel] Property documentation...</nowiki> | |||
| author = <nowiki>geneb</nowiki> | |||
| date = Apr 22nd, 2014 | |||
| added = Apr 22nd, 2014 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
For details, see: https://github.com/geneb/win-fguipc | |||
It's still VERY much alpha, but it works with the test frameworks that come with the FSUIPC SDK. (FSUIPC is the framework that people use to write add-ons (glass cockpits, etc) for Microsoft Flight Simulator since FS2000 on up to FSX.)<ref>{{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/32298253/ | |||
| title = <nowiki>Re: [Flightgear-devel] Features for 3.2 please</nowiki> | |||
| author = <nowiki>geneb</nowiki> | |||
| date = May 3rd, 2014 | |||
| added = May 3rd, 2014 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||