Hi @Buntstift68 ,
I’ve not fully tested this personally but SimConnect does support connecting to MSFS running on another PC, via a network.
First, find the external IP address of the MSFS2020 PC.
To do this, open a Command Prompt (on the MSFS2020 PC, obviously) and type:
IPCONFIG
You’re looking for the IPv4 Address, it will likely start with “192.168.”
Whilst on the MSFS2020 PC, we need to find the correct port number SimConnect should use. The default is 500, but we can double-check.
In the Command Prompt, change to the install folder of MSFS2020, if you installed it via Steam, it will be in your Steam Library, usually in a folder like:
\SteamLibrary\steamapps\common\MicrosoftFlightSimulator
Now we’ll check to see if you have a SimConnect.xml file, this is the config file used by the SimConnect server. In the Command Prompt window, type:
DIR SimConnect.xml /s
If no files are found, you’re using the standard port (500), if a file exists, open it with your text editor to find which port your network connection is listening on.
On the PC running the tool/component you want to run remotely, in the application folder, you should find the SimConnect.dll. You may also find a SimConnect.cfg file. If not, create a new config file “SimConnect.cfg”.
In the config file, enter/update the following:
[simConnect]
Protocol=IPv4
Address=<MSFS2020 IP Address from above>
Port=<Port Number from above>
MaxReceiveSize=4096
DisableNagle=0
Replace the Address and Port values with the external IP address and port number of the PC running MSFS2020.
We’re not completely finished, you also need to ensure the firewall on your MSFS2020 PC allows connections to the port above, I can’t help a lot here, as every firewall product is different.
In your firewall, you need to allow inbound TCP/IP and UDP connections to the port number we found above.
After all that, if it still doesn’t connect, try modifying the SimConnect.xml file on the MSFS2020 PC, to force it to use the external IP, it may have just connected to the internal loopback IP address (127.0.0.1), which means it isn’t listening for connections externally.
Like I said, I can’t testify this works 100% but it should allow your remote application to connect using the native SimConnect DLL.
Dragonlaird