resolved Game crash after selecting Aircraft (only in VR)

[BalthasarDE]

Hello, I've been away for about a week and wanted to do some helicopter flying again. After logging into various servers, I keep getting stuck after selecting my aircraft and a crash message appears.
I then tried flying a campaign mission and a custom mission, but I always get the same crash message. The log says something about missing Voice_Chat.log or something similar.
I've tried repairing the game via Steam, updating the game version to the last version and then back to the current version, and even restarting the computer hasn't worked. Now I'm a bit confused, when I start DCS without my VR headset, everything works strangely. So the problem only exists with my VR headset.
I hope for your help.

I use a Pimax Crystal OG
Nvidia RTX4080
AMD Ryzon 7 7800X3D
MSI MPG X670E Carbon Wifi
Kingston Fury DDR5-6000 64 GB
System drive: Crucial T700 1TB
Game drive: Samsung SSD 990 EVO Plus 4TB

My latest Log:dcs.log-20250915-112523.zip

[BIGNEWY]

Hi, 

can you remove all unofficial mods, 

then delete metashader2 and fxo folders in saved games dcs folder.

Then run a verify in steam. 

 

The crash

2025-09-15 11:25:22.672 ERROR   GRAPHICSCORE (47112): Failed assert `source.getDesc().msaa == settings.msaa && dest.getDesc().sizeX == source.getDesc().sizeX && dest.getDesc().sizeY == source.getDesc().sizeY`
2025-09-15 11:25:22.718 WARNING LOG (75172): 1 duplicate message(s) skipped.
2025-09-15 11:25:22.718 ERROR   SCENERENDERER (47112): Failed assert `depthBuffer.getDims() == dims && depthBuffer.getMSAA() == msaa`
2025-09-15 11:25:22.718 ERROR   DX11BACKEND (47112): depth buffer mainDepthBuffer2 (932x1028) must be the same size as color targets (788x932)
2025-09-15 11:25:22.718 ERROR   DX11BACKEND (47112): Failed assert `false && "depth buffer must be the same size as color targets"`
2025-09-15 11:25:22.961 INFO    EDCORE (47112): try to write dump information
2025-09-15 11:25:23.159 INFO    EDCORE (47112): # -------------- 20250915-112523 --------------
2025-09-15 11:25:23.159 INFO    EDCORE (47112): DCS/2.9.19.13478 (x86_64; MT; Windows NT 10.0.26100)
2025-09-15 11:25:23.160 INFO    EDCORE (47112): D:\SteamLibrary\steamapps\common\DCSWorld\bin\dx11backend.dll
2025-09-15 11:25:23.161 INFO    EDCORE (47112): # C0000005 ACCESS_VIOLATION at 00007ffb6306aa57 00:00000000
2025-09-15 11:25:23.162 INFO    EDCORE (47112): SymInit: Symbol-SearchPath: 'D:\SteamLibrary\steamapps\common\DCSWorld\bin;', symOptions: 532, UserName: 'KarlS'
2025-09-15 11:25:23.163 INFO    EDCORE (47112): OS-Version: 10.0.26100 () 0x100-0x1
2025-09-15 11:25:23.164 INFO    EDCORE (47112): 0x000000000001aa57 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37
2025-09-15 11:25:23.164 INFO    EDCORE (47112): 0x00000000000195f8 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x00000000000132d7 (SceneRenderer): BRDFRenderer::onWaterUpdated + 0xA97
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x000000000003598a (SceneRenderer): DCSSceneRenderer::updateAuxViewport + 0xD05A
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x00000000000588c7 (GraphicsCore): render::BaseRenderingPass::execute + 0x27
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x000000000005902b (GraphicsCore): render::BaseRenderingPass::execute + 0x78B
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x000000000005df14 (GraphicsCore): render::RenderGraph::render + 0x314
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x00000000000285e2 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x000000000016c578 (Visualizer): smSceneManager::regLua + 0x17E8
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x0000000000155964 (Visualizer): smCamera_Implement::getClipRegion + 0x1C3C4
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x000000000013f74c (Visualizer): smCamera_Implement::getClipRegion + 0x61AC
2025-09-15 11:25:23.165 INFO    EDCORE (47112): 0x000000000015a242 (Visualizer): smSceneManager::DestroySceneManager + 0x1222
2025-09-15 11:25:23.166 INFO    EDCORE (47112): 0x0000000000033171 (edCore): ed::thread::_get_current_thread_id + 0x71
2025-09-15 11:25:23.166 INFO    EDCORE (47112): 0x00000000000037b0 (ucrtbase): wcsrchr + 0x150
2025-09-15 11:25:23.166 INFO    EDCORE (47112): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17
2025-09-15 11:25:23.757 INFO    EDCORE (47112): Minidump created.

 

[BalthasarDE]

I'm impressed by how quickly a suggested solution came up. Thank you so much. I'll give it a try and get back to you when Steam's repair process is complete.

[BIGNEWY]

3 minutes ago, BalthasarDE said:

I'm impressed by how quickly a suggested solution came up. Thank you so much. I'll give it a try and get back to you when Steam's repair process is complete.

No problem, please let me know how you get on. 

If that does not work I want you to rename your dcs folder in saved games.

Keep it as a back. 

Then restart DCS, login, and test. 

thank you 

[BalthasarDE]

Unfortunately your advice didn't help me, the game crashed again in the same situation.
dcs.log-20250915-125544.zip

[BIGNEWY]

 

Sorry to hear that.

Please try a fresh install of the latest GPU driver it may help. 

thank you 

[BalthasarDE]

vor 35 Minuten schrieb BIGNEWY:

No problem, please let me know how you get on. 

If that does not work I want you to rename your dcs folder in saved games.

Keep it as a back. 

Then restart DCS, login, and test. 

thank you 

Even after renaming my dcs folder in saved games, i am stuck on the same spot.

[BalthasarDE]

vor 20 Minuten schrieb BIGNEWY:

 

Sorry to hear that.

Please try a fresh install of the latest GPU driver it may help. 

thank you 

Finally, I found the problem. It was my in-game graphics settings, which were adjusted to my monitor and were far too harsh for the high resolution of my VR headset.
I used today the wrong profile 

Thanks again for your quick help and effort.

[BIGNEWY]

2 minutes ago, BalthasarDE said:

Finally, I found the problem. It was my in-game graphics settings, which were adjusted to my monitor and were far too harsh for the high resolution of my VR headset.
I used today the wrong profile 

Thanks again for your quick help and effort.

No problem, good to hear you have found the issue. 

Thanks for letting us know