Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Simconnect as stopped working

Featured Replies

Well, I had Simconnect working just fine. AS2012 and PlanG were both running on my Client and life was good. So, I did not run the client for about a month and when I attempted to run it again, suddenly Simconnect will no longer connect.

 

I did some quick investigation and checking simconnect.xml on the server and simconnect.cfg on the client every thing look fine. I checked my server IP and discovered my IPv4 had changed, so I quickly edited the .xml and the .cfg and thought every thing would be fine. Wrong! I still cannot connect.

 

Any ideas?

 

Here are my Simconnect files:

 

simconnect.xml

 

p<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv6</Protocol>
<Scope>link-local</Scope>
<MaxClients>64</MaxClients>
<Address>fe80::35a3:b41:6f3c:8e16</Address>
<Port>4506</Port>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>192.168.1.114</Address>
<MaxClients>64</MaxClients>
<Port>500</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>local</Scope>
</SimConnect.Comm>
</SimBase.Document>

 

simconnect.cfg

 

[simConnect]
Protocol=IPv4
Address=192.168.1.114
Port=500
MaxReceiveSize=4096
DisableNagle=0

 

Intel Core Ultra 9 285K | GIGABYTE Z890 AORUS Elite X ICE | RTX 5080 | 32GB DDR5 | Win 11 Pro | Acer Predator UltraWide 3440x1440 (G-Sync)

  • Author

Just to add to the mystery, (or possibly clarify it?), I have determined that Plan G which is using IPv4 is actually connecting to simconnect. What this means is that IPv6 is working and IPv4 which AS2012 uses is not. Perhaps that is a clue, but I am still at a loss.

 

Intel Core Ultra 9 285K | GIGABYTE Z890 AORUS Elite X ICE | RTX 5080 | 32GB DDR5 | Win 11 Pro | Acer Predator UltraWide 3440x1440 (G-Sync)

Just to add to the mystery, (or possibly clarify it?), I have determined that Plan G which is using IPv4 is actually connecting to simconnect. What this means is that IPv6 is working and IPv4 which AS2012 uses is not. Perhaps that is a clue, but I am still at a loss.

 

Dont quite understand this statement. Plan G uses IPv4? AS2012 uses IPv4? None of my simconnect devices use IPv6, otherwise they are all IPv4. Not even sure how to use IPv6 in the network settings. If i recall its a strange protocol.

  • Author

Dont quite understand this statement. Plan G uses IPv4? AS2012 uses IPv4? None of my simconnect devices use IPv6, otherwise they are all IPv4. Not even sure how to use IPv6 in the network settings. If i recall its a strange protocol.

 

IPv6 is no harder to use than IPv4 and Plan G gives the choice of IPv6 or IPv4 or WideFS. Just look under options - fs connections. Any way IPv6 has stopped working again and IPv4 still won't work, so I am getting fed up with simconnect. I have re-run simconnect.msi on the client, reinstalled Accelration and the SDK SPv1a on the server with no luck. I just wish AS2012 would use WideFS and I could be done with Simconnect.

 

Intel Core Ultra 9 285K | GIGABYTE Z890 AORUS Elite X ICE | RTX 5080 | 32GB DDR5 | Win 11 Pro | Acer Predator UltraWide 3440x1440 (G-Sync)

Hi remilton,

 

Not sure if this will help or not, but I figured I'd throw this out there just in case it does help. I fly FSX using 2 pc's. 1 is my main flying machine, and the second runs a few of my saitek panels and FSWidgets GMap. My modem was recently changed out by my ISP, and the new one is also a router, so it has taken over DHCP duties. Now neither machine will keep an IP address unless I set them manually (which I really don't want to have to do.) Needless to say, anytime I boot my main pc (Host machine), the stuff attached to the client wouldn't function until I got the new IP from the host machine, then updated all the simconnect files on both machines. Anyhow, I found out that, at least when using IPv4 for the 'address' entry, I was able to use the name of the pc instead of an actual IP address. Since making this change, I no longer have problems with the client machine connecting.

 

So on the host, in the simconnect.xml, the "<address>" for me is "George-PC", and on the client, in the simconnect.cfg file(s), the "address=" is also set to "George-PC".

 

I'm not on my main pc right now, but the address field was the only thing I needed to change, so everything else was left to defaults, including IPv4.

 

As long as none of your programs *require* IPv6, you may be able to just use IPv4 and the host computer's name to get your simconnect connecting again.

 

Good luck, and I hope this is helpful in some way.

 

-George

Happy Flying!

-George

ftx_supporter_avsim.gif

  • Author

Thanks for the tip George, unfortunately it does not fix my problem. The pc's are networked correctly and simconnect is installed correctly, The simconnect just quit working one day. I have a few more things to try, but the list is getting short. Thanks again.

-Ron

 

Intel Core Ultra 9 285K | GIGABYTE Z890 AORUS Elite X ICE | RTX 5080 | 32GB DDR5 | Win 11 Pro | Acer Predator UltraWide 3440x1440 (G-Sync)

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.