Proton
Proton copied to clipboard
ValveSoftware
Death Stranding Director's Cut (1850570)
Compatibility Report
- Name of the game with compatibility issues: Death Stranding Director's Cut
- Steam AppID of the game: 1850570
System Information
- GPU: RTX 3060 for laptop
- Driver/LLVM version: NVIDIA 510.60.02
- Kernel version: 5.17.2
- Link to full system information report as Gist: https://gist.github.com/mhalano/7016923cac03f0bc726edfb7d6cb85a2
- Proton version: 6.3-8
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
The game crashes during the initialization
Reproduction
Install the game and select to use Proton 6.3-8.
If I use Proton 7.0 the game sometimes crashes with an access violation error. I'm playing now with Proton experimental to test.
Hello @mhalano, err:steamclient:create_win_interface Don't recognize interface name: SteamInput006 in your log tells us that this game uses a version of steamworks which lsteamclient doesn't understand until Proton 7.0-1 or newer. A log from a newer build of Proton would be more interesting.
The game crash on launch under proton experimental.
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
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
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
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
@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):
Scene location
At the pretty much very end of the game. At the end of Episode 13: Sam Strand. You will be on the Beach and have to walk around and watch cutscenes with Amelie.After you have watched all of them, a game credits will start to roll on the screen (lower right corner of the screen).
As soon as they appear, games tanks in performance. Here is the direct timestamped video of that location: https://youtu.be/2_p9wLMNOeM?t=91727
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
