Crimson Desert crashes on launch with OptiScaler no matter which proxy/load method I use

Since there has been an active increase in new issues without any basic info to help troubleshooting, we're releasing this Issue Report Template that should help troubleshoot without our magic 8 ball. Going forward, issues that do not follow the Template will be ignored.

Game name and version:

Crimson Desert (steam)

Mods and mod versions used

OptiScaler 0.9.0 OptiScaler 0.9.1 OptiScaler 0.9.4

GPU

rtx 3060 ti

OS

win11

Used automated or manual install?

Tried both

Also please mention in description which upscaler inputs are used (which upscaler you selected in game settings).

Did you check the Wiki and Compatibility List?

• Yes

Please describe the issue and steps to reproduce it

I'm having a weird issue with Crimson Desert where I just cannot get OptiScaler to work at all.

The game launches normally without OptiScaler, but as soon as OptiScaler is loaded, the game crashes on startup with 0xc0000005.

I've tried pretty much everything I could think of:

OptiScaler 0.9.0 OptiScaler 0.9.1 OptiScaler 0.9.4 dxgi.dll d3d12.dll version.dll winmm.dll OptiScaler.asi through an ASI loader clean game install / file verification default OptiScaler.ini forcing different Dx12Upscaler values instead of auto no RTSS / MSI Afterburner / ReShade / Discord overlay / NVIDIA overlay running

It still crashes no matter what I do.

Current setup:

Crimson Desert Steam version CrimsonDesert.exe version: 1.0.0.2330 Windows 11 build 26200 NVIDIA GPU OptiScaler 0.9.4

With 0.9.4, both dxgi.dll and version.dll crash at the exact same OptiScaler offset:

Exception code: 0xc0000005 Faulting offset: 0x000000000003e87a

0.9.1 also crashes at the same internal offset regardless of whether I use DXGI, D3D12 or ASI:

0x000000000003cf8a

I also captured a crash dump.

At the crash point in 0.9.4, the faulting instruction appears to be:

mov rax, qword ptr [rax + rcx*8]

with:

RAX = 0 RCX = 0x11

so it ends up trying to read address 0x88.

The instruction immediately before that is:

mov rax, gs:[0x58]

and the TLS pointer appears to be null on the crashing thread.

So at this point it doesn't look like a particular proxy DLL name is the problem, since changing the loading method just leads back to the same crash inside OptiScaler.

I can attach the .dmp file and logs if needed.

Has anyone seen this on the current Crimson Desert build, or is there anything else I can try? I'm basically out of ideas at this point.

OptiScaler.log