• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Connecting to SimConnect from remote computer

R

rf360m

Messages
961
Hi all,

I have successfully set up SimConnect on the same ocmputer as FSX, but now I am trying to connect from a remote computer and have been getting an error.

When I launch FSX it says "Can't init simconnect error"

The SimConnect.xml is:

<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>192.168.1.103</Address>
<MaxClients>64</MaxClients>
<Port>48447</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
</SimBase.Document>

If I change scope to local and and address to 127.0.0.1 it works fine locally but not remotely.

Any ideas?

Thanks!

-Russell
 
rf360m said:
I have successfully set up SimConnect on the same ocmputer as FSX
Click to expand...

It shouldn't really need any "setting up" on the same PC as FSX, as the FSX install is supposed to take care of that.

... but now I am trying to connect from a remote computer and have been getting an error.

When I launch FSX it says "Can't init simconnect error"
Click to expand...

Have you actually installed SimConnect on the remote PC? You need to run the SimConnect.msi file from the SDK section of the Deluxe edition of FSX.

If I change scope to local and and address to 127.0.0.1 it works fine locally but not remotely.
Click to expand...

When you provide a SimConnect.xml file you need both local and global sections -- if you only have a global one nothing with connect to FSX on the FSX PC, including any DLLs that should be loaded.

On the remote PC you need the SimConnect.cfg file in your "My Documents" folder to contain the name or IP address of the FSX PC.

Regards
Pete
 
Pete Dowson said:
When you provide a SimConnect.xml file you need both local and global sections -- if you only have a global one nothing with connect to FSX on the FSX PC, including any DLLs that should be loaded.
Click to expand...

Interesting - so my simconnect.xml file should have two <SimConnect.Comm> sections, one for local and one for global?

-Russell
 
Having both a local and a global section in the xml file did the trick! Thanks for the tip.

-Russell
 
Last edited:
rf360m said:
Having both a local and a global section in the xml file did the trick! Thanks for the tip.

-Russell
Click to expand...

Glad it was that easy. I've been complaining to the FS team about this ambiguity (global is NOT global, but remote only!) and I believe they will be fixing it. But for now it is confusing many folks.

Regards

Pete
 
In fact you could use only a global section with local applications as long as you provide a correct simconnect.cfg for them.
This is because the TCP port (either the one set by the user in simconnect.xml or a randomly choosed one) is *not* posted to the windows registry for a global scope.
 
lc0277 said:
In fact you could use only a global section with local applications as long as you provide a correct simconnect.cfg for them.
This is because the TCP port (either the one set by the user in simconnect.xml or a randomly choosed one) is *not* posted to the windows registry for a global scope.
Click to expand...

Even if that does work (I've not tried it), it is not good practice as it will prejudice any future improvements in local SimConnect efficiency, which I hope and expect to occur as SimConnect develops. The best course at present is to specify "Auto" as the local protocol, with no Port specification, and let SimConnect choose the method and route.

Regards

Pete
 
You must log in or register to reply here.
Back
Top