Crash when starting a mission with Blur on (VR only)

[PawlaczGMD]

Crash when starting a mission with Blur on (VR only).

Logs.rar

[sleighzy]

I've seen this in a couple of cases with other folk. Disabling motion blur worked. However, the underlying issue for one of the users was needing to clean and reinstall their video card drivers.

The below was output from the DCS log analyser for your log files. Of note there is the GPU error so recommend that as a first step if you haven't already. The last note containing a number of steps is a fairly generic step of steps, focus on the driver issue initially.

• There is a GPU-related error
  • (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM.

 

• Process Lasso detected
  • Process Lasso can cause issues with DCS MT. Consider disabling it.
• Memory Timing Issues
  • Remove any overclocking (XMP) from your RAM.

 

• Your DCS has crashed
  • The crash occurred inside dx11backend.dll.
  • Try a slow repair of the game.
  • Remove your custom mods.
  • Delete Saved Games\DCS\fxo and metashaders2 and try again.
  • Next, delete %LOCALAPPDATA%\TEMP\DCS and try again.
  • Next, try renaming Saved Games\DCS to DCS.old and try again.

Edited January 29 by sleighzy

[Ogata_Rina]

Got the same problem with motion blur causes 100% game crash in VR.

CPU: 14700k at Intel default setting

GPU: RTX-5090 Stock clock stock VRAM

RAM: 64GB 6400MT/s CL32

VR: Pimax Crystal Light at 0.9 render quality

 

dcs.log-20250404-051222.zip

[sleighzy]

On 4/4/2025 at 6:20 PM, Ogata_Rina said:

Got the same problem with motion blur causes 100% game crash in VR.

CPU: 14700k at Intel default setting

GPU: RTX-5090 Stock clock stock VRAM

RAM: 64GB 6400MT/s CL32

VR: Pimax Crystal Light at 0.9 render quality

 

dcs.log-20250404-051222.zip 510.03 kB · 1 download

You have a number of issues going on there. Whilst motion blur may be a trigger like some other reporters it still appears to be a GPU issue. The log also indicates memory timing issues.

Process Lasso detected

• Process Lasso can cause issues with DCS World. Consider disabling it.

Memory Timing Issues

• Remove any overclocking (XMP) from your RAM.

There is a GPU-related error

• (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM.

 

Additional tuning info:

• Remove the core-affinity mask from your CPU.
• Verify that this is configured correctly in Windows:
  • Game Mode disabled
  • Hardware accelerated GPU scheduling disabled
  • Core Isolation disabled
     
• Disable Tacview for performance reasons.
• Disable civil traffic.
• Consider using DLAA.
• Enable Full Screen mode.

 

[Qcumber]

I am having the same issue. I ran the crash log through the discord log analyser and this is the report.

"Errors

There is a GPU-related error

(Re-)install the latest GPU drivers. Don't overclock your GPU or RAM.

Your DCS has crashed

The crash occurred inside dx11backend.dll.

Try a !repair.

Delete Saved Games\DCS\fxo and metashaders2 and try again.

Next, delete %LOCALAPPDATA%\TEMP\DCS and try again.

Next, try renaming Saved Games\DCS to DCS.old and try again.

Stacktrace

(dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 (SceneRenderer): BRDFRenderer::onWaterUpdated + 0xBA8 (SceneRenderer): DCSSceneRenderer::updateAuxViewport + 0xCEDA (GraphicsCore): render::BaseRenderingPass::execute + 0x27 [...]

Carry out the suggested repair steps one after the other. If all fails, open a !support ticket."

I have tried all these options and it still crashes. Everything works fine when Motion Blur is disabled. 

 

 

dcs.log-20250406-104152.zip

Edited April 6 by Qcumber

[Ogata_Rina]

Disabled Process Lasso, reinstalled driver, disabled XMP (which is stable in every other game and memory test), and I'm still able to recreate this bug.

It's probably a driver issue, but it's not a priority by any means, no one should even considering using motion blur in VR lol. I just coincidentally found the problem since I was running my desktop setup in VR. Obviously I would not run DCS with default DDR5 clock, so I will just turn off motion blur for now.

A really really really easy fix for this bug is just to force motion blur off in VR. Seriously no one should even consider using motion blur in VR.

dcs.log-20250406-113427.zip

[Qcumber]

32 minutes ago, Ogata_Rina said:

A really really really easy fix for this bug is just to force motion blur off in VR. Seriously no one should even consider using motion blur in VR.

I was just interested to see if it helps VR. From your comment I would suggest not.