Dont worry about that error.
It relates to a backup server on the backend.

Something I'm not worried about at the moment and will look into a some point.

I can see that you did connect successfully.

Thanks Dave. I think I see the issue(s) but I'm not going to have time to fix them for a few days. It looks like it's the "." "," separator that is used with certain language packs. In some parts of the world a lat lon would be 52.123456 3.123456 in others... 52,123556 3,123456 I...

Hi Dave.

Thanks for the post.

Can you send me your log.txt file located in ProgramFiles(x86)/simcomx folder.

AFAIK the source code for the Xplane plugin is not available.

I'm unable to have a look at the moment as my laptop threw a hardware fault, so I'm in the middle of rebuilding it (literally). But Peter might have output the version being used to the log file? Any SimConnect version you use later than the Xpack version SHOULD support an app written for the Xpack ...

Have you tried with the Xpack version of simconnect installed? I am getting the same repeat error on connect. I am running 1.3.0.9 Where do I obtain the Xpack version? Thank AL :mrgreen: I have installed the "Xpack version" of 10.0.61259.0, bringing my total to 4 versions of SimConnect cl...

Have you tried with the Xpack version of simconnect installed?

walt642 wrote:Changed Xpuipc config ip address to 127.0.0.2

Is that right XPlane users?
I would have thought 127.0.0.1????

Thank you.

I think I know what that is.

I experimented with something a few days ago, which I'll change back shortly.

Using SimCom X by connecting to a sim before then, may fix it.

No app update needed.

Well I can see quite a few people now using SimCom X successfully. I know people dont know what frequency others are using, so I would encourage people to use the Unicom frequency 122.800 when trying it out on their own. As it's now working, I'm going to calm down on the updates. I can see a few min...