I'm trying to connect to the network, and I get this message. https://gyazo.com/783f93787cec2915e494517b314bed2d
If there is anything I can do to correct this let me know.
Simconnect Error Confirm Flight Simulator is On
-
- Posts: 819
- Joined: Sat Jan 18, 2014 5:13 pm
Re: Simconnect Error Confirm Flight Simulator is On
Same issue right now
Helping a friend to run P3D on his full motion 737 sim on Windows 7 professional
Helping a friend to run P3D on his full motion 737 sim on Windows 7 professional
Kyle Sanders
Re: Simconnect Error Confirm Flight Simulator is On
It would help if you confirmed WHICH version of flight sim is being run (FSX box, FSE SE, X-plane).
Going to assume this is FSX.
IF FSE box, confirm that the latest service pack (SP1 or SP2) has been installed or FSX acceleration pack has been installed.
IF FSE SE, confirm that the simconnect.MSI in the PE client has been run.
Have you make any modifications to the simconnect.cfg (configuration) files?
Have you looked through the common errors thread?
viewtopic.php?f=8&t=835
Has this sim EVER worked (with or without PE)?
Tell us about other packages installed on the system (FSUIPC, add on packages).
Going to assume this is FSX.
IF FSE box, confirm that the latest service pack (SP1 or SP2) has been installed or FSX acceleration pack has been installed.
IF FSE SE, confirm that the simconnect.MSI in the PE client has been run.
Have you make any modifications to the simconnect.cfg (configuration) files?
Have you looked through the common errors thread?
viewtopic.php?f=8&t=835
Has this sim EVER worked (with or without PE)?
Tell us about other packages installed on the system (FSUIPC, add on packages).
Last edited by wmburns on Sun Apr 03, 2016 7:34 pm, edited 2 times in total.
-
- Posts: 9943
- Joined: Sat Oct 09, 2010 8:38 pm
- Location: Pompton Plains, NJ
- Contact:
Re: Simconnect Error Confirm Flight Simulator is On
It can't be xplane if it's SimConnect.
In the case Kyle mentioned, the error was caused by having a SimConnect.cfg file with a port number that was incorrect as the user had set up custom ports for the SimConnect server and didn't update the SimConnect.cfg file to refer to the new ports.
In the case Kyle mentioned, the error was caused by having a SimConnect.cfg file with a port number that was incorrect as the user had set up custom ports for the SimConnect server and didn't update the SimConnect.cfg file to refer to the new ports.