Dead by Daylight
Same problem at SCUM (513710). SCUM uses EAC now and you just get kicked, if you try to join a multi player game
Same problem with Insurgency: Sandstorm, EAC detects Sandbox mode and kicks player for multiplayer.
So, any news about how to run EAC on Linux (have the same Dead by Daylight error)?
So, any news about how to run EAC on Linux (have the same Dead by Daylight error)?
the only way to see the progress is in the wine test https://bugs.winehq.org/show_bug.cgi?id=44235
cant even start the game it says it needs at least directx 11. even if with the config command on the start parameters in steam
I tested Dead by Daylight during free weekend some time ago - it started, but I got blocked by EAC.
@TailsxKyuubi if any game complains that it needs DirectX 11, then it's usually your card not supporting Vulkan or possibly outdated drivers.
@dreamer i have an gtx 970 and updated the driver up to 396 but it havent worked
Any news for EAC games? I tested and current state is like first message here https://github.com/ValveSoftware/Proton/issues/519#issue-354005484
@Zorrototo this should be solve in wine (winehq.org) ;)
You mean with WINE staging? Curent WINE version is older than current Proton version, which itself is older than the staging version of WINE. Vague answer sorry to tell you :)
Also I won't try out of Steam solutions.
The issue is still up, but I guess EAC is working with Valve on solution
https://www.reddit.com/r/linux_gaming/comments/c45f3g/the_easyanticheat_team_is_working_with_valve_to/
Dead by Daylight, Linux User, DX11 Feature 11.0 Error Message
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3095.
@acornleaf posted on 2019-09-28T01:25:54:
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game: 381210
System Information
- GPU:
- Driver/LLVM version: bcmwl-kernel-source - distro non-free
- Kernel version: 4.15.0-20-generic
- Proton version: 4.11-6
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
I have posted this on the PC Bugs section of the Dead by Daylight's forums and no response from the community.
I got a response from Steam Support to submit a ticket here, I hope I'm in the right place. I've tried to fix this but am still dealing with the pop up that said DX11 feature level 11.0 is required to run the engine. I have tried many fixes, details below.
Fixes I've tried:
- Updating Steam Play to Proton 4.11-6
- Changing the game's launch settings to d3dll_UE4Features
- [ In Terminal ]
- sudo apt-get install mesa-vulkan-drivers mesa-vulkan-drivers:i386
- sudo apt install nvidia-drivers
I'm using Linux Mint 19.1 Tessa, devices and drivers below:
== /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0 ==
modalias : pci:v000014E4d00004727sv00001028sd00000010bc02sc80i00
vendor : Broadcom Limited
model : BCM4313 802.11bgn Wireless Network Adapter (Inspiron M5010 / XPS 8300)
driver : bcmwl-kernel-source - distro non-free
Reproduction
Hello @acornleaf, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, 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.
Ubuntu 19.04 | Proton 4.11-11
Crash Log
Proton log
======================
Proton: 1576681293 proton-4.11-11
SteamGameId: 381210
Command: ['/home/ce7bx/.steam/steam/steamapps/common/Dead by Daylight/DeadByDaylight.exe']
Options: set()
======================
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
esync: up and running.
7493.264:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b430000: builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
7493.283:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.284:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\wineboot.exe" at 0x7f6410b30000: builtin
7493.286:000a:000b:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.287:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f6410970000: builtin
7493.287:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f64109c0000: builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
7493.470:000c:000d:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.471:000c:000d:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\services.exe" at 0x400000: PE builtin
7493.473:000c:000d:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.474:000c:000d:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f6b00080000: builtin
7493.474:000c:000d:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f6b001c0000: builtin
7493.475:000c:000d:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f6afffa0000: builtin
7493.475:000c:000d:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
7493.476:000c:000d:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\userenv.dll" at 0x7f6affe60000: builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
7493.503:000f:0010:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.504:000f:0010:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\plugplay.exe" at 0x400000: PE builtin
7493.506:000f:0010:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.506:000f:0010:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f69625a0000: builtin
7493.506:000f:0010:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f69626f0000: builtin
7493.507:000f:0010:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f69624c0000: builtin
7493.512:000f:0010:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
7493.560:0016:0017:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.561:0016:0017:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\winedevice.exe" at 0x400000: PE builtin
7493.562:0016:0017:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.563:0016:0017:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f14cc090000: builtin
7493.563:0016:0017:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f14cc1d0000: builtin
7493.564:0016:0017:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f14cbfb0000: builtin
7493.564:0016:0017:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ntoskrnl.exe" at 0x67a00000: PE builtin
7493.570:0016:0017:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
7493.580:0016:0019:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7f14cb930000: builtin
7493.581:0016:0019:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7f14cb910000: builtin
7493.581:0016:0019:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7f14cbaf0000: builtin
7493.581:0016:0019:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\setupapi.dll" at 0x6a700000: PE builtin
7493.581:0016:0019:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\drivers\\winebus.sys" at 0x7f14cbf70000: builtin
7493.733:0016:0019:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65000000: PE builtin
7493.733:0016:0019:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x6bec0000: PE builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
7493.777:001e:001f:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.778:001e:001f:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\winedevice.exe" at 0x400000: PE builtin
7493.779:001e:001f:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.780:001e:001f:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f7f13f80000: builtin
7493.780:001e:001f:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f7f140d0000: builtin
7493.781:001e:001f:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f7f13eb0000: builtin
7493.781:001e:001f:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ntoskrnl.exe" at 0x67a00000: PE builtin
7493.788:001e:001f:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
7493.795:001e:0021:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\drivers\\mountmgr.sys" at 0x7f7f13e60000: builtin
7493.805:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7f640fd80000: builtin
7493.806:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f640fca0000: builtin
7493.808:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7f640f9e0000: builtin
7493.808:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7f640fa20000: builtin
7493.808:000a:000b:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shlwapi.dll" at 0x68a40000: PE builtin
7493.809:000a:000b:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
7493.809:000a:000b:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65000000: PE builtin
7493.809:000a:000b:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shcore.dll" at 0x64940000: PE builtin
7493.850:000a:000b:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x6bec0000: PE builtin
7493.853:000a:000b:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\shell32.dll" at 0x7f640ff40000: builtin
7493.857:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\steam.exe" at 0x7e8a0000: builtin
7493.859:0008:0009:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71240000: PE builtin
7493.860:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7e7b0000: builtin
7493.860:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7e7f0000: builtin
7493.861:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7e660000: builtin
7493.862:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7e590000: builtin
7493.862:0008:0009:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fdc0000: PE builtin
7493.864:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7e330000: builtin
7493.864:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7e370000: builtin
7493.865:0008:0009:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65200000: PE builtin
7493.870:0008:0009:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shlwapi.dll" at 0x68c40000: PE builtin
7493.871:0008:0009:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shcore.dll" at 0x64b40000: PE builtin
7493.871:0008:0009:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\shell32.dll" at 0x7d5a0000: builtin
7493.912:0008:0009:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x6c0c0000: PE builtin
7493.921:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.922:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\explorer.exe" at 0x400000: PE builtin
7493.925:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.926:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f156fcb0000: builtin
7493.926:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f156fdf0000: builtin
7493.927:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7f156fb10000: builtin
7493.928:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f156fa20000: builtin
7493.928:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
Setting breakpad minidump AppID = 381210
7493.931:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7f156f770000: builtin
7493.931:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7f156f7a0000: builtin
Steam_SetMinidumpSteamID: Caching Steam ID: 76561199016417154 [API loaded no]
7493.937:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7493.938:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\explorer.exe" at 0x400000: PE builtin
7493.940:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7493.941:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7fa638680000: builtin
7493.941:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7fa6387c0000: builtin
7493.942:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7fa6384d0000: builtin
7493.942:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7fa6383f0000: builtin
7493.943:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
7493.945:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7fa638130000: builtin
7493.945:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7fa638170000: builtin
7493.975:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65000000: PE builtin
7493.975:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x6bec0000: PE builtin
7493.984:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\setupapi.dll" at 0x6a700000: PE builtin
7493.984:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x7f156f470000: builtin
7493.997:0008:0025:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\setupapi.dll" at 0x6a900000: PE builtin
7493.997:0008:0025:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x7d370000: builtin
7494.001:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shlwapi.dll" at 0x68a40000: PE builtin
7494.002:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shcore.dll" at 0x64940000: PE builtin
7494.003:0026:0027:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\shell32.dll" at 0x7f156d600000: builtin
7494.008:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\oleaut32.dll" at 0x6a100000: PE builtin
7494.008:0026:0027:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\actxprxy.dll" at 0x960000: PE builtin
7494.009:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65000000: PE builtin
7494.009:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x6bec0000: PE builtin
7494.019:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\setupapi.dll" at 0x6a700000: PE builtin
7494.019:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x7fa637e40000: builtin
7494.030:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shlwapi.dll" at 0x68a40000: PE builtin
7494.030:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shcore.dll" at 0x64940000: PE builtin
7494.032:0028:0029:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\shell32.dll" at 0x7fa636020000: builtin
7494.036:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\oleaut32.dll" at 0x6a100000: PE builtin
7494.036:0028:0029:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\actxprxy.dll" at 0x750000: PE builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
7494.058:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b430000: builtin
7494.059:002f:0030:trace:loaddll:load_native_dll Loaded L"Z:\\home\\ce7bx\\.steam\\steam\\steamapps\\common\\Dead by Daylight\\DeadByDaylight.exe" at 0x400000: native
7494.061:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7e800000: builtin
7494.061:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\MSIMG32.dll" at 0x6b1c0000: PE builtin
7494.064:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71240000: PE builtin
7494.065:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7e5e0000: builtin
7494.065:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7e620000: builtin
7494.065:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7e6a0000: builtin
7494.068:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7e390000: builtin
7494.068:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7e3d0000: builtin
7494.068:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\SHLWAPI.dll" at 0x68c40000: PE builtin
7494.069:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fdc0000: PE builtin
7494.069:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65200000: PE builtin
7494.070:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shcore.dll" at 0x64b40000: PE builtin
7494.070:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\gdiplus.dll" at 0x6f680000: PE builtin
7494.075:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\SHELL32.dll" at 0x7d9b0000: builtin
7494.116:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\imm32.dll" at 0x6c0c0000: PE builtin
7494.121:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-synch-l1-2-0.dll" at 0x6e540000: PE builtin
7494.122:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-fibers-l1-1-1.dll" at 0x6ba80000: PE builtin
7494.123:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-localization-l1-2-1.dll" at 0x6e8c0000: PE builtin
7494.126:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\setupapi.dll" at 0x6a900000: PE builtin
7494.126:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x7d6c0000: builtin
7494.153:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\oleaut32.dll" at 0x6a300000: PE builtin
7494.153:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\propsys.dll" at 0x69e80000: PE builtin
7494.153:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\windowscodecs.dll" at 0x7d530000: builtin
7494.284:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\usp10.dll" at 0x7d350000: builtin
7494.285:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\winsxs\\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.2600.2982_none_deadbeef\\comctl32.dll" at 0x17f0000: PE builtin
7494.287:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\uxtheme.dll" at 0x7d310000: builtin
7494.293:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\WS2_32.dll" at 0x7d2e0000: builtin
7494.295:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\bcrypt.dll" at 0x7d1c0000: builtin
7494.295:002f:0030:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\CRYPT32.dll" at 0x7d1f0000: builtin
7494.295:002f:0030:trace:loaddll:load_native_dll Loaded L"Z:\\home\\ce7bx\\.steam\\steam\\steamapps\\common\\Dead by Daylight\\EasyAntiCheat\\EasyAntiCheat_x86.dll" at 0x10000000: native
7494.297:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-sysinfo-l1-2-1.dll" at 0x65880000: PE builtin
ERROR: ld.so: object '/home/ce7bx/.steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
7494.315:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\kernel32.dll" at 0x7b420000: builtin
7494.346:0031:0032:trace:loaddll:load_native_dll Loaded L"Z:\\home\\ce7bx\\.steam\\steam\\steamapps\\common\\Dead by Daylight\\DeadByDaylight\\Binaries\\Win64\\DeadByDaylight-Win64-Shipping.exe" at 0x140000000: native
7494.348:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\WS2_32.dll" at 0x7f88058c0000: builtin
7494.354:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\kernelbase.dll" at 0x71040000: PE builtin
7494.355:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\sechost.dll" at 0x7f88051f0000: builtin
7494.355:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\advapi32.dll" at 0x7f8805240000: builtin
7494.355:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\gdi32.dll" at 0x7f88052c0000: builtin
7494.356:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\version.dll" at 0x7f88051d0000: builtin
7494.356:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\user32.dll" at 0x7f8805470000: builtin
7494.357:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0x7f8805100000: builtin
7494.358:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0x6fbc0000: PE builtin
7494.358:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\ole32.dll" at 0x65000000: PE builtin
7494.359:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\msacm32.dll" at 0x66440000: PE builtin
7494.359:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\WINMM.dll" at 0x7f88056e0000: builtin
7494.365:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shlwapi.dll" at 0x68a40000: PE builtin
7494.365:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\shcore.dll" at 0x64940000: PE builtin
7494.365:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\SHELL32.dll" at 0x7f88046b0000: builtin
7494.366:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\OLEAUT32.dll" at 0x6a100000: PE builtin
7494.368:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\IPHLPAPI.DLL" at 0x7f8804660000: builtin
7494.369:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\SETUPAPI.dll" at 0x6a700000: PE builtin
7494.369:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\dwmapi.dll" at 0x638c0000: PE builtin
7494.370:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\IMM32.dll" at 0x6bec0000: PE builtin
7494.373:002f:0030:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\api-ms-win-core-sysinfo-l1-2-1.dll" : builtin
7494.373:002f:0030:trace:loaddll:free_modref Unloaded module L"Z:\\home\\ce7bx\\.steam\\steam\\steamapps\\common\\Dead by Daylight\\EasyAntiCheat\\EasyAntiCheat_x86.dll" : native
7494.373:002f:0030:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\CRYPT32.dll" : builtin
7494.373:002f:0030:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\bcrypt.dll" : builtin
7494.373:002f:0030:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\WS2_32.dll" : builtin
7494.373:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\bcrypt.dll" at 0x7f8804530000: builtin
7494.373:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\CRYPT32.dll" at 0x7f8804560000: builtin
7494.374:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\DSOUND.dll" at 0x6d3c0000: PE builtin
7494.374:002f:0030:fixme:font:RemoveFontMemResourceEx (0x877221c1) stub
7494.375:002f:0030:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-appmodel-runtime-l1-1-1.dll" at 0x6de00000: PE builtin
7494.376:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\XINPUT1_3.dll" at 0x7f8804510000: builtin
7494.376:002f:0030:fixme:ver:GetCurrentPackageId (0x32fe94 (nil)): stub
7494.379:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\opengl32.dll" at 0x7a850000: builtin
7494.379:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\wined3d.dll" at 0x7f8804330000: builtin
7494.379:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\dxgi.dll" at 0x7f88044c0000: builtin
7494.380:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\d3d9.dll" at 0x7f88042b0000: builtin
7494.383:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\vulkan-1.dll" at 0x7f8804290000: builtin
7494.384:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winevulkan.dll" at 0x7f8804250000: builtin
7494.384:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\d3d11.dll" at 0x6a340000: native
7494.388:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\X3DAudio1_7.dll" at 0x7f8804230000: builtin
7494.388:0031:0032:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\X3DAudio1_7.dll" : builtin
7494.389:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\X3DAudio1_7.dll" at 0x600000: native
7494.391:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\XAPOFX1_5.dll" at 0x7f8804230000: builtin
7494.391:0031:0032:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\XAPOFX1_5.dll" : builtin
7494.392:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\XAPOFX1_5.dll" at 0x180000000: native
7494.393:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\jsproxy.dll" at 0x71240000: PE builtin
7494.393:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\WINHTTP.dll" at 0x7f88041f0000: builtin
7494.398:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\WLDAP32.dll" at 0x7f8804180000: builtin
7494.398:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\Normaliz.dll" at 0x61f80000: PE builtin
7494.400:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-runtime-l1-1-0.dll" at 0x63140000: PE builtin
7494.401:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\ucrtbase.dll" at 0x7f88032c0000: builtin
7494.402:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-string-l1-1-0.dll" at 0x6dd80000: PE builtin
7494.402:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-heap-l1-1-0.dll" at 0x63800000: PE builtin
7494.402:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-stdio-l1-1-0.dll" at 0x69380000: PE builtin
7494.403:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-convert-l1-1-0.dll" at 0x6d580000: PE builtin
7494.403:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\VCRUNTIME140.dll" at 0x6b0000: native
7494.403:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-locale-l1-1-0.dll" at 0x61540000: PE builtin
7494.404:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-math-l1-1-0.dll" at 0x70580000: PE builtin
7494.404:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-multibyte-l1-1-0.dll" at 0x62c40000: PE builtin
7494.404:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-time-l1-1-0.dll" at 0x68ac0000: PE builtin
7494.405:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-filesystem-l1-1-0.dll" at 0x620c0000: PE builtin
7494.405:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-environment-l1-1-0.dll" at 0x69b80000: PE builtin
7494.405:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-crt-utility-l1-1-0.dll" at 0x6d0000: PE builtin
7494.406:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\MSVCP140.dll" at 0x610000: native
7494.454:0031:0032:trace:loaddll:load_so_dll Loaded L"C:\\windows\\system32\\winex11.drv" at 0x7f8803060000: builtin
7494.465:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-synch-l1-2-0.dll" at 0x6e340000: PE builtin
7494.466:0031:0032:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-fibers-l1-1-1.dll" at 0x6b880000: PE builtin
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk9-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk9-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk8-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk8-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk7-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk7-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk6-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk6-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk5-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk5-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk4-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk4-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk39-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk39-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk38-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk38-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk37-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk37-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk36-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk36-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk35-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk35-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk34-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk34-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk33-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk33-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk32-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk32-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk31-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk31-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk30-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk30-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk3-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk3-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk29-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk29-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk28-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk28-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk27-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk27-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk26-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk26-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk25-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk25-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk24-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk24-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk23-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk23-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk22-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk22-WindowsNoEditor.pak.
LogPakFile: Display: Found Pak file ../../../DeadByDaylight/Content/Paks/pakchunk21-WindowsNoEditor.pak attempting to mount.
LogPakFile: Display: Mounting pak file ../../../DeadByDaylight/Content/Paks/pakchunk21-WindowsNoEditor.pak.
The game has Easy Anti Cheat you can not even reach the main menu as it checks for EAC at game start before menu. Also last time I checked it was working properly you could reach the 'before the menu' screen.
It is not known when it will work?
I need start Steam as root
But i don't know how :\
Hello @KingCerbX, there's a good chance that your desktop environment is configured to run any random .exe with the system-wide wine install with the default ~/.wine wine prefix, which would make it look for a steam-for-windows install in that prefix instead of running the game with Proton. Additionally, there is no situation where running Steam as root would help with troubleshooting.
It is not known when it will work?
probably never.
any update with easy anticheat?
I found this topic, that I guess it's relevant to see updates.
There is little to absolutely no chance that any EAC game will work properly any day.
There is little to absolutely no chance that any EAC game will work properly any day.
Technically Linux will add changes to be easier the configuration of the games with EAC in Wine
Collabora expect their Linux Kernel work for Windows game emulation in Kernel 5.11
A simple explication is in this post
It has been multiple years of speculation and trials but the end result is always the same. I will believe it when it is actually working more than a week long before being blocked or not working anymore. I was enthusiastic before, now I'm realistic. Reality being that even if on paper and early tests things seem to work, it ends up being false hope every time.
We'll see but for now I have seen enough.
I definitely hope this issue gets resolved soon.
Has there been any further development on this? This game is one of the very few reasons I have the need to keep a machine running Windows. There doesn't seem to be too much activity on the handful of forum threads posted in the discussions here
Has there been any further development on this? This game is one of the very few reasons I have the need to keep a machine running Windows. There doesn't seem to be too much activity on the handful of forum threads posted in the discussions here
@sch3p It's been pretty quiet on all the forums I've been on :/. I actually just haven't been playing DBD much lately because of it. I tried in a VM, but that didn't really work to well. I've been playing more linux friendly games instead. I imagine there are a lot of people going this route. Probably a larger silent group of missed gamers than the DBD and Steam devs realize.
Anti-cheat is one of the biggest remaining problems and I think Valve is aware of that.
Wait and see as we say.. until then nothing new. Unfortunately we have to resort to dual booting for some games.
Are there any new developements to this thread?
Not, no EAC game can work on Proton (unless the developers of the game themselves work towards that, which you would know if that was the case), some people on the internet believe it will work on release of the Steam Deck, I don't believe so, which is the sane side of the belief, as we could hear that same kind of delusional belief since 3 years ago for other various reasons.
So until there is something real that you can see and test by yourself, officially announced, the sane and safe thing to assume it that it is not working, and will not until [put another random prediction without any real reason here].
Well, right now, we have some news, but we depend on the developers to give support to this new update.
OK this is going forward then, it is a step, but still doesn't invalidate my point.
I sent this on their official forum, in hope it will be redirected to the devs.
i have friends who work at bhvr, I will ask them and report back here if i get any response back from the actual dev team.
This is actually the reason I haven't been playing anymore. Dual booting / vms are too much hassle for one game.
hi everyone, you can make request to this forum for this game to works with proton https://forum.deadbydaylight.com/en/discussion/282110/eac-on-steam-deck-proton-linux/p3
They are enabling the possibility to use DBD in Steam Deck
https://forum.deadbydaylight.com/en/discussion/282110/eac-on-steam-deck-proton-linux/p4
Yes that is old news, it will probably be next year though knowing how they struggle to do basic stuff to their game.. and how they insist about the fact when it will come will be AFTER the Steamdeck release, since many months they hide behind that to not enable EAC support for Linux... You just have to know their track record of not doing what they say they would do (like the dedicated servers, the match making issues, the ranking system, for all that to announcement, to aimed changes, to when it would be released in game, you add many years apart...)
The game start passing EAC launch inside the public-test branch although EAC still not initialized. Anyone knows what is missing?
Forgot to add the log
steam-381210.log
Anyone knows what is missing?
Linux EAC support?
The game start passing EAC launch inside the public-test branch although EAC still not initialized. Anyone knows what is missing?
Can confirm 6.0.0 is in the exact same state, no progress there.
Thanks captain Obvious.
It's not that obvious, I wouldn't be surprised if BHVR pulled stuff out from the release. Would you?
is not obvious, bhvr release a patch for use eac in linux, but never working
Toxic people being toxic. Just ignore him.
I mean posting about the game not working and sending in the process notification to many people, for this really "important"information, is OK then?
It is OBVIOUS the game is not working, as it is not working since the beginning of this issue, and there has been no new information about EAC linux compatibility for this game from its devs.
At least if you post here, post relevant information, maybe the day it will work, or the day there is an official announcement to give more info about the issue.
Until then, no need to post here such information, as obviously it is useless to let us know what we already know: the game doesn't work under Proton, because of EAC.
Thanks.
@Zorrototo please be respectful. The snarky comments each time someone posts is not helpful.
I think what is not respectful is bumping this issue for useless comments. Like this message (but as your reply is directed to me I'll answer), it generates useless notifications to everyone. No need to remind everyone that the game doesn't work under Proton when nothing has changed regarding that, that's my point. I hope next notification will be for something actually relevant.
Maybe it shouldn't have been directed directly at you as i want everyone to be respectful ofc.
I'm just saying a post every once in a while is hardly spam and not everyone who follows a game issue closely, so posting to say they also experience the issue is not that big of an offense.
Say your opinion, but please try to be respectful about it or else it will just create a bad unwelcome atmosphere. Imo posting comments like "Thanks captain obvious" and saying what people post are "useless comments" seem like examples of that.
We don't need more of that in the Linux world.
But i agree that this is also a stupid bump and I will let this be the last from me. I will also mark my two posts as off topic.
EAC now loads perfectly fine with the last update to the Proton-EAC-Runtime, but as soon as the game tries to initialize EAC, it crashes on the Unix side.
steam-381210.log
gamelauncher.log
error logs, it seems that is not a problem with dbd, it seems to wine, but I don't know how, thanks for any suggestion
@jomarocas experimental have raised the minimum driver requirements.
You need atleast the 510 or above drivers for nvidia
I've been trying to debug this for a while, but I did get an instance where the game loaded all the way to the Main Menu. I was dumb and forgot to keep the log for diffing, so I'm trying to get it again as it seems like it's a timing issue?
I didn't have any special launch args when it started, and other people have reported that trying multiple times eventually gets you in. I'll post back when I have a log of it working.
The EAC is now initializing. We can now play solo. It is possible to enter lobbies and meet players, but when the game is launched, we get the error "Disconnected from host".
According to the thread on the BHVR forums, the Epic version is fully working: https://forum.deadbydaylight.com/en/discussion/282110/eac-on-steam-deck-proton-linux/p19
The Steam one is still getting disconnected when everyone in the lobby is ready and the game is starting. Here are the logs from
this moment:
steam-381210.log
Full logs:
steam-381210.log
Launch options:
gamemoderun PROTON_LOG=1 %command%
I don't see anything that would implicate the client. What do you think?
I'm getting the same error log as you @glamothe9
LogNet: Warning: [UDBDEngineUtils::HandleNetworkFailureGame]: FailureType: ConnectionLost, Error: 'Your connection to the host has been lost.'
LogNet: Warning: [UDBDEngineUtils::HandleNetworkFailureGame] Handling unexpected unreal connection failure. GameFlowStep=OnlineLobby, IsDisconnected=true
LogNet: Warning: [UDBDEngineUtils::HandleNetworkFailureGame] Game is already disconnected. Discarding failure.
LogNet: Error: UEngine::BroadcastNetworkFailure: FailureType = ConnectionLost, ErrorString = Your connection to the host has been lost., Driver = GameNetDriver SteamNetDriver_2147480990
It seems to me that it's something to do with Proton's network drivers not playing nice with Unreal Engine's network drivers. Maybe an update to the GameNetDriver and/or SteamNetDriver would fix the issue?
Really seems like this is the last barrier to getting DBD to work on Steam. Everything else works 100% perfectly.
Edit:
After doing a bit of research into Unreal Engine it seems there's a bug that has since been addressed but it might affect DBD. As far as I could find, DBD is using Unreal Engine 4 still, just not sure which version exactly but if it's less than 4.27 then the bug is present. Anyway, here's the bug that I think might be causing the issue from the Unreal Engine documentation:
In Unreal Engine 4.27.0, an issue with the FUniqueNetIdSteam structure prevented Steam Sockets from creating successful connections. This issue is fixed in 4.27.2 and later.
Full details here: https://docs.unrealengine.com/5.1/en-US/using-steam-sockets-in-unreal-engine/
Could also be that the DBD devs need to setup the Steam Online Subsystem.
Documenation for that here: https://docs.unrealengine.com/5.1/en-US/online-subsystem-steam-interface-in-unreal-engine/
Apparently people are saying it just works now?
Apparently people are saying it just works now?
Yes, it is working without any tweaks, as long as you have Proton EasyAntiCheat Runtime installed. Just a matter of time until BHVR announces official support, me thinks
I get an EAC error "EAC client cannot be instantiated" before reaching main menu. I verified the files, tried Proton 7 and Experimental, does not work for me. It does not work on Vermintide 2 either when it should so maybe something is wrong here (I imported file from Windows and updated the game).
LogMirrors: Warning: [IMirrorsCommand::Tick] Overly long tick in mirrors command taking 13.196598 seconds. Ignoring tick
LogRealTimeMessaging: Warning: RTM: Long time between RealTimeMessaging tick: 13.196598. This could result into websocket disconnection!
GUI: Warning: Popup Sequencer: Error popup requested (not displayed yet): Title="QUIT GAME" Message="EAC client cannot be instantiated." Priority=0
GUI: Warning: Popup Sequencer: Error popup displayed: Title="QUIT GAME" Message="EAC client cannot be instantiated." Priority=0
Make sure the EAC runtime is installed. It works for me as well.
Should Proton EAC Runtime be automatically installed? Is this a dev setting?
I have it installed unfortunately. No it is not automatic. Find it in your library, in the Tools section, it is called "Proton EasyAntiCheat Runtime".
//EDIT: After rertying a dozen time, and doing many things trying to fix it, it magically works after a computer restart (I mean I'm in main menu now). Will update if I find what worked.
//EDIT2: after restarting the game, it doesn't work anymore. Will restart computer after confirming it can't work right now multiple times.
//EDIT3: it is inconsistent but I can restart the computer and start the game, and it works, sometimes.
I was able to launch the game, fiddle with the rift and settings, get into a lobby but I get kicked as the game loads (error 500).
Proton 7
Proton EAC Runtime installed
latest mesa
Reading DBD forums (https://forum.deadbydaylight.com/en/discussion/282110/eac-on-steam-deck-proton-linux/p23) it seems BHV is enabling momentarily the game at EAC globally to test and try to get the game working on the steam deck.
So someone is working on support, but we can't expect the game to work consistently (yet).
OK nice to know thanks for bringing relevant info to this issue here on GitHub. I also had error 500 at some point yesterday and stopped insisting as I figured something changed when this new error appeared. It was also wasting other people's time by waiting in lobby, starting the post lobby loading, then bringing everyone to main menu with a connection lost / error 500.
After it eventually was not working anymore, there has been some new good news. It works on the EPIC version, and it is really easy to setup (basically installing it in the Heroic Games Launcher, and copying the EasyAntiCheat folder in two locations, and adding a settings in the launcher to point to the Steam EAC runtime.
https://forums.bhvr.com/dead-by-daylight/discussion/361429/unofficial-linux-support-thread
I think the game on EPIC received changes on the EPIC side, I will try to find what the difference is by comparing folders.
//EDIT: indeed, the game files show that the EPIC version has a different file structure and naming, there are some new EGS folders, and files follow a naming like -EGS.pak instead of -WindowsNoEditor.pak which means to me it is kind of meaning that work would need to be ported over to the Steam version of the game to expect it to work the same.
Whatever, as I can merge the Steam and EPIC account for DBD https://account.bhvr.com/account/my-account/games/dbd it is good enough for me if I can play from HEROIC launcher. I hope they make the proper change for good Linux/SteamDeck support, but knowing these devs they will take long time if they eventually do it.
@kisak-valve
Could you please check this problem?
The game doesn't launch on Intel Arc A770, it just crashed and unreal engine submit error window pops up.
Here's proton log. It works on the same system with AMD RX580, perhaps the problem in the drivers?
proton_DBD.log
bump
So if anyone also struggles with launching Dead by Daylight on Intel GPUs just make a file Dead by Daylight/DeadByDaylight/Binaries/Win64/dxvk.conf with dxgi.customVendorId = 1002. This should also help with other UE4 titles. Thanks to @mbriar
Another thing I learned is that DBD can be launched with -DX12 argument and Intel GPUs don't crash there either. But the performance of VKD3D is kinda crappy on Intel.
A note regarding the Intel DG2 (A750/A770), there is a lack of VM_BIND support in the i915 driver:
https://lists.freedesktop.org/archives/intel-gfx/2023-April/324237.html
There's some more discussion about that here:
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/234
Generally worse-than-expected intel performance when trying DX12 is because of a lack of some sparseResidency features, which Mesa is working on, but that requires VM_BIND which is (again) missing in DG2.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/5003
Generally worse-than-expected intel performance when trying DX12 is because of a lack of some sparseResidency features
No, that is not how it works. The sparseResidency features are a requirement for D3D12 feature level 12_0 and games making use of D3D12 Tiled Resources will not work at all on Intel until this is implemented. If a game already works on Intel right now then that means it doesn't make use of that feature and implementing it won't make it run any faster. Unreal Engine 4 games such as this don't use Tiled Resources in DX12.
Latest updates from Epic Games broke EAC compatibility. Now (with workaround) it says that DeadByDaylight-EGS-Shipping.exe is missing.
Hey guys I just bought dbd after seeing a lot of people saying it now works on linux but every time I open it it crashes in less than 5 min every time, i can barely get through half the tutorial before it crashes. When it crashes it closes a bunch of apps and shuts off my monitors so i have to unplug and replug my pc so idk what's going on. I have the proton easeyanticheat runtime installed but I'm new to Linux so i might just be doing something wrong but I'm on pop os if that matters. If anyone has a fix please lmk 🙏
Dead by Daylight EAC Not Initiallize
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7028.
@wuilmerj24 posted on 2023-08-20T02:41:48:
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game:381210
System Information
- GPU: Integrated ryzen 7 5700G
- Video driver version:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.0-devel - Kernel version:
6.1.0-11-rt-amd64 - Link to full system information report as Gist:
- Proton version:
8.0
I confirm:
- [ ] that I haven't found an existing compatibility report for this game.
- [ ] that I have checked whether there are updates for my system available.
Symptoms
When I open Dead by Daylight, I can play with the bots, but when I play online, it reaches the lobby, but upon loading the game, it disconnects me.
Reproduction
always
Make sure to install the Proton EasyAntiCheat Runtime from Steam library in your Tools.
@Zorrototo Yes, I have it installed.
Is the game using Proton 8 to start? Maybe verify from Steam (right click on game/tool, properties, local files, verify) all of this including the game files.
You need to use the latest Proton to be able to play an EAC (compatible) game. You can force it for a specific game in its Properties->Compatibility, or globally in Steam Settings.
Dead by Daylight [381210]
Issue transferred from https://github.com/ValveSoftware/Proton/issues/7756.
@canofjuice posted on 2024-05-22T20:48:31:
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game: 381210
System Information
- GPU: GTX 750 Ti
- Video driver version: NVIDIA 550.78
- Kernel version: 6.8.9
- Link to full system information report as Gist. Forgot to include Runtime System Info...
- Proton version: Tested 9.0-1 and Experimental
I confirm:
- [ Y ] that I haven't found an existing compatibility report for this game.
- [ Y ] that I have checked whether there are updates for my system available.
Symptoms
Game crashes when i tried to enter a match. Specifically when the game shows "offerings" added by players.
Reproduction
Use Proton 9.0-1 or Experimental, Open the game normally, find a match, ready up until the game starts and shows the "offerings" screen.
This crash doesn't occur while using Proton 8.0-5, but anything 2D flickers and there is noticeable lag/performance drop.
Additional Notes
Tried running on EndeavourOS and now Bazzite, same issue. Both running KDE 6.
Steam on Bazzite uses the Flatpak Version.
Replying to https://github.com/ValveSoftware/Proton/issues/519#issuecomment-2125756247
I'm having the same problem, in various versions of Proton, GNOME or KDE
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game: 381210
System Information
- GPU: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
- Video driver version: NVIDIA 550.78
- Kernel version: 6.9.3-1-MANJARO
- Link to full system information report as Gist: https://gist.github.com/AnonymerNiklasistanonym/9b5cc36934b9221a55c7c475a9cff992
- Proton version: experimental-9.0-20240522
(I tried a lot of versions in the last months but it was always the same issue: GE-Proton9-5, GE-Proton9-7, Proton: Experimental, Proton: Default)
I confirm:
- [ ] 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.
Proton Logs: https://gist.github.com/AnonymerNiklasistanonym/f4d1e0f374f8af3b1e5c4bc7fca5e954
Symptoms
For the past months after I updated Manjaro I have gotten only a black screen (with audio - title video starts automatically playing too after some time too since I can hear it's audio) when starting 'Dead By Daylight'.
Since this didn't fix itself after the last 3,4 updates (there are a lot of issues are happening right now under KDE Wayland so I didn't pursue it much - but it was happening on X11 too) and verifying gamefiles/reinstalling didn't do the trick either I ran the game with PROTON_LOG=1 %command% and saw the line err:vkd3d-proton:dxgi_vk_swap_chain_recreate_swapchain_in_present_task: Failed to create swapchain, vr -3. repeatedly showing up.
Searching this via google didn't return any results so today I tried duckduckgo and found this issue https://github.com/HansKristian-Work/vkd3d-proton/issues/1734 where I don't really understand what was going on but I tried adding VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json before the %command% part and suddenly the game started as if everything was fine (on nvidia wayland nonetheless!).
So I just wanted to add it to this issue in case anyone else runs into the same problem.
Reproduction
- Start the game (on my hardware I guess since most people don't seem to have that problem I would assume its connected to my kernel and proprietary NVIDIA driver version)
Hello @hogsmead, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.
@hogsmead I tried to repro this, but I'm not seeing any hang. I was just playing a random game match and then at the end, I was able to get back to the main menu without issue - are you doing something different from this?
I have a couple of suggestions:
- Have you tried Proton - Experimental yet? Perhaps this issue is already fixed upstream.
- Could you try dropping in vkd3d-proton from Proton 8.0 into Proton 9.0? It is pretty simple:
cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib64/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton 9.0 Beta/files/lib64/wine/vkd3d-proton/.
cp -rf ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/vkd3d-proton/* ~/.steam/steam/steamapps/common/Proton 9.0 Beta/files/lib/wine/vkd3d-proton/.
After testing, you can just use the "verify integrity of files" option on Proton 9.0 in the steam properties for the tool to get back to the original files :)
After the 8.2.0 update, Easy Anti-Cheat is sometimes kicking me from lobbies due to "modified game files" (even though I don't have any). Already verified the integrity of the game files and the problem hasn't gone away.
In the 8.2.0 update, the anti-cheat was updated:
Upgraded EasyAntiCheat to new version. (PC only)
I have already contacted the developers about it, and so far I have not received a response.
Replying to https://github.com/ValveSoftware/Proton/issues/519#issuecomment-2330616447
i also confirm that proton experimental no working, im going to back to proton 9.0.2
DBD crashes after playing a couple of matches when using Proton 9 or Experimental. No crashes with Proton 8.
Hello @moonlitpath, blind guess, does the game run more reliably with Proton 9.0 and the launch options set to PROTON_DISABLE_NVAPI=1 %command%?
Hi @kisak-valve. Seems like this fixes the issue.
Never mind. It's still crashing.
My game was freezing with ProtonGE-9-5, switching back to proton 9-0-3 seems to have fixed it..
After the 8.2.0 update, Easy Anti-Cheat is sometimes kicking me from lobbies due to "modified game files" (even though I don't have any). Already verified the integrity of the game files and the problem hasn't gone away.
verifying game files fixes this
Anti-Cheat issue is not related to Proton. People playing on Windows also get kicked from the game. Verifying game files doesn't fix it.
Anti-Cheat issue is not related to Proton. People playing on Windows also get kicked from the game. Verifying game files doesn't fix it.
yes its related, DBD working good with 9.0.3. With experimental the game no working, verify the game always crash
Anti-Cheat issue is not related to Proton. People playing on Windows also get kicked from the game. Verifying game files doesn't fix it.
yes its related, DBD working good with 9.0.3. With experimental the game no working, verify the game always crash
Unfortunately, using Proton 9.0-3 doesn't work for me w. DBD.
Downgrading to 8.0-5 won't fix the issue aswell.
If I remember correctly, It supposed to work w. Proton 8 for me.
Normally when starting the game I always saw the EAC Logo when loading it, this is not the case now. So somehow EAC doesn't get called by DBD, which in fact is the error I get.
You have been kicked from the Server because of a failure to validate your account
through Easy Anti-Cheat (error code 4)
Additional Info: Anti-cheat client protection not active (NullClient)
Maybe the issue might lie w. DBD using an outdated EAC for their game, while ours is more up-to-date and therefore not compatible? (Just a theory)
I tried with ProtonGE version 9.16, and it's the best one that has worked for me. Sometimes the issue with EAC appears, but once I do the 'verify integrity of game files,' it works. Although sometimes it doesn't fully load, I have to restart and verify again, and then it works. It's the best version with which I've been able to play correctly.
Replying to https://github.com/ValveSoftware/Proton/issues/519#issuecomment-2425100616
For the sake of it I launched and played a game until I died https://i.imgur.com/yUYFDeP.jpeg it works. I checked and it was Proton Experimental set in the game Properties. I reinstalled recently like 2 weeks ago so maybe there is something wrong in your game files. If you have the bandwidth, uninstall the game, stop Steam, delete the game folder and the Proton prefix folder, reboot, and reinstall the game.
I've tried what you said. Unfortunately it didn't work.
I uninstalled the game, deleted the Proton prefix folder and the game folder, rebooted my PC, set to Proton Experimental and reinstalled the game.
When starting a Custom Game as a Killer, the same error message pops up again, kicking me after a short while in the game :disappointed:
Replying to https://github.com/ValveSoftware/Proton/issues/519#issuecomment-2425117966
I just played a few custom games, it works for me. Did you also verify/reinstall the EAC Runtime? I have the bleeding edge Experimental Proton by the way, if that makes any difference. Did not try with other Proton version but I expect it to work just fine as with the Experimental one.
Game freezing issue during loading screen or while a new match starts
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8231.
@Miyutsukka posted on 2024-11-10T13:34:23:
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game: 381210
System Information
- GPU: Mesa Intel® UHD Graphics 770
- Video driver version: xserver-xorg-video-intel 2:2.99.917, mesa-va-drivers 24.2.3-0
- Kernel version: 6.11.0-103009-tuxedo (64-bit)
- Link to full system information report as Gist:https://gist.github.com/Miyutsukka/3a013a9bade2c48d9308043fe385265c
- Proton version: 9.0-3
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 freezes while it loads into a new match or while the new match starts.
Reproduction
- Open game
- Start a match (both custom and online have the same issue)
- Load into match and wait until it either freezes or starts as intended
Dead By Daylight / EasyAntiCheat "unexpected error"
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/11527.
@duncte123 posted on 2024-11-28T13:04:53:
Your system information
Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: ROG RAMPAGE VI EXTREME
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i9-7980XE CPU @ 2.60GHz
CPU Family: 0x6
CPU Model: 0x55
CPU Stepping: 0x4
CPU Type: 0x0
Speed: 4200 MHz
36 logical processors
18 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System Version:
Ubuntu 24.04.1 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 6.8.0-49-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12101011
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20241024.105847
Client Information:
Version: 1731433018
Browser GPU Acceleration Status: Disabled
Browser Canvas: Unavailable
Browser Canvas out-of-process rasterization: Disabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Disabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Disabled
Browser Rasterization: Disabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Disabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Unavailable
Browser WebGL2: Unavailable
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 535.183.01
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1e07
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 18.74" x 10.55" (21.50" diag), 47.6cm x 26.8cm (54.6cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 11264 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Realtek ALC1220
Memory:
RAM: 63973 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 937498 MB
Largest Free Hard Disk Block: 686376 MB
Storage:
Number of SSDs: 4
SSD sizes: 2048G,2000G,1000G,500G
Number of HDDs: 0
Number of removable drives: 0
- Steam client version (build number or date): 1731433018 / Tue, Nov 12 18:10 UTC -08:00
- Distribution (e.g. Ubuntu): Kubuntu 24.04
- Opted into Steam client beta?: No
- Have you checked for system updates?: Yes
- Steam Logs: steam-logs.tar.gz
- GPU: Nvidia RTX 2080 TI
Please describe your issue in as much detail as possible:
Here's the easy anticheat logs:
service.log
anticheatlauncher.log
When I try to launch Dead by Daylight I just get an "unexpected error" during whatever EAC is doing.
Steps for reproducing this issue:
- Install Dead By Daylight on a fresh machine
- Try to run the game
- Observe as game does not go beyond EAC screen
Also been talking to DBD support about this. During that we've determined that "EOS-EAC" (a newer version with epic online services) might be causing the issue as older EAC versions in games work just fine. An example of a game that gives me the exact same error is "Goose Goose Duck" (1568590)
Hello @duncte123, can you try setting the game's launch options to WINE_CPU_TOPOLOGY=32 %command% and see if that has an effect?
Hello @duncte123, can you try setting the game's launch options to
WINE_CPU_TOPOLOGY=32 %command%and see if that has an effect?
That worked, I am in game
I'm new to reporting a problem with my game here, I just comment on this issue, correct? Assuming that's the case, here's the deal. First, some information about my setup:
OS: EndeavourOS Linux x86_64
Host: GF63 Thin 11UC REV:1.0
Kernel: 6.12.1-arch1-1
DE: Plasma 6.2.4
CPU: 11th Gen Intel i5-11400H (12) @ 4.500GHz
GPU: Intel TigerLake-H GT1 [UHD Graphics]
GPU: NVIDIA GeForce RTX 3050 Mobile
I can't find out what my current Nvidia drivers are as nvidia-smi has the following error message: "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running." Maybe y'all have some thoughts on how to get that working, the short version of that is I downgraded my Nvidia drivers to 550.something because the latest drivers made most of my games crash, and downgrading fixed the problem instantly (these were the same Nvidia drivers that bricked Far Cry 5, if memory serves).
So here's my Dead by Daylight problem. Prior to Thanksgiving/The Doomed Course update with the Houndmaster killer and Taurie Cain survivor, my game ran just fine. It had the occasional crash, but my friends also have that happen sometimes so I just blame that on DBD being a bit janky. However, ever since this update dropped, I can't even play the game. It crashes on startup every single time, even though I've tried a variety of proton version and a few GE versions. At best, I have the anti-cheat screen load up and shortly after an Unreal Engine crash report pops up (see screenshots). I've tried a variety of launch options, such as -dx11, but to be frank I haven't been able to find much information to help guide my attempts there, and I really don't understand much about how launch options work, or if they will even help here. Please help! I'm happy to provide further information if needed, I'll admit I'm still used to reporting issues like this, so just let me know what commands to run for information or whatever else is needed to try and address this. One last note is that I played 100+ hours of DBD before this update dropped and broke my game, so that really speaks to how stable I had it running prior to this issue suddenly coming up.
Proton versions I've tried: GE-Proton9-20, GE-Proton9-19, GE-Proton9-18, Proton Experimental, Proton 9.0-3, Proton 8.0-5, Proton 7.0-6. On a couple of occasions I had Proton 8.0-5 launch the game (no launch options) but it wasn't online and it had atrocious frames, so I assume that's a dead end. However, because I didn't always have the exact same result of loading EAC and crash, I suspect this is something that Proton can fix as it improves, so if nothing else I can wait this out. Still, I prefer something sooner if possible! Thanks.
Do the basics, delete the prefix folder ~/.local/share/Steam/steamapps/compatdata/381210/, select the latest Proton version in Steam Settings (or Force the version in the game Properties), restart Steam or the computer, verify the game files from the game Properties, and start the game (in that order).
Do the basics, delete the prefix folder
~/.local/share/Steam/steamapps/compatdata/381210/, select the latest Proton version in Steam Settings (or Force the version in the game Properties), restart Steam or the computer, verify the game files from the game Properties, and start the game (in that order).
Is Proton Experimental considered the latest? That being the case, I've done all that in order, as requested. Upon starting the game, the same process of loading EAC/crashing occured as I described in my initial post.
Proton Experimental as the name hints, is EXPERIMENTAL, it is meant to get the latest and greatest updates of Proton, at the risk of having a broken Proton sometimes. The latest is Proton 9.
Maybe clean again, and enable Proton logs then to try to see if relevant errors pop up. In game Properties, in the Launch Options, add PROTON_LOG=1 %command% so it creates a log in your Home folder when starting the game. Post it here then.
Proton Experimental as the name hints, is EXPERIMENTAL, it is meant to get the latest and greatest updates of Proton, at the risk of having a broken Proton sometimes. The latest is Proton 9.
Maybe clean again, and enable Proton logs then to try to see if relevant errors pop up. In game Properties, in the Launch Options, add
PROTON_LOG=1 %command%so it creates a log in your Home folder when starting the game. Post it here then.
Alright so I cleaned again, this time switched to Proton 9. This time, the game started up, but the frames were atrocious (unplayable levels). Attached is the log produced from the launch option you said to use.
steam-381210.log
Hello @matthoward123, that's just from the game running on the Intel GPU. You still need to fix your NVIDIA driver stack if you want to use that GPU.
Hello @matthoward123, that's just from the game running on the Intel GPU. You still need to fix your NVIDIA driver stack if you want to use that GPU.
This has actually been a source of confusion for me, I haven't been able to figure out how to do that. Could you provide some help with this? Or even just a link to an Arch Wiki discussion or somewhere that discusses this? Thank you so much, if I can resolve this issue then I think that means I have the problem of crashing on startup officially solved.
Alright so it looks like things are running smoothly and stable, no crashes thus far. I updated my Nvidia drivers and that seemed to work. I'll consider this a fixed problem barring some bizarre thing happening. Thanks for the help!
Update. So now I'm having trouble getting my NVIDIA GPU to work again, when I ran nvidia-smi I got this message, so it seems clear that the GPU isn't working like it should be: "Unable to determine the device handle for GPU0000:01:00.0: Unknown Error" Any ideas for what to do?
Replying to https://github.com/ValveSoftware/Proton/issues/519#issuecomment-2518061676
Same splash screen; DBD was working a week or 1.5 weeks ago and today it started showing "Fatal error!" on a window titled "The UE-DeadByDayLight Game has crashed and will close".
On steam cmd the error is "x11drv: Can't allocate handle for display fd" and "x11drv: Can't store handle for display fd"
I re-installed, changed prefix, rebooted, verified files; none of them worked.
Dead by Daylight keeps kicking me, due to Anti-cheat client protection not active (NullClient)
Issue transferred from https://github.com/ValveSoftware/steam-for-linux/issues/11741.
@LinuxSquare posted on 2025-02-09T12:52:12:
Your system information
- Steam client version (build number or date): 1738026274
- Distribution (e.g. Ubuntu): Arch Linux
- Opted into Steam client beta?: No
- Have you checked for system updates?: Yes
- Steam Logs: steam-logs.tar.gz
- GPU: Nvidia
Please describe your issue in as much detail as possible:
When I install & start Dead by Daylight on my PC, it starts up and I can create a custom game. After starting the custom game, DBD alerts me:
You have been kicked from the Server because of a failure to validate your account
through Easy Anti-Cheat (error code 4)
Additional Info: Anti-cheat client protection not active (NullClient)
I have tried uninstalling the game, removing the prefix, verifying the game files, switching to a different Proton-version. Everything ended up in the same error.
I can play for a few seconds, until the DBD server kicks me.
I do own a Steam Deck and on the Steam Deck, DBD works flawlessly without tinkering. (Last Checked: Today in the morning)
I have generated a proton-log, if this is going to help: steam-381210.log
Steps for reproducing this issue:
- Install DBD
- Start a custom game
- observe
Severe graphical artifacts in Dead by Daylight on Linux
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8788.
@Sayano78 posted on 2025-06-09T22:28:56:
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game: 381210
System Information
Distro: EndeavourOS (Arch Linux base)
DE: KDE Plasma (tested on both Wayland and X11)
GPU: AMD Radeon RX 6800
Driver: Mesa 25.0.5-arch1.1 (also tested with mesa-amber and mesa-git)
Steam version: 1.0.0.82-2
Proton versions tested:
- GE-Proton10-3
- Proton Experimental
- Proton 9.0-4
- Proton 8.0-5
- GE-Proton7-55
I confirm:
- [x] that I have checked whether there are updates for my system available.
Symptoms
The game suffers from heavy graphical glitches and visual artifacts during gameplay. Previously, it would also freeze completely, requiring a full system reboot. Those freezes are now resolved, but the graphic corruption persists, making the game visually unplayable. I've tested nearly every known workaround found in ProtonDB, GitHub, Reddit, and various forums — none have resolved the issue reliably.
Observed Issues
Graphical artifacts such as broken lines, flashing shadows, distorted textures, flickering, or visual tearing.
Graphical corruption persists regardless of in-game settings or Proton version.
Troubleshooting Already Tried
Switching between Wayland and X11 sessions.
Forcing 60 Hz refresh rate and different resolutions.
Steam Launch Options tested:
RADV_DEBUG=llvm
RADV_DEBUG=nodcc
PROTON_USE_WINED3D=1
MESA_GL_VERSION_OVERRIDE=4.5
DXVK_ASYNC=1
PROTON_NO_ESYNC=1
PROTON_NO_FSYNC=1
Disabling Steam Overlay and Steam Input.
Disabling in-game HDR and vsync.
Using a custom DXVK build, placed manually in game directory.
Testing through Lutris with Wine-GE and manual overrides.
Using WineD3D to force OpenGL backend.
Installing and testing mesa-amber and mesa-git.
Clean system installs tested — no overclocking, no other game is affected.
Important Notes
This issue does not affect any other game, even other Unreal Engine or DX11 titles.
It appears to be specific to this GPU model and game engine combination.
Closing Statement
I believe this may be a Proton or DXVK compatibility bug with RDNA2/RX 6800 and Unreal Engine-based games like Dead by Daylight.
video showcasing the graphical artifacts:
Hello @Sayano78, your system is configured to use AMDVLK. Can you test how the game behaves with mesa/RADV?
Hello @Kisak-valve, I have used the launch option "AMD_VULKAN_ICD=RADV %command%" to force the game to run with RADV instead of AMDVLK, and the issue with the graphical artifacts still persists. :(
Hello @kisak-valve, I also just tried the launch option "RADV_FORCE_FAMILY=radeon RADV_PERFTEST=aco VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%" and the problem still persists
@kisak-valve Problem solved. Apparently, I didn't have RAVD installed. When I installed it, I set the launch parameter "AMD_VULKAN_ICD=RADV" and it magically resolved itself. There are no more graphical errors. Thanks for letting me know about RADV.
Dead by Daylight
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9092.
@Skyzzera posted on 2025-10-10T14:06:32:
Compatibility Report
- Name of the game with compatibility issues: Dead by Daylight
- Steam AppID of the game: 381210
System Information
- GPU: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
- Video driver version: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3
- Kernel version: 5.15.0-153-generic
- Proton version: Proton experimental
I confirm:
- [Yes] that I haven't found an existing compatibility report for this game.
- [Yes] that I have checked whether there are updates for my system available.
Symptoms
I press play, it starts to load/initializing, it stops loading/vanishes suddenly, then it no longer says "running" on the bar on the left and nothing happens anymore.
Reproduction
Always since the Walking Dead update (29th July 2025). My friends and I theorize it's the new anticheat. Has worked before. Video attachment shows error.
https://github.com/user-attachments/assets/f5e2f944-3fbc-43fc-bfcf-d8424b952a1b
Hello @Skyzzera, mesa 23.2 lacks video driver features required by DXVK bundled inside of Proton Experimental. You could try updating mesa using a PPA like kisak-mesa stable.
If that doesn't help, then 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.
Apologies if this is not the place, but I exhausted every form of contact with BHVR and after contacting Steam Support, I was lead here.
I recently (and other people I found on reddit / Steam discussions) got banned from the game, BHVR claimed "Exploits: Abusing bugs or errors in design to gain a competitive advantage" (and later in Support mentioned "third party software/exploits"), which I didn't. My first thought was Mangohud, but I had been playing fine for months with it (and Experimental).
The reason I'm posting here is because the common denominator in all these bans was the use of Proton Experimental (in my case Bleeding Edge), here are the threads of the people who got banned (and decided to post, it's unclear if others are affected): here, here and here.
I was also using the following launch argument due to the "time bomb" issue since I experienced a few times:
LD_PRELOAD="" VK_LOADER_LAYERS_ENABLE=VK_LAYER_MANGOHUD_overlay_x86_64 %COMMAND%
My question is if this could've been caused by something in Experimental anytime between late October - early November? or if the EAC runtime not being updated (somehow) could make this happen? Just mentioning as I saw it update days later after the fact (though I guess it not being updated wouldn't allow me to log into the game).
I understand if this comment is removed, but as mentioned earlier: BHVR refuses to acknowledge their mistake and I've exhausted every way with them (to the point of them pretty much threatening to close my support account).
If this comment ends up removed, please @ me. Thanks.
You missed to contact the proper channel which handles game bans, EAC. Contact them and regroup with your friends maybe too if multiple people got actually falsely banned.
You missed to contact the proper channel which handles game bans, EAC. Contact them and regroup with your friends maybe too if multiple people got actually falsely banned.
Hi, the people from those threads aren't my friends, just other people I found to have been banned under the same premise which shared Proton version in common, basically.
I had already considered that but I don't have a Reference ID so I can't really send an appeal there.
I've been getting EAC issues (Error Code 4) for a few months now and it doesn't seem to matter what I'm doing as I've tried updating software, AND swapping out hardware, even using a bunch of different Proton versions (Experimental, Hotfix, 9.0-4, 10.0-4)
I've been getting EAC issues (Error Code 4) for a few months now and it doesn't seem to matter what I'm doing as I've tried updating software, AND swapping out hardware, even using a bunch of different Proton versions (Experimental, Hotfix, 9.0-4, 10.0-4)
I don't want to invalidate your situation but I'm pretty sure I played without problems for the last months (and yesterday) using first experimental and switched recently to the latest GE proton (since it supports PROTON_ENABLE_WAYLAND=1).
Maybe some more system details could be helpful for someone who knows more about this than me (I'm on 7.2 manjaro KDE plasma with an RTX 3060ti).
Read and do this https://support.deadbydaylight.com/hc/en-us/articles/360041141652-EAC-Error-Code-4
Obviously you can not do the sfc command that is for Windows.
Note that:
We are aware that this particular code can be related to faulty or failing hardware - specifically your RAM modules. We strongly recommend running tests on your internal hardware to ensure it is functioning correctly.
Delete the Proton prefix too at ~/.local/share/Steam/steamapps/compatdata/381210/ by default, and select Proton 11 in Steam so it uses latest Proton.
Start the game then after all that.
Proton versions
proton experimentalx11 2025-11proton 8.0-5x3 2025-06ge-proton10-3x1 2025-06ge-proton7-55x1 2025-06proton 9.0-4x1 2025-06proton 9.0-3x2 2024-12ge-proton9-18x1 2024-12ge-proton9-19x1 2024-12ge-proton9-20x1 2024-12proton 7.0-6x1 2024-12proton 9.0x3 2024-09proton 8.0x1 2024-08ge-proton9-5x1 2024-06ge-proton9-7x1 2024-06proton 9.0-1x1 2024-05
Launch options
PROTON_ENABLE_WAYLAND=1`).x1 2026-08PROTON_LOG=1x7 2025-10RADV_FORCE_FAMILY=radeonx1 2025-06RADV_PERFTEST=acox1 2025-06DXVK_ASYNC=1x1 2025-06MESA_GL_VERSION_OVERRIDE=4.5x1 2025-06PROTON_NO_ESYNC=1x1 2025-06PROTON_NO_FSYNC=1x1 2025-06PROTON_USE_WINED3D=1x1 2025-06RADV_DEBUG=llvmx1 2025-06RADV_DEBUG=nodccx1 2025-06WINE_CPU_TOPOLOGY=32x2 2024-12PROTON_DISABLE_NVAPI=1x1 2024-09
Launch lines
RADV_FORCE_FAMILY=radeon RADV_PERFTEST=aco VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_icd64.json %command%x1 2025-06AMD_VULKAN_ICD=RADV %command%x1 2025-06WINE_CPU_TOPOLOGY=32 %command%x2 2024-12PROTON_DISABLE_NVAPI=1 %command%x1 2024-09
Upstream links
- ValveSoftware/Proton/issues/9092x1 2025-10
- ValveSoftware/Proton/issues/8788x1 2025-06
- ValveSoftware/steam-for-linux/issues/11741x1 2025-02
- ValveSoftware/steam-for-linux/issues/11527x1 2024-11
- ValveSoftware/Proton/issues/8231x1 2024-11
- HansKristian-Work/vkd3d-proton/issues/1734x1 2024-06
- ValveSoftware/Proton/issues/7756x1 2024-05
- ValveSoftware/Proton/issues/7028x1 2023-08
- ValveSoftware/Proton/issues/3095x1 2019-09
- show_bug.cgi?id=44235x2 2018-09
DLLs
actxprxy.dllx1 2020-01advapi32.dllx1 2020-01api-ms-win-appmodel-runtime-l1-1-1.dllx1 2020-01api-ms-win-core-fibers-l1-1-1.dllx1 2020-01api-ms-win-core-localization-l1-2-1.dllx1 2020-01api-ms-win-core-synch-l1-2-0.dllx1 2020-01api-ms-win-core-sysinfo-l1-2-1.dllx1 2020-01api-ms-win-crt-convert-l1-1-0.dllx1 2020-01api-ms-win-crt-environment-l1-1-0.dllx1 2020-01api-ms-win-crt-filesystem-l1-1-0.dllx1 2020-01api-ms-win-crt-heap-l1-1-0.dllx1 2020-01api-ms-win-crt-locale-l1-1-0.dllx1 2020-01api-ms-win-crt-math-l1-1-0.dllx1 2020-01api-ms-win-crt-multibyte-l1-1-0.dllx1 2020-01api-ms-win-crt-runtime-l1-1-0.dllx1 2020-01
Error codes
0x877221c1x1 2020-01
Game starts, Controller works, But it gives me an error
I run Arch Linux with Nvidia 396.54