I have been using P3D on VatSim for a while, and it’s been fine. Yesterday I installed ActiveSky and now my P3D will not connect to VatSim and I don’t know why. Sometimes it’ll detect that the sim is running and other times it just won’t. I don’t think ActiveSky has anything to do with it because it doesn’t do anything with the connection to VatSim other than request ATIS information.
Alrighty update, it appears to not be ActiveSky and rather GSX. I don’t know how to fix this as this installation of GSX is only a few weeks old… I could try deleting it and starting fresh, although I’m not sure what to do. Although, after a few minutes now I get “Simulator appears to be frozen.” and get disconnected. I hate vPilot…
Update 2: GSX again appears to not be the problem. Just re-enabled it and left ActiveSky disabled, and the sim connected. I don’t know what the hell is going on at this point I wish vPilot wasn’t so damn picky.
Why would you hate vPilot? vPilot is simply reporting to you that you have a problem with your setup that is interfering with your ability to operate on VATSIM. All of the pilot clients have such capability.
I don’t get why it’s getting all bothered by ActiveSky the second I close ActiveSky there’s no longer a problem. It’s either something with ActiveSky(which I doubt) or vPilot is doing something strange.
Not entirely sure. I can give some data points:
Roughly 30,000 VATSIM users use P3D
Roughly 2,000 connections are made a day using P3D, almost all of those using vPilot
We do not have data on how many use P3D and AS, or P3D+AS+GSX
So the data is pretty clear that it’s not a vPilot problem, else I surmise we’d have thousands of people complaining.
Unfortunately, I know that doesn’t help you solve your issue. Unfortunately, I really don’t know where to start with that, other than trying to segregate variables.
Any insight from your Event Viewer?
Anything else change? Recent Windows update?
I have the solution, and what makes all this so odd is Event Viewer had no relevant logs, SimConnect had no relevant logs, and P3D didn’t either… Everything said it was operating as intended. It was an issue from P3Dv4 that resurfaced. Had to delete wxstationlist.bin from %appdata%/Roaming/Lockheed Martin/Prepar3d v5. That seemed to have fixed my issue. What made this issue all the more strange is that I could connect to VatSim at anywhere in the world other than the United Kingdom. After deleting that file and letting P3D make a new one I can connect to the network with no issue. With all the issues I’ve had previously with vPilot and having to reinstall it and try alternate versions several times in the past I was expecting another instance of issues with the client.
Thanks for the update! Interestingly, I’ve been running P3D and AS and GSX for years, and had not run into that issue before. Then again, I rarely fly into the UK (which reminds me, I need to do more of that!). Thanks for sharing, and I hope that takes care of it permanently!