reported DCS Crash in MP - secondary shadows

[Cleric812]

Hello all,

I seem to be having a rather odd issue. Whenever I enter into any multiplayer server and select the MiG-29A Fulcrum my DCS locks up completely. Asking me to send a crash report, which I have multiple times.

I can use other modules on the same servers without issue.

I do see other players able to fly around in the new MiG-29A Fulcrum.

I can use the module in SP, both instant action and training missions attempted.

 

Has anyone experienced the same issues? If you need further info please let me know, I will add the crash reports to this message.

 

Looking forward to flying this magnificent module soon since it has been my favorite since I first saw one years ago IRL,

 

Kind regards,

 

Vincent

dcs.log-20250918-085805.zip dcs.log-20250918-093351.zip dcs.log-20250918-094021.zip dcs.log-20250918-105932.zip dcs.log-20250918-110453.zip dcs.log-20250918-111127.zip dcs.log-20250918-124810.zip

[BIGNEWY]

Hi, 

do you use any mods or edits? Or work with editing tools?

the crash seems to imply a texture conversion issue

Quote

2025-09-18 11:10:07.782 WARNING SCENERENDERER (19208): render graph: forced to update texture desc of already created texture on the same frame (0)
2025-09-18 11:10:09.973 ERROR_ONCE DX11BACKEND (26392): texture 'ptb-1150_spec' not found. Asked from ''
2025-09-18 11:10:10.171 WARNING BACKENDCOMMON (26392): Need to reprocess [DDS] image 'mods/aircraft/mig-29-fulcrum/cockpit/textures/mig29_cpt_textures/MiG29_Glass_dam_NRM.dds'. Reason: Conversion requires - expanded pixel size, setting alpha to known value. Source is an 8:8:8 (24bpp) format
2025-09-18 11:11:26.890 ERROR   GRAPHICSCORE (19208): Failed assert `count < c`
2025-09-18 11:11:26.947 INFO    EDCORE (19208): try to write dump information
2025-09-18 11:11:27.126 INFO    EDCORE (19208): # -------------- 20250918-111127 --------------
2025-09-18 11:11:27.127 INFO    EDCORE (19208): DCS/2.9.20.15010 (x86_64; MT; Windows NT 10.0.26100)
2025-09-18 11:11:27.128 INFO    EDCORE (19208): D:\Program Files\Eagle Dynamics\DCS World\bin\GraphicsCore.dll
2025-09-18 11:11:27.129 INFO    EDCORE (19208): # C0000005 ACCESS_VIOLATION at 00007ffbe12f2782 00:00000000
2025-09-18 11:11:27.130 INFO    EDCORE (19208): SymInit: Symbol-SearchPath: 'D:\Program Files\Eagle Dynamics\DCS World\bin;', symOptions: 532, UserName: 'Vince'
2025-09-18 11:11:27.131 INFO    EDCORE (19208): OS-Version: 10.0.26100 () 0x300-0x1
2025-09-18 11:11:27.132 INFO    EDCORE (19208): 0x00000000000a2782 (GraphicsCore): render::SecondaryShadowmapModule::collectShadowmaps + 0x42
2025-09-18 11:11:27.133 INFO    EDCORE (19208): 0x00000000000a121b (GraphicsCore): render::SecondaryShadowmapModule::SecondaryShadowmapModule + 0x2AB
2025-09-18 11:11:27.133 INFO    EDCORE (19208): 0x00000000000a2b96 (GraphicsCore): render::SecondaryShadowmapModule::collectShadowmaps + 0x456
2025-09-18 11:11:27.133 INFO    EDCORE (19208): 0x000000000005d0e2 (GraphicsCore): render::BaseRenderingPass::prePass + 0x22
2025-09-18 11:11:27.133 INFO    EDCORE (19208): 0x000000000005c627 (GraphicsCore): render::RenderGraph::lightsPrePass + 0x67
2025-09-18 11:11:27.133 INFO    EDCORE (19208): 0x000000000016d8e4 (Visualizer): smSceneManager::regLua + 0x11C4
2025-09-18 11:11:27.134 INFO    EDCORE (19208): 0x0000000000156ef4 (Visualizer): smCamera_Implement::getClipRegion + 0x1CC74
2025-09-18 11:11:27.134 INFO    EDCORE (19208): 0x000000000014076c (Visualizer): smCamera_Implement::getClipRegion + 0x64EC
2025-09-18 11:11:27.134 INFO    EDCORE (19208): 0x000000000015b602 (Visualizer): smSceneManager::DestroySceneManager + 0x1222
2025-09-18 11:11:27.134 INFO    EDCORE (19208): 0x00000000000331e1 (edCore): ed::thread::_get_current_thread_id + 0x71
2025-09-18 11:11:27.134 INFO    EDCORE (19208): 0x00000000000037b0 (ucrtbase): wcsrchr + 0x150
2025-09-18 11:11:27.134 INFO    EDCORE (19208): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17
2025-09-18 11:11:27.476 INFO    EDCORE (19208): Minidump created.

 

[Cleric812]

Interesting, I have used some texture mods in the past but haven't done so since upgrading my pc to a new GPU. The mod was completely uninstalled and the MiG-29 was not yet released when I dabbled with texture mods.

I also wanted to add that I did do a repair build earlier and deleted all shaders in the saved games folder. Neither of these steps helped.

I will delete the MiG-29 files and redownload it. Seems odd this would cause a crash in MP but not in SP.

[BIGNEWY]

How long ago did you update your display driver?

I would try a fresh driver install to see if it helps

thank you 

Try turning off SSLR out of curiosity and let me know if thee is a difference 

[Cleric812]

Just had a try after deleting the module and reinstalling it. It appears I discovered a new variable, it works in normal mode but not VR.

Also DCS crashed in SP using VR so it would appear it might be related somehow to VR.

Last display driver update was 4-5 days ago, running the latest nvidia drivers (581.29)

Will try with SSLR off now.

[Cleric812]

Just a quick note, the thread is marked remove user mods. There are no mods installed at the moment whatsoever.

[BIGNEWY]

Ive adjusted the tag dont worry. 

Can you try this. 

rename your folder in saved games DCS ( Keep it is a back up )

restart DCS and allow it to create new shaders. 

then test and attach fresh logs 

thanks

[Makakas]

Same problem

 

[BIGNEWY]

3 minutes ago, Makakas said:

Same problem

 

please add logs if it is the same issue, if not please make a new thread 

 

[Makakas]

dcs.log-20250918-160236.zip

[Cleric812]

Just tried it with SSLR off, no joy.

Deleted the DCS saved games folder, still no joy

dcs.log-20250918-165629.zip

[BIGNEWY]

thanks for the logs, I will ask the team to take a look 

[Moezilla]

8 minutes ago, Cleric812 said:

Just tried it with SSLR off, no joy.

Deleted the DCS saved games folder, still no joy

dcs.log-20250918-165629.zip 3.89 MB · 1 download

Just going from the crash and the log I would suggest disabling the following: secondary shadows, SSS (screen space shadows, iirc?), SSAO, and SSLR; which all show as "ON" in your log, and the crash directly refers to "secondaryshadowmaps".

It wouldn't hurt to reduce shadows to medium as well, which would also reduce VRAM and CPU load a little.

[Cleric812]

Hello all,

Just got back from a total reinstall of DCS. The initial run using my previous settings resulted in a crash, however @Moezilla you managed to get it right, when I turn secondary shadows off, it runs just fine. So it would appear that there is a problem with the Fulcrum and secondary shadows. SSS, SSAO and SSLR all run fine, it seems to be just the secondary shadows which causes the issue.

@BIGNEWY I hope this troubleshooting helps and the team can have a more focused look at this and see if they can fix the secondary shadows issue.

Just to be complete I added my crash log for the crash after a total reinstall with the secondary shadows on.

 

Now it's time to finally enjoy this gorgeous looking module and live my childhood fantasy

Thank you all for the help and quick replies.

 

Vincent

dcs.log-20250919-070218.zip

Edited Friday at 07:14 AM by Cleric812

[BIGNEWY]

thanks for giving us more clues we will take a look at secondary shadows and see if we can reproduce 

[Redacuragsr]

I downloaded my Mig-29A module and was able to play it for half a day, then I turned DCS off, and then when I restarted DCS and tried to load any mission that has the MiG-29A module in it, it would then take forever to load and then crash every time.  This only happens in VR and only with the MiG-29A module for some reason. Everything else works fine. I have attached my crash logs in hopes that someone can help

dcs.log dcs.log.old dcs.20250919-184054.crash

[Baseline]

Same problem for me too. Running the Pimax Crystal Super.

Game crashes just before I try to click the fly button.

[Raven (Elysian Angel)]

Game crash or black screen? I had serious black screen problems, but deleting the Mission Editor folder in Saved Games and running a repair fixed that.

It might be worth a try.

[MAXsenna]

Game crash or black screen? I had serious black screen problems, but deleting the Mission Editor folder in Saved Games and running a repair fixed that.
It might be worth a try.

Did you backup your logbook first?
People might be pissed if they just randomly delete it.

Sent from my SM-A536B using Tapatalk

[Raven (Elysian Angel)]

4 minutes ago, MAXsenna said:

Did you backup your logbook first?
People might be pissed if they just randomly delete it.

Sent from my SM-A536B using Tapatalk
 

I did not. It crossed my mind, but I looked for the file and my foggy head couldn’t find it. Then I realised I don’t mind it gets reset so I just deleted the folder anyway.

[Makakas]

 

[Redacuragsr]

1 hour ago, Baseline said:

Same problem for me too. Running the Pimax Crystal Super.

Game crashes just before I try to click the fly button.

Yep I’m running on the Pimax crystal super too

Edited Friday at 10:48 PM by Redacuragsr

[Redacuragsr]

1 hour ago, Raven (Elysian Angel) said:

Game crash or black screen? I had serious black screen problems, but deleting the Mission Editor folder in Saved Games and running a repair fixed that.

It might be worth a try.

I had black screen too, the plane loaded partially first, then black screen and crashed.  I did a repair, reinstalled all my Pimax stuff but it’s still doing it.  I’ll try deleting the mission editor folder and try it again.  Thanks for the idea.

[MAXsenna]

I had black screen too, the plane loaded partially first, then black screen and crashed.  I did a repair, reinstalled all my Pimax stuff but it’s still doing it.  I’ll try deleting the mission editor folder and try it again.  Thanks for the idea.

If you want to keep your flight records. RENAME the folder.

Sent from my SM-A536B using Tapatalk

[Redacuragsr]

2 hours ago, Makakas said:

 

Disabling secondary shadows fixed it, thank you!

1 hour ago, MAXsenna said:

If you want to keep your flight records. RENAME the folder.

Sent from my SM-A536B using Tapatalk
 

Good idea, but renaming the folder didn’t fix anything for me, however when I turned off secondary shadows everything went back to normal 

Edited Saturday at 12:24 AM by Redacuragsr