Hello, I have P3DV5 and when I start the program, it looks fine. Then I get to the page on which you select aircraft, location and time. I select any, the screen shifts to black with the progress bar moving up, when it gets to about 90% it just stops and I get back to the windows desktop. No matter which airport I choose, the same thing happens. I remember in previous versions, you could some of the cfg's o ini's and let the software rebuild them at start up.

I can' remember which files it was.

Thanks in advance 

 

Juan

Juan

C:\Users\xxxx\AppData\Roaming\Lockheed Martin\Prepar3D v5.                Delete the Prepar3D.cfg so it can rebuild.

 

Edited May 25, 20215 yr by Benzhangar

There's also a script in your main P3D folder called "Delete Generated Files" that you can run to force P3D to regenerate all of those files.  Might be worth a shot.

There are a couple of semi-recent nVidia drivers that will really booger up P3D, as well.  Graphics anomalies like stuff going black makes me wonder if that might be your problem.

466.27 seems to be a good one on my two sim machines (one with a 3090, the other a 1080Ti).

As above.. most likely it is the nvidia drivers.

S.

9 minutes ago, simbol said:

As above.. most likely it is the nvidia drivers.

S.

 It seems the last three updated drivers are not well configured with P3D.  CTD's, Mouse movement lag and the dreaded crash at startup. I rolled back to 461.72 and all flights are currently flawless.

I am running the latest Nvidia drivers and Windows 2021-05 update and P3Dv5 runs fine. could be an addon.

9 hours ago, G-RFRY said:

I am running the latest Nvidia drivers and Windows 2021-05 update and P3Dv5 runs fine. could be an addon.

One thing that also rarely gets mentioned is that video drivers are written to work in conjunction with the latest Windows WDDM low-level display system driver at the time of release.  And likewise, the WDDM drivers go hand-in-hand with the current BIOS and motherboard system drivers.  If you use a new video driver on an old OS version, or vice versa, that can be be a source of problems, as can be a new OS version on a system with a 2-3 year old BIOS.  I suspect that these mismatches may account for some of the varied experiences people have with different drivers.

 

The load progress bar getting to ~90% and then CTDing sounds to myself to be more of a file issue, as in a corruption or incompatible file like an Ai or scenery model, being as the ~90% range is about when AI traffic is being loaded.

The first thing I do when troubleshooting such types of issues are non destructive types of tests.

For Example.

Delete the Shader and scenery index files as these are automatically recreated on the fly. These are located in the following paths.

Shaders:     ~\AppData\Local\Lockheed Martin\Prepar3D v3/4/5\Shaders

Index Files: ~\ProgramData\Lockheed Martin\Prepar3D v3/4/5\SceneryIndexes_x64

If not resolved then move onto renaming config files e.g. prepar3d.cfg file to enable a new one to be regenerated. I recommend renaming because they do hold the current config settings and there maybe a need to reference the values.

Then processes of elimination such as setting traffic values to zero to help narrow down the problem.

There may also be a need to disable addins etc.

Cheers R