Jump to content

Recommended Posts

Posted

Hello everyone!
I hope you can help me.
Yesterday, I downloaded and installed the new DCS update 2.9.21.16362 (STEAM).
Since then, I've been having problems with the Normandy map 2.0.
I own  DCS: Normandy 2.0
           DCS: Normandy 2.0 Full by Ugra Media
           DCS: Normandy 2.0 UP Grade 2

When I place a Cold War aircraft on the map (A10), I can 
fly normally on the map. 
When I place a World War II aircraft (P 51),  DCS crashes.
When I try to load my own missions, the game crashes.
The mission starts to load, but before it is fully loaded, the game crashes.
If I load a purchased campaign that takes place on the Normandy map, the game crashes.

I have done the following:

Steam: Checked files for errors. 

Reinstalled Normandy 2.0.

Uninstalled mods.

Created log file, attached.

Translated with DeepL.com (free version)

dcs.log

Posted
18 minutes ago, baloueb123 said:

Since then, I've been having problems with the Normandy map 2.0.
I own  DCS: Normandy 2.0
           DCS: Normandy 2.0 Full by Ugra Media
           DCS: Normandy 2.0 UP Grade 2

 

WTF?

For Work / Gaming: 28" Philips 246E Monitor - Ryzen 7 1800X - 32 GB DDR4 - nVidia RTX1080 - SSD 860 EVO 1 TB / 860 QVO 1 TB / 860 QVO 2 TB - Win10 Pro - TM HOTAS Warthog / TPR / 2xMDF

Missing modules:
Mig-29A / C-130J / F4UD-1 / F-5E Remastered / OH-58D / CH-47F / F-16C / F-14 / Mi-24P / JF-17 / Fw-190 A-8 / I-16 / CE-2 / Yak-52 / FC2024
Cold War Germany / Afganistan / Iraq

Posted (edited)

Summary

Normandy terrain load triggered heavy graphics work (big clipmaps, many textures) and logged: "No suitable driver found to mount mods/terrains/normandy/assets/assetstextures.zip".
Engine forced a huge preload (preloadRadius=100000) which loaded many terrain/texture assets at once.
Immediately after heavy terrain/texture processing the log shows repeated "DX device removed. Reason: 0x887A0006" and a GraphicsCore crash — indicating GPU/driver/device loss likely caused or exposed by the Normandy load and missing/corrupt terrain assets.

Quick targeted actions

  • Temporarily remove/rename Mods/terrains/Normandy and re-run DCS. If stable, Normandy assets are implicated.
  • Reinstall/replace Mods/terrains/normandy/assets/assetstextures.zip (ensure it’s a valid, uncorrupted archive).
  • Lower preloadRadius (from 100000 down to default or ~3000–10000) before loading Normandy to reduce GPU pressure.
  • Disable overlays (Steam/recording) and update or rollback AMD GPU drivers; test with stock clocks (no overclock).
  • Run with user mods removed (Saved Games\DCS\Mods and Mods) to isolate Normandy vs aircraft/mod interactions (P-51D texture warnings appeared during terrain init).
  • Collect diagnostics if repro persists: dxdiag, Windows Event Viewer (display/driver errors), DCS minidump and dcs.log around the Preload() → first "DX device removed" timing, and submit to DCS support with these files.
Edited by plott1964

PC specs:

Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/Multiple M.2 SSD Drives/T.Flight HOTAS X/Pimax Crystal Light

Posted (edited)
41 minutes ago, baloueb123 said:

Excuse me, what is WTF?

I am German, my English is not very good

When This Friday? 😉

Alternatively, Was Zumba teufel.

Edit: I just translated that back and it says it’s something about devil so no. WTFs happening to translator 😄

 

Edited by Slippa
  • Like 2
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...