Hello guys,
first of all thank you for providing this support forum! I really need some help.
I will try to provide as much information as possible so this will probably end up in a giant wall of text.
First things first: I switched from FSX to P3D v3 and I got some serious issues that I have never had before.
In the following, I will go through my problems in some sort of timeline... :smile:
1) First installation of P3D v3.0
Installed following addons: Aerosoft Airbus, Active Sky, AivlaSoft EFB, Navigraph Database, TOPCAT, PFPX, FS2Crew 737 and Airbus
All was fine, everything was working perfectly!
Purchase and installation of the PMDG 737, problems started: :excl:
1-2 hours into the flight my joystick suddenly would stop working in P3D. Plane was confi on autopilot and everything was "fine", exept that I was unable to do anything within P3D with my Joystick.
If I tried to open up any menu (Set Time and Season, Chose Airport, Change Airplane) my sim would crash and I would get this error message:
In this phase I made various tests and I can say that the Aerosoft Airbus as well as any default airplane would not stop my joystick from working nor would I get any error when I tried to open up any window at any given time. (Btw: If my joystick was working on the PMDG 737 in the first hour, I could open menus as well).
I was unable to fix the problem no matter what I did (reinstalling / uninstalling various addons, as well as the 737 ofc) so I decided the completly reinstall P3D and all of its components.
Now things will get very weird:
2) Complete reinstall of P3D v3.0 and with all of the addons
The problem was kinda "fixed". I guess it was, but I can't be sure as you will see in the following. PMDG 737 worked and joystick wouldn't crash on me anymore.
[update to P3D v3.1]
Purchase and installation of PMDG 777-200/F
The problem came BACK! This was so weird... the PMDG 777 now had the exact, EXACT same problem as the 737 had on the first install (see 1) )
It didn't matter whether ASNext, AivlaSoft, PFPX or TOPCAT were running or not. 1-2 hours into the flight, or even just standing still on the runway, the joystick would stop working.
Opening windows would result in:
So I began to search the internet again, tried all sorts of stuff but eventually read that PMDG and KERNELBASE.dll couldn't really be connected, I decided to try to get rid of the KERNELBASE.dll problem with reinstalling WINDOWS 7!
And with that, things got even worse.. or even more weird
3) Reinstalling windows 7 and with that P3D v3.1 as well
Installed all of my addons as well as PMDG 737 and 777 and I thought all was working wonderfully, as I flew with the 737 from EKCH-LGAV and everything was fine. On final approach into LGAV I got a new error:
I wasn't worried too much, since my joystick didn't fail on me. And I blamed the xactengine3_4.dll error on FS2Crew.
So I happily started a new flight the next day as suddenly my joystick stoped working 1 hour into the flight. I was shocked. I went ahead and opened up a menu, which would cause the KERNELBASE.dll problem on the old windows 7, but the sim just shut down without any error. No error in eventviewer, no error, absolutly nothing.
I did some more testing: Aerosoft Airbus (7 hours of flight time since windows 7 reinstall) and PMDG 777 (5 hours of testing) are working fine so far.
To sum this all up:
1) PMDG 737 Joystick problem + KERNELBASE
2) PMDG 737 is fine, PMDG 777 Joystick problem + KERNELBASE
3) PMDG 737 Joystick problem WITHOUT KERNELBASE problem
Some more information:
I tested 2 Saitek X52, both with same results, so I don't think my joystick is broken. Furthermore the joystick works when again when I restart P3D and it works in windows all the time.
I tested 1 and 2, with and without the Saitek drivers and right now I won't install them again, since the problem occured with and without the drivers already back in my old OS. Furthermore uninstalling Saitek Drivers is a pain and I don't need and don't want them on my system anymore.
This is pretty much all I know at this point.
If you made it this far, I really really thank you for reading this, maybe someone has a solution for this very weird problem.
Greetings,
Franz-Niklas Büter
#Edit 1: Added full name