Azref

I am having issues with the iniManager and making purchases. When i click buy in the app the checkout does not load and simply opens a panel with a blue circle. I have tried reinstalling the iniManager but it hasn't fixed the issue. I have also tried logging out and back in. I am not using a VPN or anything and am running the iniManager as Admin Any help is appreciated.

Hi Max Just ran a test with a freshly configured Warthog profile. The A310 and A300 load without issue. I have only tried the Freighter version for both so far as had limited time today. Kind regards

Hi Max. I seem to have located the issue causing the crash and it has nothing to do with a plugin, LUA script or scenery item. If i delete my controller profile folder the aircraft will load in both the new install and my original. The cause seems to be the use of my Thrustmaster Warthog. As long as I don't use it both the A300 and A310 will load without issue. (Thankfully I have a Honeycomb setup for airliners so can swap over) Could someone look into why the TM Warthog is causing the aircraft to crash on load?

Hi Max. This is after I reinstalled the plugins and scenery back to what i had previously. As stated previously removing them made no difference to the SASL crash. I am happy to try a second XPlane install however don't see how that would be much help as the attached logs detail that it's the SASL causing the crashes. I'm wondering if it's an SASL conflict or download error with the iniManager at this point as I have already tried removing all plugins and scenery with the crash still occuring. I also don't understand why the aircraft load without issue prior to activation.

Just wanted to add my name to the SASL crash list. I can load the aircraft if it's not activated. As soon as I activate and try to load XPlane crashes from an SASL error pointing to the A300. This is also occuring with the A310 for me. All other aircraft work and only the A300 and A310 by iniBuilds seem to cause any issue. I have cleared out my scenery and plugins but the error still persists. I didn't have this issue with the A300 V1 until it started after the installation of the A310. Any help is greatly appreciated as at the moment I feel rather disappointed in having spent a substantial amount on aircraft I can't seem to load/fly. A310 Log.txt A300 Log.txt