American Airlines Virtual

I mentioned this as part of the New Microsoft Flight Sim thread and it was suggested I post it as a new thread so here goes.

I re-purchased the Aerosoft Airbus A320/321 for P3Dv4 (since I already had it for FSX) and got to fly it one time! After installation I flew a quick circuit around the airport just as a test and things went ok. The next time I loaded the A320, and every time since, it will crash P3D after about 30-60 sec. Another guy on the Aerosoft forum had the same problem. I've worked with Aerosoft support for the past 2 or 3 months trying to resolve the problem. After trying numerous suggestions they provided to no avail, they say they see a Kernelbase.dll error and the only way to resolve it is to reload Windows . The only issue I have on my computer is when I select the A320 a/c, everything else works fine (all my other payware a/c, and all my Windows applications). So I'm not going to reload my entire computer just to get that one a/c to work.

At some point I will do some investigation on that dll to see if I can find anything.

Ted, I had issues, too, but it was the managed speed drop issue which it looks like has been fixed. Looks like part of the issue had more to do with rebooting the computer immediately after installing and before starting up P3Dv4.

If you haven't already, I'd uninstall the 320/321, delete the folder structure it creates, pause your A/V, re-download the 320/321 package from Aerosoft, install it as Admin, restart the computer, then give it a try.

Try the software version downloaded from Aerosoft BEFORE applying any updates with their Updater. If you apply updates later, remember to RESTART before flying.

I haven't flown the 318-321's for a couple of months . Will try to work a flight in over the next couple of days. I'm currently running v1.2.4.2 of the product and I see there are regular and experimental updates available. I'll fly with my current version before updating.

I'm on WIN7 and the latest version and patch for P3Dv4.

Ted, too bad about the A-bus and P3d, I wanted one. The Kernelbase.dll error would not only be because of the aircraft. I get the same error almost each time I shut off P3d. Somewhere in the computer is a file which P3d does not like, and it probably doesn't like the airbus either, so double your pleasure. I am still using Win 7 for my FS computer.
I think Aerosoft was using it as a catch all "fix".
WLP

Wayne Pierce wrote: ↑10-05-2019 10:44 AM ... I get the same error almost each time I shut off P3d...)

I get a "Prepar3D exe has stopped working" error every time I shut down P3D when running the Majestic Q400. That a/c only. No problem with any others. It has a conflict with a module that is getting loaded at P3D startup. I determined that by doing the below. Ted, you might want to see if this helps you zero in on what is causing your problem, too.

I edited the dll.xml file located at C:\Users\YOURNAME\AppData\Roaming\Lockheed Martin\Prepar3D v4 and changed (just the start of the file is shown below)

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>

to

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>True</Launch.ManualLoad>
<Launch.Addon>

Save the change and start P3d. It will prompt to load all the modules. I would only load the mimimal modules you think are essential for the A320/321 to function, then try flying.

In the case of my Q400, all I loaded was FSUIPC. When I exited P3D from the Q400, no error! I could selective add other modules and determine which is the conflict -- but I'm too lazy. I can live with the error since it only happens when I close P3D running the Q400.

When I installed the Aerosoft Airbus' I did NOT install RAAS. That possibly is another difference in our configs.

I think I recall "ordering" issues with the modules in dll.xml but that was a long time ago and several galaxies back. Still, that might be something to consider.

Flew my next leg KBWI-KMIA using the Aerosoft A320 v 1.2.4.2. No Problems.

I'll load v 1.2.5.0 next week and fly another leg. This is probably the version you are downloading from Aerosoft.

First, let me thank all of you for your suggestions. As usual you are all very helpful. And like you, I am still on Win 7.

Harold Henderson wrote: ↑10-05-2019 04:43 AM If you haven't already, I'd uninstall the 320/321, delete the folder structure it creates, pause your A/V, re-download the 320/321 package from Aerosoft, install it as Admin, restart the computer, then give it a try.

Harold, I did all of the above except re-booting immediately after the installation. I'll give this a try.

Wayne Pierce wrote: ↑10-05-2019 10:44 AM The Kernelbase.dll error would not only be because of the aircraft. I get the same error almost each time I shut off P3d. Somewhere in the computer is a file which P3d does not like, and it probably doesn't like the airbus either.
I think Aerosoft was using it as a catch all "fix".
WLP

Wayne, I don't get any errors when I exit P3D. The only way I found out about the Kernalbase.dll error was when Aerosoft pointed it out from the Win Event Error screen shot I provided. And yes, I think they are using it as a catch all.

Harold Henderson wrote: ↑10-05-2019 03:13 PM I get a "Prepar3D exe has stopped working" error every time I shut down P3D when running the Majestic Q400. That a/c only. No problem with any others. It has a conflict with a module that is getting loaded at P3D startup. I determined that by doing the below. Ted, you might want to see if this helps you zero in on what is causing your problem, too.

Harold, I also have the Majestic Q400 for P3D and do not get this error when I exit P3D, however I've not flown the Q400 in about 6mos. I'll make a flight with it to assure I still do not get this error. I'm running Pilot Ver. 1.020 of the Q400.

After I try the A320 re-install with an immediate restart, I'll give your xml edit a try if my issues are not resolved.

Harold Henderson wrote: ↑10-06-2019 03:04 PM Flew my next leg KBWI-KMIA using the Aerosoft A320 v 1.2.4.2. No Problems.

I'll load v 1.2.5.0 next week and fly another leg. This is probably the version you are downloading from Aerosoft.

Yes, you are correct. I'm running v1.2.5.0.

Loaded 1.2.5.0 and flew the A319 KMIA-CYYZ with no problems.

Harold,
You have done what Aerosoft's tech support couldn't do....my problem seems to be resolved. I'm not 100% sure what did it but I uninstalled the A320 and deleted the folders as you suggested. I rebooted my system just as a precaution then disabled my anti-virus protection before re-installing the A320. At this point I haven't done anything different than I did previously. During the re-install I did not install FSCrew. Again during one of my previous attempts I installed without installing FSCrew but it did not help. One difference, however, is that I also uninstalled FSCrew this time before the re-install. Finally after the installation I allowed the A320 installer to restart my system and I launched P3D with the virus protection still disabled.

I've now launched P3D 3 different times selecting the A320 without a crash. One of those times I flew a complete flight from KDFW-KIAH. Today I loaded the A320 again with no problem then changed to a different A320 livery. P3D crashed shortly after the new livery loaded and my first thought was the problem is back. However, I loaded P3D again and loaded that same livery and everything worked fine.

So the bottom line is the only thing I did different was to uninstall FSCrew, restart the computer immediately after the install, and keep the anti virus disabled for the first launch of P3D after installation.

Thanks again for everyone's help.

Glad you are back up and flying, Ted.

Harold Henderson wrote: ↑10-10-2019 04:53 AM Glad you are back up and flying, Ted.

Harold, I'm curious. Did you install FSCrew to your P3D A320 and did it give you problems if so?

I never installed FSCrew.

Harold Henderson wrote: ↑10-14-2019 04:09 AM I never installed FSCrew.

Yeah, sounds like a good idea.

What AA livery did you install? I have two AA liveries, texture.n124us (CFM).zip, and texture.n124us (IAE).zip, that I got from AVSIM library. I'm hesitant to use because my A320 crashing P3D started after I installed the AA livery, though I couldn't see how a livery could crash the Sim.

I don't have any AA liveries installed right now, but you can always uninstall the livery if the sim starts crashing after you install them.

Theodore Martin wrote: ↑10-08-2019 08:54 AM

Harold Henderson wrote: ↑10-05-2019 03:13 PM I get a "Prepar3D exe has stopped working" error every time I shut down P3D when running the Majestic Q400. That a/c only. No problem with any others. It has a conflict with a module that is getting loaded at P3D startup. I determined that by doing the below. Ted, you might want to see if this helps you zero in on what is causing your problem, too.

Harold, I also have the Majestic Q400 for P3D and do not get this error when I exit P3D, however I've not flown the Q400 in about 6mos. I'll make a flight with it to assure I still do not get this error. I'm running Pilot Ver. 1.020 of the Q400.

Harold, just to follow up on what I previously said I would do, I finally got around to flying the Majestic Q400 again in P3Dv4. Flew from PHNL to PHKO (Theme flight) and after parking at the gate and shutting down, I exited P3D and did not get an error. Not sure why you receive an error every time you shut down after flying the Q400....software gremlins I guest.