protonscr

Space Engineers 2

protonopen appid 1133870Game compatibility - UnofficialMesa driversAMD RADV
ValveSoftware/Proton#8859 · opened 2025-06-27 by Sveske-Juice · updated 2026-01-05 · 7 comments · github · game page · search this game
1 matching comments, n / p to jump
SSveske-Juice 2025-06-27 github

Compatibility Report

  • Name of the game with compatibility issues: Space Engineers 2
  • Steam AppID of the game: 1133870

System Information

  • OS: NixOS 25.11 (Xantusia) x86_64
  • GPU: RX 6900XT
  • Kernel version: 6.14.6-zen1
  • Proton version: experimental-10.0-20250612c
  • Steam Linux Runtime: sniper: 3.0.20250408.124536 sniper 3.0.20250408.124536

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Proton Log

The relevant line for the problem is this line:

:warn:seh:OutputDebugStringA "Error: the required library hostfxr.dll could not be found in [Z:\\nix\\store\\pyp6xpcc67g40rwlz4sgi18qbkjyyi6h-dotnet-sdk-wrapped-9.0.105\\share\\dotnet\\host\\fxr\\9.0.4]"

Symptoms

Fails to launch with window saying:
"You must install .NET Dekstop Runtime to run this application"

Image

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:

environment.systemPackages = [
  pkgs.dotnetCorePackages.dotnet_9.sdk # required for omnisharp lsp
];

# https://nixos.wiki/wiki/DotNET
environment.sessionVariables = {
  DOTNET_ROOT = "${pkgs.dotnetCorePackages.dotnet_9.sdk}/share/dotnet";
};
Kkisak-valve maintainer 2025-06-27 github

Related: #8067

SSveske-Juice 2025-06-27 github

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%

RRed007Master 2025-12-02 github

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.

Kkisak-valve maintainer 2025-12-03 github

[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:

Compatibility Report

  • Game: Space Engineers 2
  • Steam App ID: 1133870

System Information

I confirm:

  • [ X] that I haven't found an existing compatibility report for this game.
  • [ X]that I have checked whether there are updates for my system available.

Note: Crashes happen before Proton can really start, no logs can be found. Proton Did not start up for logs to be saved.

Symptoms

Immediate crash.

Reproduction

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

Qquonic 2026-01-05 github

Compatibility Report

  • Name of the game with compatibility issues: Space Engineers 2
  • Steam AppID of the game: 1133870

System Information

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

Symptoms

amdgpu reset's

Reproduction

Have an AMD GPU, using RADV from the Mesa drivers.

Workaround

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.

Kkisak-valve maintainer 2026-01-05 github

Hello @quonic, that reads like something that should also be mentioned to your video driver vendor if it hasn't been already.

Qquonic 2026-01-05 github

@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.

Proton versions

Launch options

Launch lines

Upstream links

DLLs