Related: [#8067](https://github.com/ValveSoftware/Proton/issues/8067)
Yes, DOTNET_ROOT is definitely the issue.
Setting these launch options works around the problem:
DOTNET_ROOT="" %command%
What is interesting - I can't reproduce it, I just started SE2 with DOTNET_ROOT=/usr/bin/dotnet ... %command% but it still works perfectly fine.
Maybe it's some layered problem?
Can't somebody who DON'T have this problem reproduce it?
But yea, anyway setting DOTNET_ROOT as global sounds like terrible idea, just set it separably for apps that need it.
[Space Engineers 2] Persistent launch crash due to Fsync/RT priority conflict on Arch Linux/NVIDIA
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9276.
@C10udN9n3 posted on 2025-12-03T04:11:10:
Note: Crashes happen before Proton can really start, no logs can be found. Proton Did not start up for logs to be saved.
Immediate crash.
Pressing start on the game. This can be reproduced after tweaking and configuring wine and proton, on all mentioned proton versions, including a custom Proton-GE 10-25
amdgpu reset's
Have an AMD GPU, using RADV from the Mesa drivers.
My solution that has so far prevented the amdgpu reset's from happening.
Launch Options: RADV_DEBUG=hang,allbos DOTNET_ROOT="" DXVK_NVAPI_ALLOW_OTHER_DRIVERS=1 PROTON_ENABLE_NVAPI=1 PROTON_ENABLE_WAYLAND=1 gamemoderun %command%
Mostly it is allbos that fixed everything, but I keep hang just in case something else causes a reset.
Hello @quonic, that reads like something that should also be mentioned to your video driver vendor if it hasn't been already.
@kisak-valve I just looked and there are plenty of bug reports related to my video driver vendor with other games. Marvel Rivals also had a similar issue back in Jan 2025, but has since been fixed by the game devs or Mesa devs, I can't remember which.
ge-proton10-27x1 2026-01proton 9.0-2x1 2025-12proton 9.0-4x1 2025-12DXVK_NVAPI_ALLOW_OTHER_DRIVERS=1x1 2026-01PROTON_ENABLE_NVAPI=1x1 2026-01PROTON_ENABLE_WAYLAND=1x1 2026-01RADV_DEBUG=hang,allbosx1 2026-01RADV_DEBUG=hang,allbos DOTNET_ROOT="" DXVK_NVAPI_ALLOW_OTHER_DRIVERS=1 PROTON_ENABLE_NVAPI=1 PROTON_ENABLE_WAYLAND=1 gamemoderun %command%x1 2026-01DOTNET_ROOT="" %command%x1 2025-06hostfxr.dllx1 2025-06
Compatibility Report
System Information
I confirm:
Proton Log
The relevant line for the problem is this line:
Symptoms
Fails to launch with window saying:
"You must install .NET Dekstop Runtime to run this application"
So it seems that having dotnet installed on host os (NixOS) (or DOTNET_ROOT env variable) makes wine look for the dll on the native host, while it should be looking for the dll in the wine prefix, right?
Workaround
Uninstall dotnet on host, and it works normally
Reproduction
This is the relevant part of my nix config which handles dotnet: