DeathSprint 66: Wine OpenXR assertion dialog appears on startup
Issue transferred from https://github.com/ValveSoftware/Proton/issues/10311.
@actionschnitzel posted on 2026-10-25T13:41:03:
When launching DeathSprint 66 on Linux via Steam, a Wine C++ Runtime Library assertion dialog appears:
C:\windows\\system32\undll32.exe../src-wine/dlls/wineopenxr/openxr_loader.c651!_status && "CreateInstance"The game does not proceed normally until the assertion dialog is dismissed by clicking OK. After closing the dialog, the game continues starting and appears to run.
This issue started occurring on October 25, 2026. The game previously launched without this dialog.
The Proton log shows that DeathSprint66.exe and ProximaGameAntiCheatShell.dll are loaded. It also contains COM-related errors shortly before the process continues.
The issue appears to be related to Wine/Proton's OpenXR initialization, but the exact cause is currently unknown.
wineopenxr/openxr_loader.c, line 651.The issue has so far been observed consistently during startup.
The following launch option was used to generate a Proton log:
PROTON_LOG=1 %command%
Relevant log excerpt:
Loaded ... DeathSprint66.exe ... native
Loaded ... ProximaGameAntiCheatShell.dll ... native
err:ole:com_get_class_object class {6962a8a2-bf55-4246-ad5d-9d26e0c1e1ce} not registered
err:ole:com_get_class_object class {71663b86-cc70-44a6-bb3a-40b95b74ebdf} not registered
pid 4843 != 4842, skipping destruction (fork without exec?)
Full Proton log: steam-1273560.log (to be attached).
System information and the exact Proton version will be added once collected.
@actionschnitzel have you tried bleeding edge? it's working on my end (at least game launch and tutorial) https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge
5. @actionschnitzel have you tried bleeding edge? it's working on my end (at least game launch and tutorial) https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge
That did the trick! THX
In the meantime, I used WINEDLLOVERRIDES="wineopenxr=d" %command% as a workaround. It allowed the game to launch without any issues in Game Mode, although the error dialog would show up later when switching to Desktop Mode.
I'll stick with Bleeding Edge for now until the fix makes it into the stable releases.
WINEDLLOVERRIDES="wineopenxr=d"x1 2026-10PROTON_LOG=1x1 2026-10proximagameanticheatshell.dllx1 2026-10
Compatibility Report
System Information
I confirm:
steam-1273560.log
Symptoms
Game fails to launch
Reproduction