P3D v5.4 facilities.dll problem A320pro

[raptor84 2]

Hello everyone,

 

Hopefully some one could help me with an issue that all of a sudden I am experiencing. This issue has started to occur yesterday (24Jun24). Based on the attached error report, it appears that its a facilities.dll problem when I select the Aerosoft A320 pro, P3D suddenly crashes (after "loading terrain data, etc., etc.). When I select other aircraft, i.e. QW 787, P3D does not crash and loads normally.

 

To begin, I have P3D v5.4.9.28482 installed on a new PC (strictly only for P3D, not used for anything else) with Windows 11 Home (version 23H2). All drivers/software used, including Nvidia (latest driver 555.99 updated as of June 4, 2024) is current. This also includes the latest version of A320 (1.4.3.2) The last flight I did in P3D was on June 10, 2024. A few days I purchased and installed (22Jun24) the following new aircraft: A2A C172 and Carenado C172. 2 days ago, I've had no issues when I launched P3D when testing out both aircraft and setting up cameras, buttons/keys in FSUIPC. Every time I start up P3D, everything ran like normal. However, yesterday (24Jun24), when I launched P3D to do a flight using the Aerosoft A320pro, that's when I noticed P3D would CTD which never happened before. Below is a summary of what happened:

 

I right click and run P3D as "run as administrator." P3D launches good, seeing the splash screen, prompts me the main menu and then I select aircraft and airport per usual. Once I click the "OK" button, I see what is displayed in the attached screenshot (which to me, normally its a black screen background with the "loading terrain data box only showing then I see myself at the gate or parking position). But in this case, after the "loading terrain data" is loaded, P3D crashes on me. Even when I go to Task Manager to see if the P3D process is still running, nothing there.

 

I attached the error report. Any thoughts??

Please login to display this image.

P3D v5 CTD.txt

[mopperle 4178]

In the last years there were many reports in the P3D Forum about Crashs with this dll. In some cases uninstalling scenery addons or updating Windows solved this issue.

search their forum, maybe one of the suggestiv solution helps.

[raptor84 2]

I'll take a look at their forum. However, as stated, I think I'm going to have to uninstall A320pro because that is the one where I'm having the trouble where before I wasn't I'm able to select other aircraft, i.e. QW787 and no problems. But when I selected A320pro, that's where P3D crashes where it never did that before.

[Deltaguy24 0]

Just started having this problem as well.  The Aerosoft Airbus series has given me rock solid performance for years.  Now, all of the Airbus planes do not work at all.  The A319-321 and the A330. 

[raptor84 2]

I know right? It's been giving good performance as well. I want to say that had it not been for me installing the two C172s aircrafts, I probably wouldn't have had any issues. Now, I did post the topic of my issue on the P3D forum (link below) and I'm not really sure who is to blame, Aerosoft or P3D. I haven't tried anything based on the suggestion yet. Maybe you can give that a shot and let me know how it went with you. As far as I'm concerned, everything on my end is updated. So why are we having this issue???

 

https://www.prepar3d.com/forum/viewtopic.php?t=150796&sid=4c25db30df466fe240d1c6c6538fe920

[Deltaguy24 0]

I am at a complete loss on this one.  Did a flight 3 days ago and all worked fine.  Now when I load up any of the Aerosoft Airbus planes, the sim will load but it hangs and then just crashes to desktop.  All my other aircraft work perfectly fine, PMDG, QW, Captain Sim, Ifly.  The Aerosoft is my favorite.  I have tried everything I can think of.  Reinstalled P3d, reinstalled the airbusses, nothing is working.

 

[Deltaguy24 0]

Only thing I do notice is there was a Windows Update for Windows 11.  Maybe it broke something in the Bus

 

[raptor84 2]

Maybe, if possible, uninstall the updates. If not, try do a system restore to the day you remember when the A320 worked. That's what's I'm thinking of doing.

[raptor84 2]

2 hours ago, Deltaguy24 said:

  All my other aircraft work perfectly fine, PMDG, QW, Captain Sim, Ifly.  The Aerosoft is my favorite.  I have tried everything I can think of.  Reinstalled P3d, reinstalled the airbusses, nothing is working.

 

I'm in the same boat. All other aircrafts I have installed, in this case QW 787, load just fine. Its just an Aerosoft A320pro problem. I can select it but P3D CTD. Anyway, reinstalling P3D I say wouldn't be necessary.  I've thought about reinstalling Aerosoft and seeing that you did that and ended up having no resolution for the issue, then it would be pointless for me to go that way as well. Now, I' ve updated the C++ redistributables on my Windows 11 PC to the current version hoping that maybe, maybe that would solve it but no! Still have the issue. I even updated the driver to my graphic card as well and again, problem still exist, UGK!!

 

I'm barely coming around to getting Fenix A320 in MSFS setup even though I haven't used MSFS at all since getting it back in Nov 2023. But Aerosoft A320 was my go to aircraft and now I can't enjoy it anymore. Hopefully, but I doubt it, Aerosoft can look into this problem because clearly, Lockheed P3D isn't helping at all. They said there will not be any more updates to P3Dv5.4.

[mopperle 4178]

On the other hand, the A320 worked before something has changed on your systems. And this can be nearly everything, another addon, a Windows update (happened with me, where suddenly none of my BT devices worked anymore), any other software outside the sim….

Reading all the other posts about the crash with the facilities.dll pointed to software writing to a certain area of the memory and causing the crash. 
So the A320 might not be the problem, but just made another problem obvious.

So imho the only thing you can do is to think about what has changed and maybe make rollback of a Windows update (helped in my case), uninstall newly installed software….

But maybe Aerosoft support got another idea.

[raptor84 2]

12 hours ago, mopperle said:

On the other hand, the A320 worked before something has changed on your systems. And this can be nearly everything, another addon, a Windows update (happened with me, where suddenly none of my BT devices worked anymore), any other software outside the sim….

Reading all the other posts about the crash with the facilities.dll pointed to software writing to a certain area of the memory and causing the crash. 
So the A320 might not be the problem, but just made another problem obvious.

So imho the only thing you can do is to think about what has changed and maybe make rollback of a Windows update (helped in my case), uninstall newly installed software….

But maybe Aerosoft support got another idea.

I've been banging my head against the wall trying to figure out what it could be. I figure after installing the two C172s aircraft, that it was the cause and by uninstalling them, it would solve the issue.  Yes, I agree it could something outside of the sim like a windows update. Since my last flight in the sim, (Jun 10th flying the QW787) until June 22nd, it should be hard for me to see what changes my PC did (i.e. windows update) that may have caused the issue. Its very well could be a windows update that may have causing the issue.

 

I don't think the folks over at Aerosoft support care to solve the problem. In my opinion, they probably more focus, care about more about MSFS than their A320 in P3D.

[Tom 456]

I'd recommend searching for "Check for updates" in the Windows search bar, and then clicking "Update history". It'll give you a list of all updates recently installed, along with the date. It'll be useful to know if you ( @raptor84@Deltaguy24) share any of the same updates, as it could help confirm if this is some kind of Windows update issue.

 

45 minutes ago, raptor84 said:

I don't think the folks over at Aerosoft support care to solve the problem. In my opinion, they probably more focus, care about more about MSFS than their A320 in P3D.

While the P3D line of buses doesn't receive feature updates anymore, we still have someone dedicated to just P3D/FSX (and older) support. I'd always recommend dropping a ticket if you can, as it's generally a lot easier for us to solve issues there.  

[raptor84 2]

On 6/29/2024 at 6:44 PM, Deltaguy24 said:

Only thing I do notice is there was a Windows Update for Windows 11.  Maybe it broke something in the Bus

 

Any updates on your end?? Are you still having the same issue because I still am. I tried out a suggestion by a member in the P3D forum and he said to delete the files in the Shade folder which I did and I still have the same issue. Once the loading terrain data is complete, P3D CTD.

 

Please login to display this image.

 

 

[vonmar 8]

@raptor84

 

Previously Tom (Administrator) mentioned :

"I'd always recommend dropping a ticket if you can, as it's generally a lot easier for us to solve issues there.   "

 

Have you done that?

 

[raptor84 2]

11 minutes ago, vonmar said:

@raptor84

 

Previously Tom (Administrator) mentioned :

"I'd always recommend dropping a ticket if you can, as it's generally a lot easier for us to solve issues there.   "

 

Have you done that?

 

No. I've now since uninstalled it.

[Deltaguy24 0]

It was a Windows 11 update that messed mine up.  I uninstalled that update and it all works fine again.

[raptor84 2]

42 minutes ago, Deltaguy24 said:

It was a Windows 11 update that messed mine up.  I uninstalled that update and it all works fine again.

Do you happen to remember which windows 11 update was it?? I can see I have various updates that occurred on the 24th. Any particular one???

[Balogh Ádám 49]

I have exactly the same problem, same error code, same offset, everything is the same. Any solution? Which Windows update do I have to remove?

 

[raptor84 2]

11 hours ago, Balogh Ádám said:

I have exactly the same problem, same error code, same offset, everything is the same. Any solution? Which Windows update do I have to remove?

 

I didn't uninstall a window update. What I did was uninstall the Aerosoft A320pro then reinstalled it and it seemed to take care of the problem. However, I don't know if that would be the case for you. If you haven't seen this post below, take it look. I provide more details and update status there.

 

https://www.prepar3d.com/forum/viewtopic.php?t=150796&sid=4c25db30df466fe240d1c6c6538fe920