If I use Proton 7.0 the game sometimes crashes with an access violation error. I'm playing now with Proton experimental to test.

Understood. I will enable Proton 7.0 which crashes sometimes.

The game crash on launch under proton experimental.

System Info

Game Log (error.txt)

steam-1850570.log

Proton 7.0-1 works but still have random crash during loading (e.g. attempting to visit firing range).

Thank you, @arifwn. I'm trying to get the logs, but the game isn't crashing enough (!). I think may be there are more crashes over the first part of the game

For whatever reason this game will always crash at start for me without enabling SteamInput and using Experimental. Tried a bunch of launch options, different versions of Proton, unplugging peripherals, etc. and could only get it to launch in this way. And from what I can tell, rumble doesn't work through SteamInput even using the official controller profile. Which is a shame because rumble is quite important for this game. There is not even a rumble emulation option for me in the "Controller Option" settings, was this feature discontinued?

Is there a possibility to get the haptic feedback working with the Dualsense controller? I've tested with Proton experimental with Dualsense controller plugged in via USB and steam input disabled and the adaptive triggers work perfectly. However there is no haptic feedback. I understand the game uses the controllers audio output for this feedback. I do see the Dualsense as an audio device, but I assume Proton doesn't currently have a way to utilize this.

On Fedora 36 (was working before). Already check the files. Tried with Proton, Proton Experimental, Proton-GE, with no parameters, with just gamemoderun and with PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr gamemoderun %command% -dx12. On Fedora 35, before I decided to test F36, it was crashing, but as I saw Windows players also having crashes I decided not to try playing
Nvidia drivers: 510.68.02
Kernel: 5.17.5
NVIDIA GeForce RTX 2060 Mobile
Fedora 36 Workstation (GNOME 42.0) Fully updated

error.txt

I'm having the same exact errors as msmafra and arifwn on Debian 12 (testing / bookworm).
I tried Official Proton 7.0 / Proton Experimental / GE-Proton7-24: nothing works.

On ArchLinux it's working.
I just finished Order No. 3 Cremation Mission (Bridget's corpse). (almost) No issues at all.
I'm trying to figure out how to get DualSense (bluetooth) working into the game. Steam recognize it.
In per-game Controller's settings I left DEFAULT ones. Should I try forcing Enabling Steam Input?
DualSense is working with Proton on other Steam (windows-only, SteamPlay) games.

Also it's working perfectly fine on Flycast, DuckStation, M. A. M. E.

kernel: extra/linux-zen 5.18.9.zen1-1
multilib: YES
GPU: GTX 1660SUPER
drivers: extra/nvidia-dkms 515.57-1
SteamLibrary: mounted on external NTFS USB HDD
mount options:

sudo mount -t ntfs-3g /dev/sdc5 /mnt/NTFS/ -o users,allow_other,rw,uid=1000,gid=1000,umask=000,fmask=000,dmask=000,relatime,async,big_writes,locale=it_IT.utf8,suid,dev,exec

DSDC struggles to hit a stable framerate, mostly hovering around 70-90 frames a second on a 144 Hz, 1440p panel. Disappointingly, GPU and CPU aren't even half used. Checked for thermal / power / bus bottlenecks and there were none. The card should be plenty powerful to run this game at the target framerate of 144 fps.

• GPU: AMD Radeon RX 6900 XT
• Driver/LLVM version: Mesa 22.1.6 / LLVM 14.0.6 (Using RADV)
• Kernel version: 5.15.60
• Link to full system information report as Gist: https://gist.github.com/NyaomiDEV/4f965c94d5c41c2678d109995ef59bf1
• Proton version: 7.0-4, Experimental

@NyaomiDEV
Same here... I have a less powerful GPU (GTX1660S), but running the game in Fullscreen 1920x1080@60 with Medium Graphic Settings preset, I got no full / stable framerate and both GPU and CPU (Ryzen 1700) are not fully used, no bottlenecks.

Looking around this could be caused by:

• the game is not well optimized for AMD CPUs

and / or

• Steam Overlay

and / or

• Steam Input enabled

and / or

• Using a gamepad instead of Keyboard and Mouse

Streaming this game from a Linux host (Kubuntu 20.04, 2080 Ti) to the Deck works fine after the recent Steam beta update... except that after about half an hour the audio breaks up and eventually stops working entirely. Ironically, the audio that's playing on the host still works fine.

Sporadically on game exit, I'll get an error popup about the DS4 haptics. No idea if it represents a game bug, a controller driver bug, or a Proton issue. I think probably the former, since it's only sometimes and is otherwise working great, but I thought I'd report it in case it gives any insight into anything.
error.txt

Randomly crashes, same error.

On the steam deck (512GB) the game either stops responding or outright crashes, when in map view immediately after input from the right analog stick, regardless if the stick is from the integrated controller or bluetooth connected xbox controller. The right stick controls view angles on the map. Map movement of the map with the left stick works without issues. Controlling the character with the right stick works without issues.

When attempting to kill the non-responding game in gaming mode, sometimes the kill succeeds, sometimes the entire deck needs to be hard reset, I have not figured out what this depends on.

I have verified, that the crash does not happen on Windows 10 using the controller (different hardware, just to rule out issues on the game side).

As of 2.12.2022 it happens on:
SteamOS versions: stable, preview
Proton versions: Experimental, 7.0-4
Game run mode: desktop mode, gaming mode

steam-1850570.log

Just came here to report the same as the above, exactly the same on SteamOS 3.4 with Proton 7.0-4, Proton Experimental (including bleeding edge beta) and GE-Proton 7-41.

As soon as I touch the right stick on the map, most of the time the Steam Deck hard reboots itself but I just caught this one https://steamcommunity.com/sharedfiles/filedetails/?id=2898032788 that did not result in a hard reboot but it still killed the game the same way. Seems like this is easily reproducible.

Thought it might be XeSS but it’s the same with FSR2. In-game Vsync also doesn’t change the bug.

Update: changing the right stick in Steam Input to Joystick Mouse fixes it. So a Steam Input bug?

Video to show it: https://www.youtube.com/watch?v=zMguCPInqoQ

Proton Log:
steam-1850570.log

Replying to https://github.com/ValveSoftware/Proton/issues/5758#issuecomment-1338150128

Worth noting that changing the behaviour of the right stick just makes the stick move around the map instead of tilting it, which is causing the crash. People have reported the same issue on a keyboard by holding Alt and moving the mouse around which should tilt the map, so it doesn't feel like a Steam Input issue.

While true, it at least stops it crashing for now. I've tried other combinations in Steam Input. Have no idea what's causing it.

Someone who follows me on Mastodon pointed out the crashing on the map is a Mesa GPU issue that has a fix, so hopefully Valve will pull it in for Steam Deck soon: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704

Can you try again with Mesa main? We merged a fix for this issue. Thanks!

@hakzsam this may be a stupid question (apologies, I'm new to Steam deck and Mesa) - but I tried checking for updates to Mesa on my deck this morning (via desktop updates) and there are no recent updates (since Nov). I'm very happy to test the Death Stranding DC bug again if someone can explain what I need to do to get the latest version of Mesa with the merged fix. Thx

@tk32-git I think a new Mesa update (containing the fixes as well) will land on the Steam Deck very soon.

Can you try again with Mesa main? We merged a fix for this issue. Thanks!

I'd love to. Unfortunately, after trying to compile mesa main on the steam deck for a couple of hours in various ways and always getting stuck with errors
/tmp/tmpkkojmqbm/testfile.c:2:18: fatal error: errno.h: No such file or directory
and
mesa/meson.build:1037:6: ERROR: Could not get define 'ETIME'
I am at a loss on how to get mesa main to the steam deck earlier than waiting for some official release (currently mesa driver version 22.2.4 is installed in discover with some wonky other older/developer versions but those still crash).

I am a technical person, but not 100% at home in linux systems, so if someone would cook up some steps about how to get over those errors on the steam deck, I'm willing to give them a try. The steps would need to contain some explanation on how to make the system use the compiled mesa drivers if some steps are needed, I have no clue how to do that.

I would like to add that the performance on Steam Deck is awful and it really shouldn’t be Verified. From what I can tell. A game update made it far worse but the original version (not directors cut) runs better.

Across two Steam Decks, a BT encounter will drop it hard below 30FPS as will moving through new areas in the open world.

Can you try again with Mesa main? We merged a fix for this issue. Thanks!

I don't know how to check the mesa driver version, but as of latest steam deck preview and proton experimental the map crash does not happen anymore

DSDC struggles to hit a stable framerate, mostly hovering around 70-90 frames a second on a 144 Hz, 1440p panel. Disappointingly, GPU and CPU aren't even half used. Checked for thermal / power / bus bottlenecks and there were none. The card should be plenty powerful to run this game at the target framerate of 144 fps.
@NyaomiDEV

Same here, 6900XT. I feel really annoyed that I can't 'just boost my usage' to be able to play this game in all its glory; I've waited long enough :sob: No matter what resolution I run at it's not the framerate I would like to play the director's cut at.

Does anyone know if this is going to get any better?

I'm also getting random freezes where I need to kill and restart sway, can't determine what it is and I'm not good enough at linux to find the logs for the crashes so I'm sorry :frowning_face:

I hope we can get this game into a happy place soon. I have no idea why this runs so poorly?

• CPU: AMD Ryzen 7 5800X
• GPU: 6900 XT
• Running at: 2560x1440 windowed mode, getting 70-90 fps but feels sluggish when this is normally more performant in other games
• OS: NixOS 23.05
• Windowing: Wayland / Sway
• Driver: RADV NAVI21 (Mesa 22.2.4)
• Full system information: Found here

I just finished the game yesterday. The game ran buttery smooth except for the issue that was reported here.

However, at the almost very end of the game, I encountered a huge performance drop (SPOILERS kind of):

I've deleted the game because I've completed it, but I just wanted to report this in case someone else experienced it as well.

• CPU: AMD Ryzen 9 5900X
• GPU: AMD RX 6800 XT
• RAM: 32GB
• Running at: 2560x1440 Fullscreen/Borderless (other option than Windowed)
• OS: EndeavourOS
• Windowing: Wayland / KWin
• Driver: Mesa-git from AUR
• Full system info: here

Note: The GPU hang with RADV is fixed in Mesa 22.3.1+ and should also be fixed on Steam Deck.

I downloaded the game, and when I started it gave me this error

I am using Proton Experimental, with Proton 7.0-5 works fine

Hi.

I have been playing the game for about 60 hours fairly well until now, some stutter here and there, but looks like it's a common problem even in windows.

The game crashes consistently in a mission when entering the ruined factory, about the same spot. The game stutter a lot more than usual while approaching the area. I've been playing until now with proton-next 7.0-6 mostly. The crash is present in proton 7.0-5 too.

I have had a similar experience with a nightmare inside the private room, crashing every time, playing around with proton version I was able to advance then, but not now.

System Information
steam-1850570.log

I have been testing the latest Proton Experimental and I was able to complete the mission without any trouble. The hour or so that I have been playing looks like it''s working fine.

Hello,
I'm experiencing issues with ground and stones textures glitching as can be seen on the video here:

https://user-images.githubusercontent.com/6793160/232576516-a964994e-d647-4d80-81a9-fc92b4767492.mp4

I tried some launch options found on protondb page changing graphical options in game, changing proton version to GE, but nothing I tried fixed it

System Information

• GPU: RX 570
• Driver/LLVM version: Mesa 23.0.2
• Kernel version: 6.2.11
• Link to full system information report as Gist: https://gist.github.com/marekjedrzejewski/88677863b16633b992c4ca8a50a530f7
• Proton version: Experimental

steam-1850570.log

I confirm:

• [X] that I have checked whether there are updates for my system available.

Wow, that was quick!
Thanks, that was the problem, glitches are gone after removing amdgpu-pro-oglp and vulkan-amdgpu-pro ❤️
Hope I won't need those anytime soon as I only installed them to play around with davinci resolve and didn't touch it for quite some time

Gnome 44.3 (wayland and xorg tested)
mesa/radv 23.1.1
Proton 8.0-2 and Experimental tested

Proton log: steam-1850570.log

With a 3440x1440 (21:9) display connected the max resolution detected by the game is 3360x1440. The game has visible thin black bars on each side of the screen when using 3360x1440.

Setting 3440x1440 manually in settings.cfg of the game results in an unsupported window settings error.

I had bluetooth gamepad controller problems with this game in steam deck. The integrated gamepad works fine. I couldn't re-arrange the order, only deck controller or keyboard.

I tried various proton revisions and no luck. Enable or disable steam input or choose a community layout doesn't solve it.

Hi, I've got a problem that while moving the cursor of the map, it jumps very fast, making the map complete unuseable.

Video on Google Drive (Sorry for the inconvenience but Github keeps telling me upload failed for the video)

I've tried Proton 7.0-6, 9.0-4, Hotfix and Experimental, and non of them resolves this problem. Both mouse and controller is not working.

It is also worth mention that the speed of the loading animation is fast and unstable compared to the Windows ones (which you can tell by the start of the video), and sometimes the game menu ignore some of my mouse clicks. I'm not sure whether it's the same problem.

Proton log: steam-1850570.log

@TTsdzb I couldn't get the same effect, tried proton 7 through experimental and the cursor moved normally in all of them. Have you noticed anything similar in other games? What desktop environment are you using?

@simifor I haven't run any large game like this for now, and my other games seems fine. I'm using Arch Linux with KDE Plasma 6.3.0 (still got this problem after latest update), and is a Wayland session. Are you running the game on x11?

@simifor I haven't run any large game like this for now, and my other games seems fine. I'm using Arch Linux with KDE Plasma 6.3.0 (still got this problem after latest update), and is a Wayland session. Are you running the game on x11?

I can play fine on Arch with X11 (KDE) and nVIDIA GTX 1660 SUPER. I'm using Proton 9.0 (latest). Inputs are working as expected: both keyboard and DualShock4 (USB).
Same for the standard edition of Death Stranding.

I can play fine on Arch with X11 (KDE) and nVIDIA GTX 1660 SUPER. I'm using Proton 9.0 (latest). Inputs are working as expected: both keyboard and DualShock4 (USB). Same for the standard edition of Death Stranding.

I tried running it in a x11 session but the issue persists. Besides, using an Xbox controller could also cause this problem, which doesn't seems like caused by the mouse input.

I'm playing on a Lenovo Legion R7000P 2021 with an AMD integrated GPU and a NVIDIA 3060 Laptop. The game runs on the discrete one accroding to the log.

@TTsdzb you're on a laptop... Seems like some input acceleration option is enabled.

Can you try completely disabling the touchpad itself from within KDE System Settings (within X11)?

Also check if Mouse Acceleration is on.

Try starting from a fresh Proton profile (REMEMBER BACKING-UP YOUR OLD ONE!!).

Replying to https://github.com/ValveSoftware/Proton/issues/5758#issuecomment-2646936373

Maybe some Valve's devs hopefully have a look into these:

15433.839:00cc:00d0:err:xrandr:xrandr14_get_adapters Failed to get adapters
15433.859:00cc:00d0:err:xrandr:xrandr14_get_adapters Failed to get adapters
15433.960:00cc:00d0:err:xrandr:xrandr14_get_adapters Failed to get adapters
15433.973:00cc:00d0:err:xrandr:xrandr14_get_adapters Failed to get adapters
15435.260:0124:016c:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
15435.266:0124:016c:err:ntlm:ntlm_LsaApInitializePackage no NTLM support, expect problems
15435.827:0124:0128:err:module:import_dll Library MSVCP140.dll (which is needed by L"Z:\\mnt\\data\\liusq\\Steam\\steamapps\\common\\DEATH STRANDING DIRECTORS CUT\\DXCompiler.dll") not found
15435.827:0124:0128:err:module:import_dll Library VCRUNTIME140_1.dll (which is needed by L"Z:\\mnt\\data\\liusq\\Steam\\steamapps\\common\\DEATH STRANDING DIRECTORS CUT\\DXCompiler.dll") not found

@TTsdzb I had originally tested on plasma xorg 6.2.5, but today I test on plasma xorg and wayland 6.3.0 without issue. Have you noticed if the glyphs change when the issue happens with the xbox controller? does it switch to mouse and keyboard icons?

@cinnamonmatexfce the times I've seen xrandr issues match with user problems has been related to crashes (either due to the game trying to run at a resolution not supported by the display or it trying to load amdvlk and radv at the same time). Just in case, @TTsdzb should check the resolution list in the game's graphics settings to see if there's anything weird going on.
kerberos and ntlm are harmless, they appear in most logs.
The missing libraries are atypical as they are in the prefix, but considering I have the same error, it should be unrelated to the cursor issue.

@Sanfe I'm sorry your report went unaddressed for so long, I checked just now with a dualsense and it was working as expected, if you are still having controller issues let me know

Have you noticed if the glyphs change when the issue happens with the xbox controller? does it switch to mouse and keyboard icons?

No it sticks to the controller's glyph. And it only changes when I physically move my mouse. Sorry for the mistake, that's a misunderstanding of your question.

I'll check the other things when I'm free. Besides, did you guys notice the loading animation is weirdly fast compared to Windows? I think it's some sort of clocking issue of the game menu...

Can you try completely disabling the touchpad itself from within KDE System Settings (within X11)?

Also check if Mouse Acceleration is on.

Try starting from a fresh Proton profile (REMEMBER BACKING-UP YOUR OLD ONE!!).

Disableing the touchpad and Mouse Acceleration in a x11 session doesn't work, either.

May I ask where is the Proton profile? I moved the prefix in <LibraryPath>/steamapps/compatdata/1850570/pfx elsewhere during this test.

should check the resolution list in the game's graphics settings to see if there's anything weird going on.

Resolution is good with a maxium of 1080P, which is my monitor resolution.

DualSense haptics still not work for this game, right?

Is there any particular reason?

Thanks.

I have build Proton-GE 9.26 with this patches and still no luck:

https://github.com/arnxxau/proton-dualsense

Maybe anyone else could try.

For anyone wondering DualSense haptic feedback not working, check out this thread: https://github.com/ValveSoftware/Proton/issues/5900

The patches don’t do anything for Death Stranding for now, although it was included Proton GE

Hi, I've got a problem that while moving the cursor of the map, it jumps very fast, making the map complete unuseable.

Video on Google Drive (Sorry for the inconvenience but Github keeps telling me upload failed for the video)

I've tried Proton 7.0-6, 9.0-4, Hotfix and Experimental, and non of them resolves this problem. Both mouse and controller is not working.

It is also worth mention that the speed of the loading animation is fast and unstable compared to the Windows ones (which you can tell by the start of the video), and sometimes the game menu ignore some of my mouse clicks. I'm not sure whether it's the same problem.

Proton log: steam-1850570.log

Hello. I have this issue too but I have yet to find what causes this problem.
What is even strange is that this occurs on ALL distros on all post-DeathStranding proton support versions (including proton-ge), except Linux Mint. Funny enough, Linux Mint makes the loading screen not be sped up, as well as the menu correctly registering my mouse/controller clicks, but it crashes when I load a save. When I go back to the game after the crash, the issue occurs.
I tried both hybrid, integrated and discrete options and all persist.

Edit : Right now I am testing Bazzite and the issue happens here too.

The last report, merged from #9133, is gone now with proton-GE-10-24.

This is a mere guess, but in proton-GE-10-22 problems of many games were fixed, by the wine fix related to ntdll. Perhaps this is one of them.

Anyway thanks kisak-valve for sorting issues. Best regards.

I want to add something regarding the game stuttering every once in a while. The issue is caused by HPET. To check if you have it enabled, run this command:
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
If you have HPET enabled, check what other sources you have:
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
If you have TSC, you will have to switch to it. If you don't have it at all, you must use a kernel that enabled it (GRUB won't enable it automatically if your hardware reports issues with this clocksource). Good luck!