P3D Hotfix 5.1 causes DXGI Graphics card error

[ajra1966]

Hi Jorgen,

in my case all ENV updates are there via EnvDir and also the new ASCA 121220, all other addons are updated and bathymetry is off.

Thank you

[Martyson]

@ ajra1966 ,

The General Debugging Steps are here for your review:
https://www.prepar3d.com/forum/viewtopi ... 2&t=123246

Uninstalling/Deactivating Prepar3D:
https://www.prepar3d.com/forum/viewtopi ... 2&t=125187

Downloading and Installing Prepar3D:
https://www.prepar3d.com/forum/viewtopi ... 2&t=120676

[petakas]

Nice informative video on DX12 and P3D https://youtu.be/UmqcT94d3qM

[Martyson]

@ petakas ,

Do you have DXGI errors ?

[ajra1966]

Hi,

after looking at the video the was shared above, I understood that the issue with DXGI is related to the way DirectX 12 handles VRAM. I had my textures at 4096 resolution which was consuming lots of VRAM. I decided to reduce it to 2048 and performed a flight from LFPG (Taxi2Gate) to EGLL (OrbX TE + Aerosoft EGLL) and monitored how match VRAM was being used all the way. It was clear that when getting low on EGLL approach the number rose to around 6.1 GB (GPU is a 1080 with 8 GB VRAM). This alowed me to complete the flight without a DXGI error. The VRAM at LFPG was around 4 GB but the scenery is no so "hungry" and no OrbX TE there.
This was only one flight, I know, but it hit the most complex combination of scenery I have (OrbX + AS + ASP3D + ASCA + FSLabs A320 + night flight) so I have some confidence (only some!) that DXGI errors won't happen many more times.

Enjoy!

PS1: after closing P3DV5.1 the magic number came down to 0.2! It is amazing the amount of VRAM that the simulator consumes.
PS2: It is a step back that now we have to manage VRAM ourselves if we don't want to have crashes when with DirectX 11 that was done automatically. It could get slow but wouldn't crash due to lack of VRAM.

[TSC6440]

Hi,
Using aircfraft from major manufacturers, 744, A3XX professional, 787.
The only one 100% successful with P3DV5.1 HF1 is the 744 with high P3D settings.
The others are almost everytime prone to DXGI_ERROR_DEVICE_HUNG with quite lower P3D settings and GPU memory 4.0/10 gb 30 fps.
Nvidia 2080ti. all updates installed.
ASP3D ORBX Various payware sceneries.
Regards,

[quid21]

Hi,

after looking at the video the was shared above, I understood that the issue with DXGI is related to the way DirectX 12 handles VRAM. I had my textures at 4096 resolution which was consuming lots of VRAM. I decided to reduce it to 2048 and performed a flight from LFPG (Taxi2Gate) to EGLL (OrbX TE + Aerosoft EGLL) and monitored how match VRAM was being used all the way. It was clear that when getting low on EGLL approach the number rose to around 6.1 GB (GPU is a 1080 with 8 GB VRAM). This alowed me to complete the flight without a DXGI error. The VRAM at LFPG was around 4 GB but the scenery is no so "hungry" and no OrbX TE there.
This was only one flight, I know, but it hit the most complex combination of scenery I have (OrbX + AS + ASP3D + ASCA + FSLabs A320 + night flight) so I have some confidence (only some!) that DXGI errors won't happen many more times.

Enjoy!

PS1: after closing P3DV5.1 the magic number came down to 0.2! It is amazing the amount of VRAM that the simulator consumes.
PS2: It is a step back that now we have to manage VRAM ourselves if we don't want to have crashes when with DirectX 11 that was done automatically. It could get slow but wouldn't crash due to lack of VRAM.

ALso just watched that - very interesting. I've just switched back on bathemetry and enhanced atmospherics and increased texture resolution to 4096, BUT reduced my FPS target from 60 to 30 and it hasn't crashed.

Is the issue therefore, with DX12 or the card or P3D for not limiting itself?

[TSC6440]

Hi,
Processed as indicated by quid21 and made a 30 min test flight.
It went just as expected with A3XX A/C without previous reported DXGI failure.
Sounds good and will report further tomorrow with a longer flight.
Regards

[TSC6440]

Hi,
100% DXGI failures with quid inputs this morning and back to previous settings.
Regards.

[MarkOtten1996]

Hi,

Just bought P3D. Installed PMDG 737, FlyTampa Amsterdam and Orbx Basepack. After startup a DXGI Error popped up in the main screen. I don't know what to do. Can someone help me out?

[JorgenSA]

"Installed PMDG 737, FlyTampa Amsterdam and Orbx Basepack."

Was P3D running OK before you installed those? And what are your system specifications?

Jorgen

[MarkOtten1996]

P3d worked fine.

I have 3600 AMD, 2060 GTX and 32 GB RAM

[JorgenSA]

So your installation was OK, and your hardware is fine. Good!

That means we should look at your settings.

Under Options/Display, check the frame rate and set to 30, and texture resolution to 1024x1024.

Under Options/World, uncheck the checkboxes for Enhanced Atmospherics and Bathymetry.

Shut P3D down, wait a moment, fire it back up and see if it runs now.

I am kinda brutal in lowering the settings, but the aim is to get things running and the you can increase the settings gradually.

I trust that Windows 10 and your AMD drivers are up to the latest level?

Jorgen

[MarkOtten1996]

So your installation was OK, and your hardware is fine. Good!

That means we should look at your settings.

Under Options/Display, check the frame rate and set to 30, and texture resolution to 1024x1024.

Under Options/World, uncheck the checkboxes for Enhanced Atmospherics and Bathymetry.

Shut P3D down, wait a moment, fire it back up and see if it runs now.

I am kinda brutal in lowering the settings, but the aim is to get things running and the you can increase the settings gradually.

I trust that Windows 10 and your AMD drivers are up to the latest level?

Jorgen

I got it at startup of the main screen.
I tried everything you listed above. No change. All drivers are up to date.

[MarkOtten1996]

So your installation was OK, and your hardware is fine. Good!

That means we should look at your settings.

Under Options/Display, check the frame rate and set to 30, and texture resolution to 1024x1024.

Under Options/World, uncheck the checkboxes for Enhanced Atmospherics and Bathymetry.

Shut P3D down, wait a moment, fire it back up and see if it runs now.

I am kinda brutal in lowering the settings, but the aim is to get things running and the you can increase the settings gradually.

I trust that Windows 10 and your AMD drivers are up to the latest level?

Jorgen

I got it at startup of the main screen.
I tried everything you listed above. No change. All drivers are up to date.

I think I found the solution. It was MSI Afterburner.