Jamie Major 1273522 Posted October 25, 2019 at 04:57 PM Posted October 25, 2019 at 04:57 PM Hello, been having this problem for a while now if I start Xpilot then close it and attempt to open it agian it throws this error. Not sure whats going on with it. Can confirm its fully closed down. Any ideas thanks. Link to comment Share on other sites More sharing options...
Board of Governors Roger Curtiss Posted October 26, 2019 at 05:26 AM Board of Governors Posted October 26, 2019 at 05:26 AM I received the same error today as well. Xpilot had loaded just fine a few days ago. This error arose after I downloaded and installed the latest version 1.1.1...I believe. Roger Curtiss VATGOV12 VP-Virtual Airlines & Special Ops r.curtiss(at)vatsim.net Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 26, 2019 at 05:32 AM Posted October 26, 2019 at 05:32 AM Do you have exact steps to reproduce this error? I'm unable to reproduce it by opening and closing xPilot. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Board of Governors Roger Curtiss Posted October 26, 2019 at 05:47 PM Board of Governors Posted October 26, 2019 at 05:47 PM If I open XPilot before opening XPlane then it comes up just fine but with the message that it cannot find XPlane. If I open XPalne and then launch XPIlot the Unhandled exception error pops up. I did check and I am running the latest version of Windows .net framework 4.8 Roger Curtiss VATGOV12 VP-Virtual Airlines & Special Ops r.curtiss(at)vatsim.net Link to comment Share on other sites More sharing options...
David Veksenfeld Posted October 27, 2019 at 10:17 PM Posted October 27, 2019 at 10:17 PM I think I figured out a fix. You probably have other Vatsim Client plugins installed, whether it be XSquakbox or xSwiftbus. If you do, disable them in the plugins list on X-Plane 11. I also disabled xPilot in that list too. I tried launching xPilot after that and it worked, and I re-enabled xPilot in the plugins list. I connected to Vatsim with no issues. Hopefully this fixes anyone else's issue, and if not make sure you have the latest .NET framework from Microsoft. Link to comment Share on other sites More sharing options...
Robert Shearman Jr Posted October 27, 2019 at 10:25 PM Posted October 27, 2019 at 10:25 PM Side note -- it's recommended to move any and all other folders for AI traffic or multiplayer network clients completely out of the Resources/plugins folder rather than just disabling them in the menu. Whether or not the above error is related, said plugins can "fight for control" of the aircraft CSL animations. Cheers, -R. Link to comment Share on other sites More sharing options...
Board of Governors Roger Curtiss Posted October 29, 2019 at 12:24 AM Board of Governors Posted October 29, 2019 at 12:24 AM I think I figured out a fix. You probably have other Vatsim Client plugins installed, whether it be XSquakbox or xSwiftbus. If you do, disable them in the plugins list on X-Plane 11. I also disabled xPilot in that list too. I tried launching xPilot after that and it worked, and I re-enabled xPilot in the plugins list. I connected to Vatsim with no issues. Hopefully this fixes anyone else's issue, and if not make sure you have the latest .NET framework from Microsoft. Indeed...this seems to have worked. Thank you Roger Curtiss VATGOV12 VP-Virtual Airlines & Special Ops r.curtiss(at)vatsim.net Link to comment Share on other sites More sharing options...
Justin Shannon Posted October 29, 2019 at 12:30 AM Posted October 29, 2019 at 12:30 AM I think I figured out a fix. You probably have other Vatsim Client plugins installed, whether it be XSquakbox or xSwiftbus. If you do, disable them in the plugins list on X-Plane 11. I also disabled xPilot in that list too. I tried launching xPilot after that and it worked, and I re-enabled xPilot in the plugins list. I connected to Vatsim with no issues. Hopefully this fixes anyone else's issue, and if not make sure you have the latest .NET framework from Microsoft. Indeed...this seems to have worked. Thank you Which part fixed your issue? Removing other plugins or upgrading your .NET framework version? Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
David Veksenfeld Posted October 30, 2019 at 10:22 PM Posted October 30, 2019 at 10:22 PM Deleting the plugins fixed my issue. I had been running the latest .NET framework when I was getting the issue. Link to comment Share on other sites More sharing options...
Recommended Posts