Open Houtworm opened 6 years ago
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:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.0-devel
6.1.0-11-rt-amd64
8.0
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.
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:
Game crashes when i tried to enter a match. Specifically when the game shows "offerings" added by players.
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.
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
Proton Logs: https://gist.github.com/AnonymerNiklasistanonym/f4d1e0f374f8af3b1e5c4bc7fca5e954
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.
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: 1) Have you tried Proton - Experimental yet? Perhaps this issue is already fixed upstream. 2) 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:
The game freezes while it loads into a new match or while the new match starts.
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:
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.
Game starts, Controller works, But it gives me an error I run Arch Linux with Nvidia 396.54