reported DCS Crash in MP - secondary shadows

[MAXsenna]

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

Good to know!

Sent from my SM-A536B using Tapatalk

[Dentedend10]

Hi! I had the same issue on Pimax Crystal OG. Can confirm, turning off the Secondary Shadows fixed it.

Edited Sunday at 08:18 AM by Dentedend10

[Tshark]

Myself and friend had the same issue.  Both using Pimax Supers.  Turning off Secondary Shadows fixed it as well.

[Andrei]

Same problem. Pimax Crystal. And turning off secondary shadows helped as well.

Looks like it's VR specific. Crash log is the same every time

OS-Version: 10.0.26100 () 0x100-0x1
0x00000000000a2782 (GraphicsCore): render::SecondaryShadowmapModule::collectShadowmaps + 0x42
0x00000000000a121b (GraphicsCore): render::SecondaryShadowmapModule::SecondaryShadowmapModule + 0x2AB
0x00000000000a2b96 (GraphicsCore): render::SecondaryShadowmapModule::collectShadowmaps + 0x456
0x000000000005d0e2 (GraphicsCore): render::BaseRenderingPass::prePass + 0x22
0x000000000005c627 (GraphicsCore): render::RenderGraph::lightsPrePass + 0x67
0x000000000016d8e4 (Visualizer): smSceneManager::regLua + 0x11C4
0x0000000000156ef4 (Visualizer): smCamera_Implement::getClipRegion + 0x1CC74
0x000000000014076c (Visualizer): smCamera_Implement::getClipRegion + 0x64EC
0x000000000015b602 (Visualizer): smSceneManager::DestroySceneManager + 0x1222
0x00000000000331e1 (edCore): ed::thread::_get_current_thread_id + 0x71
0x00000000000037b0 (ucrtbase): wcsrchr + 0x150
0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17

 

Edited Sunday at 01:16 PM by Andrei

[YoYo]

No problem for me so far (but Quest), turn off all mods and check it again. From what I see it applies more to Pimax owners, so maybe there is some software problem with the update from Pimax?

[Andrei]

Can anyone check - I can't ATM - if the problem is only there when using QuadViews? So if Secondary shadows on and quadviews off - does it still crash?

[BIGNEWY]

this issue has been reported and a fix should be coming soon 

thank you