Enshrouded (1203620)

[polluxau]

Compatibility Report

• Name of the game with compatibility issues: Enshrouded
• Steam AppID of the game: 1203620

System Information

• GPU: RX 6700
• Video driver version: mesa 23.3.3
• Kernel version: 6.7.1
• Link to full system information report as Gist: https://gist.github.com/pollux56/0922d4590850f8453c082952a261e701
• Proton version: proton experimental (bleeding edge)

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.

steam-1203620.log

Symptoms

try to join a game or create a game and it will crash the desktop when the intro starts

Reproduction

use proton stable or experimental, try to create game and get past the intro, game will crash your desktop

[rhoot]

ProtonDB has a lot of reports of people having the same issue (all with AMD cards), and most not being able to run the game at all with the RADV drivers. I've been able to play just fine with RADV drivers however. I don't have AMDVLK even installed though, so that might be the difference?

"EndeavourOS Linux" (64 bit)
Kernel Version: 6.7.1-zen1-1-zen
X Window Manager: wlroots wm
Steam Runtime Version: steam-runtime_0.20231127.68515
Driver: AMD AMD Radeon RX 6900 XT (radeonsi, navi21, LLVM 16.0.6, DRM 3.56, 6.7.1-zen1-1-zen)
Driver Version: 4.6 (Compatibility Profile) Mesa 23.3.3-arch1.1

Two problems I did run into with this game:

• When closing the game Steam will sometimes start validating 8.4 GiB of files. Not sure what files or why.
• I was unable to launch the game at all earlier. Not sure what caused it or why, just no window would show up. It looked as if it stalled on launch. Running with PROTON_LOG=1 gave me nothing but the below. The only solution I could find was to delete the compatdata folder for the game.

======================
Proton: 1705700124 proton-8.0-5c
SteamGameId: 1203620
Command: ['/home/johan/games/SteamLibrary/steamapps/common/Enshrouded/enshrouded.exe']
Options: {'forcelgadd'}
depot: 0.20231211.70175
pressure-vessel: 0.20231208.0 scout
scripts: 0.20231208.0
sniper: 0.20231211.70175 sniper 0.20231211.70175
Kernel: Linux 6.7.1-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:13:51 +0000 x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
======================

Edited to add: The game ID is 1203620

[polluxau]

Replying to https://github.com/ValveSoftware/Proton/issues/7442#issuecomment-1909589488

i dont have vlk installed either and im running endeavour os with the latest packages installed, the only difference im seeing is that your running a wm while im running kde plasma 5.27.10 and i have tried both kwin x11 and kwin wayland with the same results of it crashing when entering the intro of creating a game

[polluxau]

enshrouded.log here is the enshrouded crash log aswell

[polluxau]

thats odd the game is working on kde neon unstable with flatpak steam

edit: if i set reflections to quality the game will crash, setting everything to normal/balanced doesnt make the game crash and its working on endeavour os now so yay :)

[SolarLune]

On a fully-updated EndeavourOS, with the following stats (and skipping Steam's shader precaching):

GPU: AMD Radeon RX 6650 XT
CPU: AMD Ryzen 5 1600 x12
DE: Gnome 45.3
Kernel: Linux 6.7.1-arch1-1
GPU Driver:  amdgpu
Proton: 8.0-5

The game starts and appears to preprocess the shaders.

However, the problems start once the Keen logo shows up, followed by the main menu.

Under X11, when the window is not selected, the game is choppy, but appears correctly (which seems to be expected behavior from my memory of playing on Windows). When I mouse over the window, or click on the window to make it active, though, the window turns black. I can click a menu element (Play or Settings, for example) a frame or two before it goes black, but if I then make the window unselected to see the current state, it will appear back at the main menu. This is the same in either Windowed mode or Fullscreen mode (toggled with Alt+Enter).

Under Wayland instead, it's the same as X11 under windowed mode. However, if I switch in fullscreen mode with Alt+Enter, then the game wholly appears correctly, regardless of if the window is active or not. I still get a black screen game crash when attempting to load a world, though - about 6 seconds after the loading screen starts, my GPU hangs, first evidenced by my inability to scroll a web browser on my other screen, after which my mouse cursor also stalls.

About 12 seconds after that starts, the game crashes.

The crash log is as follows:

https://gist.github.com/SolarLune/205f98300b60908ad06f206999320bc6

I tried a few times more - setting the graphics quality settings to Max Performance didn't help; it still hung the GPU driver. Changing it from my desktop resolution (1440p) to 720p and turning off FSR2 as antialiasing didn't help either - it hung for a longer period of time this time, and then crashed Wayland (I presume) and kicked me out to the login prompt.

[Aftermath]

System:
  Kernel: 6.6.13-200.fc39.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.40-13.fc39 Desktop: KDE Plasma v: 5.27.10 Distro: Fedora release 39
    (Thirty Nine)
CPU: AMD Ryzen 9 7950X3D 16-Core @ 32x 5.759GHz
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX] vendor: Sapphire NITRO+
    driver: amdgpu v: kernel arch: RDNA-3 bus-ID: 03:00.0
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.4
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
    resolution: 1: 2560x1440 2: 2560x1440 3: 2560x1080 4: 2560x1440
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: wayland,x11,surfaceless,device inactive: gbm
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.3.3 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi navi31 LLVM
    17.0.6 DRM 3.54 6.6.13-200.fc39.x86_64)
  API: Vulkan v: 1.3.268 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland
    devices: 2

I was able to start a single player game running Proton Experimental: Bleeding Edge. I also had to turn off a particular graphical setting regarding some voxel rendering option in order to have normal frames, otherwise it would render less than 1 FPS.

I do still get an crash of the display driver / display environment if I attempt to join a dedicated server.

[polluxau]

Replying to https://github.com/ValveSoftware/Proton/issues/7442#issuecomment-1910828896

That seems to be the same problem for me, hosting works tho

[Blisto91]

Made mesa issue for the hang when entering a world https://gitlab.freedesktop.org/mesa/mesa/-/issues/10500

Edit: reworded as it likely isn't the intro video or entering the world for the first time part that is the cause.

[Aftermath]

FWIW, I updated to a kernel-vanilla/stable 6.7.1 from Fedora copr, and the bad behavior changed. I can now connect to dedicated servers and play mostly normally, and Voxel Detail Models can be enabled now without killing frames.

Point Light Shadows are now broken though, and cause really low frames if enabled. Otherwise, runs great.

Worth noting that there were several hotfixes targeting the game today. I don't know if any of those would have had a direct effect on our issues.

[SolarLune]

Back with another finding. As per ProtonDB, starting the game and loading into a single-player world works if I have the RADV drivers installed. On EndeavourOS / Arch, this is done through installing vulkan-radeon and vulkan-icd-loader, I believe, and then running the game with the command VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json %command%.

Also note that the game runs fine on Steam Deck at about 25-30 FPS on all Performance settings.

[TobiasLainson]

I'm also having similar problems, the game launches fine but when I join a multiplayer game it starts to load then I get a black screen, then loading screen again and after that the whole system hangs and I have to pull the power to restart computer.

I have also found a way to circumvent this hang, if I start a single player game first and then quit to start screen I am able to join a multiplayer game without the system hanging. Doing it this way I loose about 2/3 of my fps though. going from 60-100 to 19-25, mangohud is telling me my GPUs memory frequency is going down from a locked 1000Mhz in the single player game to a fluctuating 400-600Mhz during multiplayer.

System: Nobara 39 Mesa 23.3.3 Kernel 6.7.0 Proton, its the same behavior with proton 8, experimental and ge-proton-8-30

[intelligentgaming]

The game runs fine on Ubuntu 23.10 with a RTX 3080 and Ryzen 7 5700X, even at some times beating Windows 11 performance on the same machine.

However the only glitch I have found is that sometimes when launching the game, it will launch in windowed rather than full screen, but this can be easily fixed by toggling in game.

Whether this is the game, Proton or Gnome is anyone's guess.

[Zepticon]

I have similar issues. In order to be able to join a multiplayer dedicated server, i need to sett my settings to "Max Performance". When in game again, i turn them on one by one.

The following options causes issues for me:

• Contact Shadows: Crashes the game. Sometimes i get a crash message, sometimes i need to kill the computer.
• Reflections: Crashes the game. Sometimes i get a crash message, sometimes i need to kill the computer.
• Point Light: Kills frame rates. I drop to 2-3 fps on my 7900XTX

I can have all other settings on max without issues.

System: Kubuntu on kernel 6.7.6 AMD 7800X3D Sapphire RX 7900XTX Nitro+ 64Gig 6000mhz memory

Edit: It seems with those 4 settings disabled, I am able to launch the game as is. The strange thing is that sometimes i can enable some of the settings without it crashing. But not always. But i have steadily played with these off now for a two weeks and no more crashes.

Edit 2: I can also reliably launch the game with Voxel detail models set to max now. It crashes very rarely with this setting on. Still not possible to launch with the above 3 settings on anything than low/off.

[AQDuck97]

The game feels very stuttery for me on Wayland as VRR is not being used even when forced to always on in Plasma settings. The game only has windowed or borderless mode and trying it in windowed mode then using KWin to fullscreen it (which enables VRR with every other program, you can tell by slight flickering) does not work for Enshrouded.

[polluxau]

with the newest patch it crashes a couple of times when trying to load the shader cache and trying to load into a world will stay in the loading screen for a couple of minutes then it kicks you back out to the menu, also some images are broken

this was under latest proton experimental(bleeding edge)

rx 6700 mesa 24.0.3 kernel 6.8

EDIT: latest proton experimental(bleeding edge) the game is now working properly, able to load in and main menu looks correct!

[BentHaase]

Can confirm, the remaining issue is the never ending 'validation' of around 10GB. Any known fix for this?

[urbenlegend]

Can confirm, the remaining issue is the never ending 'validation' of around 10GB. Any known fix for this?

Yeah I am getting the same issue. 9.2 GB of data is being downloaded every time. I have a feeling it is due to the shader cache.

EDIT: Yeah I left Steam to finish processing the shaders in the background and now I no longer get the 9.2 GB download.

EDIT 2: Nvm, it still seems to trigger big downloads but only after a day or so. Doesn't happen with every launch of Steam.

[urbenlegend]

Another issue I am experiencing is if I set Texture settings to Max Quality, all the textures appear black. If I drop it down by one to Quality, it seems okay.

[kisak-valve]

Hello @urbenlegend, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[urbenlegend]

@kisak-valve Here's the proton logs: steam-1203620.log

To generate these logs, I booted into the game, set the texture quality from Quality to Max Quality to trigger the black texture bug, and then loaded into my world. After spinning the camera around for a few seconds, I immediately quit the game.

Here are my Steam Runtime Diagnostics

For anyone curious, this is what it looks like in game:

https://github.com/ValveSoftware/Proton/assets/241316/6a807e26-a56a-49ea-9d8e-3aec84a4c5e0

[esullivan-nvidia]

Another issue I am experiencing is if I set Texture settings to Max Quality, all the textures appear black. If I drop it down by one to Quality, it seems okay.

Thank you for reporting this issue. I was able to determine this is an NVIDIA driver regression only present in r555. A fix will be shipped in a future driver release. If you wish to reference this bug in the future it is being tracked internally with bug number 4675675.

[polluxau]

with the latest enshrouded update the studio improved steamdeck support and added fsr3 which is working perfectly under proton experimental(bleeding edge)

the game also doesnt crash or freeze when switching around graphics settings so there are no more problems that i am seeing now, this under my rx 6700, mesa 24.1.4, kernel 6.10, cachy os

[faandg]

As of last week something broke when running the enshrouded gameserver in proton, should this be tracked here as well? See https://github.com/ValveSoftware/Proton/issues/7995 (it does not appear to be limited to Fedora) and the linked ticket to find some additional testing.