Does not work on my laptop.
`Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Laptop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
CPU Family: 0x6
CPU Model: 0x3a
CPU Stepping: 0x9
CPU Type: 0x0
Speed: 3300 Mhz
8 logical processors
4 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
Linux 4.x (64 bit)
Kernel Name: Linux
Kernel Version: 4.18.16-arch1-1-ARCH
X Server Vendor: The X.Org Foundation
X Server Release: 12003000
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime-beta-release_2018-10-24
Video Card:
Driver: Intel Open Source Technology Center Mesa DRI Intel(R) Ivybridge Mobile x86/MMX/SSE2
Driver Version: 3.0 Mesa 18.2.3
OpenGL Version: 3.0
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1058
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 2
Primary Display Resolution: 1366 x 768
Desktop Resolution: 1366 x 768
Primary Display Size: 13.39" x 7.48" (15.31" diag)
34.0cm x 19.0cm (38.9cm diag)
Primary VRAM Not Detected
Sound card:
Audio device: Realtek ALC270
Memory:
RAM: 7422 Mb
Miscellaneous:
UI Language: English
LANG: en_GB.UTF-8
Total Hard Disk Space Available: 191725 Mb
Largest Free Hard Disk Block: 105911 Mb
VR Headset: None detected
Recent Failure Reports:
`
It did work on my desktop though but controller input didn't work (at least with a Steam Controller), but it did work once I mapped the controller keys to keyboard keys.
Hello @hmlendea, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
You can give some of the other Proton runtime config options a try. The video driver for Ivybridge provides an incomplete implementation of Vulkan, so that may be a contributing factor.
Hey, Pid doesn’t run for me too. Thinkpad X220 (Sandy Bridge), Fedora Silverblue 29, Flatpak Steam.
Also with Proton 3.16-4 Beta: steam-218740.log
Hello @jurf, Intel/Sandy Bridge does not support vulkan and no games that need dxvk to run DirectX 10/11 games will work on your system. Your best bet is to try PROTON_NO_D3D11=1 %command% or PROTON_USE_WINED3D=1 %command% in the game's launch options.
@kisak-valve thanks, that worked! Why isn’t it set automatically on systems like mine however?
@kisak-valve steam-218740.log sorry for the huge delay. I rarely use my laptop and I forgot about it.
If you want I can also upload the log from my desktop, where the game works fine (although the Steam Controller didn't work if I used the Xbox mappings (default) but I don't know if it's because of the game, or Proton. It worked when I mapped it to keyboard keys.)
@hmlendea, Proton is trying to use dxvk to run the game, but your system does not have a sane vulkan video driver.
Mesa/Intel/Ivybridge has incomplete vulkan support, so even if you enabled vulkan for your laptop, then you'll most likely encounter other issues and the same launch options mentioned a couple comments ago is your best bet.
@kisak-valve Hello. Thanks for the reply. PROTON_NO_D3D11=1 %command% worked for me.
Now I have a question. Why can't Proton disable DXVK by default, on systems which are known to have poor Vulkan support (like ivybridge)?
Due to xinput I have some issues with the controls and my gamepad (XBOX One S) in this game. The character is always moving more than I do on my pad. This is already in the menu the case, when it moves 2 menu entries instead of one. There is also some input lag by times with the gamepad.
Beside that the game works fine.
Log: steam-218740.log
Sysinfo: https://gist.github.com/NoXPhasma/f842039588ff89403b66abae978a4882
proton 3.7x1 2018-08PROTON_NO_D3D11=1x2 2018-11PROTON_USE_WINED3D=1x1 2018-11PROTON_LOG=1x1 2018-10PROTON_NO_D3D11=1 %command%x2 2018-11PROTON_USE_WINED3D=1 %command%x1 2018-11
I tested Pid and it worked perfectly, besides the fact that my specific controller wouldn't be detected. Input via keyboard works perfectly fine, though. Not sure if this qualifies for whitelisting.
System information from steam