Actually, I would prefer not to use any DLL-based interface. That is quite 1990-style. A network-based interface using TCP is the way to go for any modern system, if only because this means that the new modules do not need to be running on the same machine as the MSFS operating system. On top, DLL means Windows means platform-dependent, which is also 1990-style.
Something as the MCDU is eminently network-capable and it would be a pity if it had to be run as a native module inside MSFS.
Of course any API that can be implemented in a small DLL for MSFS dropin, which then opens a TCP socket for the real communication to an external program, is an acceptable workaround. I see this happening for the new PSx free-standing simulator. It will not include external scenery except for basic runway environments, but there will probably be a dropin MSFS DLL to quickly and easily connect MSFS as the windshield (using Sim Connect).
Thanks for the help
Richard,
Actually, I would prefer not to use any DLL-based interface. That is quite 1990-style. A network-based interface using TCP is the way to go for any modern system, if only because this means that the new modules do not need to be running on the same machine as the MSFS operating system. On top, DLL means Windows means platform-dependent, which is also 1990-style.
Something as the MCDU is eminently network-capable and it would be a pity if it had to be run as a native module inside MSFS.
Of course any API that can be implemented in a small DLL for MSFS dropin, which then opens a TCP socket for the real communication to an external program, is an acceptable workaround. I see this happening for the new PSx free-standing simulator. It will not include external scenery except for basic runway environments, but there will probably be a dropin MSFS DLL to quickly and easily connect MSFS as the windshield (using Sim Connect).
Jeroen