Proton
Proton copied to clipboard
ValveSoftware
Sekiro: Shadows Die Twice (814380)
Compatibility Report
- Name of the game with compatibility issues: Sekiro: Shadows Die Twice
- Steam AppID of the game: 814380
System Information
- GPU: R9 290x
- Driver/LLVM version: Mesa 18.2.2
- Kernel version: 4.15.0-46-generic
- System info: https://gist.github.com/ivakam/53a2dbb0f5d0adb68c8e7253d71eadaa
- Proton version: 3.16-8 beta
Symptoms
Game launches to a black screen with the steam FPS overlay showing ~15 FPS for about 2 seconds and then silently closes. Other games run fine (as far as I've tested).
Reproduction
Just launching the game reproduces the error afaik. I've tested on Proton 3.16-8 beta with DXKV upgraded to 1.0.1 with the same results.
Are you using steam-native or steam-runtime? Bit weird that it crashes inside SDL2, the game works fine for others.
I'm afraid I can't tell you if I'm using steam-native or steam-runtime. I can tell you however that it doesn't matter if I run it from the terminal using steam steam://rungameid/814380 or if I just click "Play" in the library. The former option doesn't print anything out of the ordinary
I am aware that it works for most other people. I just want to play the dang game too! :sob:
According to version sdl2-2.0.so.0 it's steam-runtime, but why 'PROTON_USE_WINED3D11=1'? Also better to disable steam overlay.
I read somewhere that it fixed a similar issue for another game. Turning it off changes nothing.
On a related note, I just tried Dark Souls 3 with the exact same error and result (using Valve's recommended Proton version results in the infamous "steam shows game as running for a fraction of a second and then silently stops"). I'll be trying DkS1 shortly (I have no games installed on this machine, so I'm testing as I install them).
I will definitely try disabling the overlay. Thanks for the quick help!
EDIT: Running with steam overlay turned off didn't change anything as far as I can see. I'll check the logs to see if anything's changed in there.
Run a full system upgrade through your package manager and upgrade to Steam beta.
Game runs perfectly for me, running everything on high with AA, no configuration needed.
Xeon 1230v2, RX580, Mesa 19.0.0-1 on Arch, kernel 5.1.0-rc1
Default PS4 controller mapping through Steam had gyro enabled but that has nothing to do with the game or Proton.
Honestly this could be a whitelist candidate.
Just tried both full system upgrade + Steam beta with no working Sekiro in sight :( The full upgrade did fetch a bunch of related packages bringing me up to Mesa 18.3.3, but it hasn't changed the situation at all (I've tried rebooting)
It seems like Dks1 and 3 produce the same error as Sekiro. Tropico 4 (the only whitelisted 3D game I own) works 100%. Native linux games like Dota 2 work 100% (even with Vulkan), and 2D games work perfectly both through proton and natively.
Driver: X.Org AMD Radeon R9 200 Series (HAWAII, DRM 3.23.0, 4.15.0-46-generic, LLVM 7.0.0) Driver Version: 4.4 (Compatibility Profile) Mesa 18.2.2
Can you try with a newer driver?
https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa
Add this ppa to your system.
I have updated both Mesa and amdgpu since the OP and I'm now on OpenGL Mesa 18.3.3 and amdgpu 19.0.1. No dice.
Edit: An important word
Unfortunately I'm away from my PC until later tonight (EU time), but I'll make sure to give you new logs asap!
Starts fine, xbox 360 controller is used ingame as mouse, appears to work fine in big picture, anyone else run into this? Edit: had to disable xbox configuration support in steam controller settings!
Starts fine, xbox 360 controller is used ingame as mouse, appears to work fine in big picture, anyone else run into this? Edit: had to disable xbox configuration support in steam controller settings!
My friend on Windows said their PS4 controller was mapped exactly the same as mine by default.
Gyro on, and right joystick was set as mouse instead of joystick. These are steam controller mapping issues and don't really have anything to do with the game or Proton itself.
@lieff Both gists linked in the OP have been updated with the new logs (error persists entirely unchanged).
I have compared your log with mine and first noticeable difference is:
31107.338:001d:0023:err:ntoskrnl:IoCreateDriver failed to insert driver L"\\Driver\\WineHID" in tree
My log do not have that. May be it harmless, but can indicate some incompatibility of your system with wine code. And probably sdl2 can crash in input/hid/pnp code.
Here my log with matched file paths with yours: steam-814380.log
Can you try launching game with that?
LC_CTYPE=C %command%
Paste it to launch options of Sekiro. Steam library - Right click to Sekiro - Properties
@lieff Interesting. I'm downloading a Fedora image right now to see if switching to another distro will solve the issue. I have this sneaking suspicion that EOS's Gala wm is causing issues with SDL2, and EOS doesn't like when you mess with its DE.
@Leopard1907 Tried running it. No difference. Logs look (more or less) the same as well.
Got my Steam controller working in big picture but not ingame (except the mouse). Buttons won't work. I have the default mapping by FromSoftware. I tried settings Forced ON in game controller options. I tried checking unchecking the Xbox/PS/etc configurations on/off. Any idea ?
Got this /lib/udev/rules.d/99-steam-controller-perms.rules
# This rule is needed for basic functionality of the controller in Steam and keyboard/mouse emulation
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# This rule is necessary for gamepad emulation; make sure you replace 'pgriffais' with a group that the user that runs Steam belongs to
KERNEL=="uinput", MODE="0660", GROUP="${USER}", OPTIONS+="static_node=uinput"
# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"
# Valve HID devices over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*28DE:*", MODE="0666"
# DualShock 4 over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666"
# DualShock 4 wireless adapter over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666"
# DualShock 4 Slim over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666"
# DualShock 4 over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"
# DualShock 4 Slim over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"
@Bumbadawg do you have similar
31107.338:001d:0023:err:ntoskrnl:IoCreateDriver failed to insert driver L"\\Driver\\WineHID" in tree
error in log? Can be related. Xbox one controller works fine ingame on my end.
I just thought I'd chime in one final time and say that switching to Fedora 29 fixed the issue. The game runs perfectly fine now with no extra tinkering. I can't say what caused it to not work, but my suspicion is that Gala wm has something to do with it.
I'll leave the issue open as it hasn't been resolved, I just "sidestepped" it because I want to play the game more than I want to solve the issue at the moment.
Hello @Bumbadawg, did you adjust uinput's group in the udev rule like it says needs to be done?
Hello @Bumbadawg, did you adjust uinput's group in the udev rule like it says needs to be done?
Hello @kisak-valve, yes i set it to my username. I also usermod -a -G input myusername and installed the package steam-devices right after posting this.
@Bumbadawg do you have similar
31107.338:001d:0023:err:ntoskrnl:IoCreateDriver failed to insert driver L"\\Driver\\WineHID" in treeerror in log? Can be related. Xbox one controller works fine ingame on my end.
Nope @lieff there was not.
@kisak-valve i link my log if it helps.
NB: i noted my Steam controller keeps disconnecting/reconnecting when i have not Steam running. Is it related / normal ?
[ +0,001817] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/0003:28DE:1102.001B/input/input35
[ +0,057530] hid-generic 0003:28DE:1102.001B: input,hidraw5: USB HID v1.11 Keyboard [Valve Software Wired Controller] on usb-0000:00:14.0-9/input0
[ +0,000985] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.1/0003:28DE:1102.001C/input/input36
[ +0,000359] hid-generic 0003:28DE:1102.001C: input,hidraw6: USB HID v1.11 Mouse [Valve Software Wired Controller] on usb-0000:00:14.0-9/input1
[ +0,000934] hid-generic 0003:28DE:1102.001D: hiddev1,hidraw7: USB HID v1.11 Device [Valve Software Wired Controller] on usb-0000:00:14.0-9/input2
[ +0,716109] input: Microsoft X-Box 360 pad as /devices/virtual/input/input37
[ +5,798842] usb 3-9: USB disconnect, device number 11
[ +0,404852] usb 3-9: new full-speed USB device number 12 using xhci_hcd
[ +0,149156] usb 3-9: New USB device found, idVendor=28de, idProduct=1102
[ +0,000004] usb 3-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0,000003] usb 3-9: Product: Wired Controller
[ +0,000003] usb 3-9: Manufacturer: Valve Software
[ +0,001365] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/0003:28DE:1102.001E/input/input38
[ +0,057567] hid-generic 0003:28DE:1102.001E: input,hidraw5: USB HID v1.11 Keyboard [Valve Software Wired Controller] on usb-0000:00:14.0-9/input0
[ +0,000450] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.1/0003:28DE:1102.001F/input/input39
[ +0,000074] hid-generic 0003:28DE:1102.001F: input,hidraw6: USB HID v1.11 Mouse [Valve Software Wired Controller] on usb-0000:00:14.0-9/input1
[ +0,000381] hid-generic 0003:28DE:1102.0020: hiddev1,hidraw8: USB HID v1.11 Device [Valve Software Wired Controller] on usb-0000:00:14.0-9/input2
[ +0,880760] input: Microsoft X-Box 360 pad as /devices/virtual/input/input40
@Bumbadawg, your log says you're using Proton 3.16 beta, but is missing a header which was added with Proton 3.16-7, which means you're using an unexpected version of Proton. Please opt into Steam's beta and/or go to Steam -> Library dropdown -> Tools and install Proton 3.16 beta from the list.
@Bumbadawg, your log says you're using Proton 3.16 beta, but is missing a header which was added with Proton 3.16-7, which means you're using an unexpected version of Proton. Please opt into Steam's beta and/or go to Steam -> Library dropdown -> Tools and install Proton 3.16 beta from the list.
Thanks a ton @kisak-valve , updating Steam to beta did the trick :) On the side, my Steam controller keeps disconnecting/reconnecting when i have not Steam running. Is it related / normal ?
Just a tip for AMD users: I couldn't get Sekiro working at all (it booted straight into a white screen that it never left) until I set the ICD loader to use the radeon Vulkan driver, instead of the default (for me) AMDVLK Vulkan driver.
If you don't know what that means:
AMD has a choice of two open-source Vulkan drivers: radeon is the name of the one the community started when AMD was taking a while, and AMDVLK is the one AMD eventually got to making. You can have both installed at once and games will pick one--for me, they seem to always pick AMDVLK unless I specify otherwise, which I've so far only had to do for Killing Floor 2 and Sekiro.
And here's how I do that: radeon's ICD file, for me in Arch Linux, lives at /usr/share/vulkan/icd.d/radeon_icd.x<architecture>.json, so I set the launch options in steam to the following:
env VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json %command%
(Having both architecture files at once separated by a colon : tells it to try the first one, then try the second one if that doesn't work, which it won't if the game executable in question happens to be x32 instead of x64.)
@Jimi-James what's your GPU and which AMDVLK version were you using? While it doesn't render correctly, the game does run for me with latest AMDVLK on Polaris.
But yeah, RADV is definitely the driver of choice here.
@doitsujin I'm on an R9 Fury, so Fiji. I just updated, and I'm currently using Arch's mesa-git repository, and I just updated today, so I should be on a pretty new version of AMDVLK? I'm on r40.48d46fa.
Amdvlk is not part of mesa and your amdvlk is from somewhere around 2018-07.
Well, thanks for that patronizing response. I know the AMDVLK driver isn't part of the whole mesa stack. If you had read my first post, you'd have to think that I think mesa is developed by AMD or something to think that. However, it's included in an unofficial repository that Arch users can add, named mesa-git after its main reason for existing.
It's good to know my current version is that old, thanks, but then that means Arch users don't seem to have an easy way to get much more up to date? The version on the AUR currently is not much newer, and also flagged as out-of-date. Hm, this is a sticky situation I'll have to figure out at some point.
I did not intend to be patronizing, you wrote I'm currently using Arch's mesa-git repository, and I just updated today, so I should be on a pretty new version of AMDVLK? I'm on r40.48d46fa. which I read as associating the mesa-git (instead of amdvlk-git) AUR package with amdvlk and it's non-trivial find when that version came available to compare to the releases or release notes.
AMDVLK and mesa/radv are largely independent driver vendors.