Oliver,

I would like to post on this forum an issue that I am having on P3D V4.1. Although I don' t think the issue is related to your Addon Organizer (I have posted it also on other forums), the reason I am posting here is because the problem started to appear immediately after I update the Addon Organizer to the latest version (1_26_b01 ) and seems to be related to scenery so I would like also to hear your thoughts and hopefully have some troubleshooting suggestions here.

I am running P3D V4.1 on Win10 Home (without the latest Meltdown patches as I have disabled WIndows update) and the problem appears with any addon aircraft loaded at an addon airport.  When I launch a flight at an addon airport, it loads everything correctly and then it starts the initialization of the airplane, and the green bar with the seconds counter appears on top of the screen. Exactly two seconds after it starts, the green bar disappears and the initialization stops. The Sim menu is still functional and if I quit the Sim, the Sim has a CTD with a "ucrtbase.dll module fault" (as reported by appcrashview). It is not specific to a particular addon aircraft However if I a load a previously saved flight everything initializes correctly and the sim runs flawlessly, but then it CTD upon exit (for the same ucrtbase.dll fault).

I have googled "ucrtbase.dll ctd" and it appears that it is something related to Microsoft Visual C++, but I have followed the Avsim CTD guide for this case, and reinstalled all the Microsoft Visual C++ but nothing has changed.

Again, the only change I made to the Sim before this issue started was the update of the Addon Organizer to version 1_26_b01. 

I would like your view on this

Thanks

 

Ezio

 

 

 

Hello Ezio,

sorry no idea. The first question that comes to mind is: what green bar with seconds counting down??? I don't have that. I have only seen these types of info bars from specific aircraft, like PMDG, or addons like GSX. There those bars are covering the initialization process of the programmatic logic of the aircraft or addon. So if the simulator crashes then, something must have gone wrong there I suppose - a question which goes directly to the developer of the addon in question.

Generally speaking though, merely installing the AddonOrganizer will do nothing to your simulator - it can't. And in any case, the tool does not mess with your core config files, it only handles addon configuration.

The only change that was made in the 1.26 is this one:

Quote

Date 19.01.2018
Version 1.26 b01
- Bugfix: New packages not properly initialized when adding scenery

So unless you have added new scenery, the tool has been the same as it was before.

If you were using it, then it might have happend that you have either activated an addon that was not there before (or it was disabled), or you may have indavertendly removed a component that should be there.

If you want to go back to the situation before using the tool: the P4AO creates a file called "*_orig" saving the original file of everything that it changed (=all the XML files and the three .cfg files). You can just rename them back - or, if there is a lot of them, I can add a button real quick that copies all those original files back the way that they were. 

On another note: the simulator crashing on startup or shutdown is often caused by programmatic addons that are attaching to SimConnect. If an addon has been compiled with th 4.0 libraries, then it will crash very often when the simulator shuts down (that was one of the issues resovled in 4.1, but the addon needs to be recompiled for that version.)

I have a similar problem when I use Rex SkyForce. If I keep that tool running, and it updates the cloud structures alongside ACSA and AS4, then the sim will always crash. Sometimes right away, sometimes after a few minutes - but every single time. I have to keep SkyForce disabled, otherwise I can't fly.

Best regards

Oliver,

thanks for your answer. You made me realize something which I had completely forgotten: another thing I installed very recently is Rex Sky Force and I am using it just for the Clouds textures and sync, as I am using AS16 for weather engine.

I am not 100% sure if my issues started immediately after I installed SF but for sure this is interesting based on what you wrote in your answer. I will make some more investigation in this direction. Just one question: when you say "I have to keep SF disabled", what do you mean exactly ? You just don't launch it while P3D is running or what else ?

Thanks

 

Ezio 

2 hours ago, Eziocin said:

Oliver,

thanks for your answer. You made me realize something which I had completely forgotten: another thing I installed very recently is Rex Sky Force and I am using it just for the Clouds textures and sync, as I am using AS16 for weather engine.

I am not 100% sure if my issues started immediately after I installed SF but for sure this is interesting based on what you wrote in your answer. I will make some more investigation in this direction. Just one question: when you say "I have to keep SF disabled", what do you mean exactly ? You just don't launch it while P3D is running or what else ?

Thanks

 

Ezio 

Hello Ezio,

currently I don't even start Rex SkyForce, I am back with all-ASCA. Initially I made that integrated setup where SF is supplying the clouds and ASCA the sky (provided by ENVTEX), with AS4 for the weather. I soon started to notice strange performance issues. But last weekend it started crashing every time. My plane was the Milviz Otter, just sitting on a parking spot at PAPH with ORBX Southern Alaska. I just started the sim and left it sitting there, to see what the weather was like, while I did some other work. When I looked back at the screen I realized that P3D was gone. At first I didn't think much of it, but as it turned out, keeping SF running crashes the sim consistently. Not always at the same time though, somtimes it was holding on for a couple of minutes. I found a few forum posts telling the same story on the net, but nothing conclusive.

My P3D system as reference: i9 7900x @4,3Ghz, 64 GByte RAM, Asus GTX 1080Ti, SSDs only, Windows 10 Pro, freshly installed when P3D 4.1 came out. 

Best regards

Hello Oliver,

Welcome to the club ! I (and some other people) have a similar issue when SF3D is running !

I found that when P3D crash with no message when SF3D is active, it launche dxdiag.exe just before closing every thing. Check if you also find "dxdiag.txt" (with the date/time of crash) in your C:\Users\xxxx\AppData\Roaming\Lockheed Martin\Prepar3D v4\

Two topics are open at REX and one at Prepar3d.com (apparently some users have the same kind of problem with different weather engines).

Hope they will fix it soon.

Gérard