Avatar

Rokolell

Rokolell

About

Username
Rokolell
Joined
Visits
83
Last Active

Comments

  • @Mach2 said:

    https://forums.bhvr.com/dead-by-daylight/discussion/comment/3314130#Comment_3314130

    I think there’s a chance that Heroic is able to trick the game into thinking you’re on a true PC, whereas Steam knows you’re on a Steam Deck. Of course nothing certain and I very well could be grasping at straws, but in my mind it’s what makes sense..

    Heroic isn't faking anything.

    The biggest difference between the Epic and Steam version is the game executable and the Steam client, so it's either a bug with Steam itself or deliberate blocking of the steam version on the servers.

  • @aragami said:

    https://forums.bhvr.com/dead-by-daylight/discussion/comment/3313916#Comment_3313916

    https://forums.bhvr.com/dead-by-daylight/discussion/comment/3313763#Comment_3313763

    You guys are all right, but why does the epic version works and the Steam one doesn't? Cannot be just a server side block otherwise it wouldn't work for Epic too. I may be wrong since I'm far from being an expert tho

    The answer could be some differences between these two, maybe it's just a library mismatch or a difference in how the executable from Steam works compared to that of Epic.

    I don't know if this have any relevance or is it just an expected result since I don't have the knowledge to analyze a dll/so compiled library but I found this, maybe someone could investigate even more:

    (I used the same command for every file you see here)

    user@pc:~$ strings '.steam/debian-installation/steamapps/common/Dead by Daylight/DeadByDaylight.exe' | grep Easy
    

    This give the following results:

    - DeadByDaylight.exe

    Unloading the EasyAntiCheat library.
    Outdated EasyAntiCheat library, does not match with launcher's version.
    EasyAntiCheat Oy1
    EasyAntiCheat Oy0
    

    - DeadByDaylight-Win64-Shipping.exe :

    ../../../EasyAntiCheat/eac_server64.dll
    ../../../EasyAntiCheat/easyanticheat_x64.dll
    

    - EasyAntiCheat_x64.dll :

    Easy Anti-Cheat successfully loaded in-game
    User-Agent: EasyAntiCheat-Client/1.0
    EasyAntiCheat\Cache\
    EasyAntiCheat successfully initialized
    Error validating EasyAntiCheat code signing certificate.
    EasyAntiCheatPreRelease
    EasyAntiCheat_x64.pdb
    EasyAntiCheat_x64.dll
    EasyAntiCheat Oy1
    EasyAntiCheat Oy0
    

    - easyanticheat_x64.so :

    EasyAntiCheat\Cache\
    User-Agent: EasyAntiCheat-Client/1.0
    EasyAntiCheat successfully initialized
    Easy Anti-Cheat/1.0.0
    EasyAntiCheat Client
    

    If someone with the Epic version could try the same to see if there are any differences would be cool.

    It would be more useful to get logs in the Epic version from ram to compare them to Steam, but it's really annoying to do, and I also don't have the epic version, so I can't do it anyway.

    Plus, the content isn't really helpful either. So in the end, we can just wait...

  • Yeah, it's just confusing how the EpicGames version works, but Steam doesn't.

  • @Moshquito said:

    https://forums.bhvr.com/dead-by-daylight/discussion/comment/3312531#Comment_3312531

    Hi, i own both versions. If u tell me what to do, i can have a look at the build

    If you're able to play via Epic, the file content of drive_c/users/<USER>/AppData/Roaming/EasyAntiCheat/83/loader.logwould be interesting.

  • I wasted some time dumping the DbD logs from RAM. Doesn't look really promising though: EAC sends an auth ticket, then the game goes in the disconnected state and afterward receives some EAC commands.

    So, maybe a race condition in EAC authorization?

  • Can confirm it works. Good job everyone on the Proton team (and bhvr as well 😉).

  • The steam version fails here: https://github.com/EpicGames/UnrealEngine/blob/cdaec5b33ea5d332e51eee4e4866495c90442122/Engine/Source/Runtime/Engine/Private/LevelTick.cpp#L438

    I suspect auth fails on the server side and it force closes the connection.

    Not really sure how to debug it further without decrypted game logs, though. If a dev sees this, it's probably the best to debug what's wrong on Steam's or Proton's end and report it, so other games won't suffer from the same issue, and no workarounds are needed.

    Or you decrypt my gamelogs, and I'll retry. :3

  • Well there were also a few Problems:

    1. In the beginning, it took the devs a while to figure out how you enable it for the Deck, and they added the needed .so files.
    2. Then EAC support for DbD was kinda broken in Proton and no one was aware of it until some community members mentioned it.
    3. Now the EAC part on the Linux side is broken, and it must be investigated... The module is there (https://download.eac-cdn.com/api/v1/games/83/client/linux64/download/) , so yeah... need to be patient.

    They are working on it. 😉

  • @yosoynacho said:

    https://forum.deadbydaylight.com/en/discussion/comment/3229194#Comment_3229194

    There's no bug, the game fails to get EAC proton binaries meaning that devs haven't turned on proton support.

    Not true, the binaries are downloaded, else the loader would hang...

    @meffle said:

    https://forum.deadbydaylight.com/en/discussion/comment/3230174#Comment_3230174

    So what you're saying is 'switch to using EOS, please behavior'. If so, other developers have done the same thing much quicker in exactly the same time period.

    Devs, not only DbD, shouldn't be forced to do this, just to run a game on Deck.

  • @davidlicurici said:

    Yea , but Apex Legend and Fall Guys , runs without problems

    Fallguys doesn't even use legacy EAC but uses EOS EAC and Apex uses a different kind of apiset....

  • @meffle said:

    https://forum.deadbydaylight.com/en/discussion/comment/3229304#Comment_3229304

    That doesn't mean that there's an eac bug. Other developers haven't struggled this badly to add support.

    it is. Halo MCC has the exact same issue.

  • @nikodemo said:

    https://forum.deadbydaylight.com/en/discussion/comment/3229194#Comment_3229194

    What's the bug? I'm happy to go bother someone else. XD

    The Linux module of EAC crashes, when DbD loads EAC. You can see that when the game is loading, it will hard hang / crash.

  • Guys, you need to calm down. As I said before, the DbD devs actually enabled the game for the Deck it just doesn't work because of a bug in Easyanticheat, which needs to be fixed by Epic. As soon as that's fixed, you can play the game, but you need to still be a bit patient.

  • Someone from LGD Discord tested the Epic version and it has the same issue.

  • Some good news for the devs. The EAC loader issue seems fixed now, but support for Proton doesn't seem to be enabled (no 100% sure though) on the EAC side, yet.This causes the game to (obviously) hard hang on load.

    [Info] Desktop screen settings detected. DPI: 96 DPI Multiplier: 1.000000 BPP: 32.
    [Info] Localization loaded for: 'en-US'.
    [Info] Settings file full path: 'Z:\run\media\bernhard\Games\SteamLibrary\steamapps\common\Dead by Daylight\EasyAntiCheat\Launcher\Settings.json'.
    [Info] Start. ExecutablePath: 'Z:\run\media\bernhard\Games\SteamLibrary\steamapps\common\Dead by Daylight\DeadByDaylight/Binaries/Win64/DeadByDaylight-Win64-Shipping.exe' LaunchParameters: '' WorkingDirectory: ''.
    [Info] Finished window initialization.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    [Info] [LauncherProgress] 0%.
    ...
    [Info] [LauncherFinished] EACAsyncResult: 0 Message: 'Easy Anti-Cheat successfully loaded in-game'.
    [Info] Unloading the EasyAntiCheat library.
    [Info] Destroying windows.
    [Info] Exit.
    

    Update: The issue is still on the Proton side 😵:

    048c:fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
    09a8:fixme:avrt:AvRevertMmThreadCharacteristics (0000000012345678): stub
    *** stack smashing detected ***: terminated
    


  • @rvzrvzrvz said:

    If they stop buffing camping/tunneling every patch it could be fun, the best strat is still tunneling someone out early and facecamp is even stronger against solo groups now, you're forced to play killer and make your own imaginary rules if you want to avoid these boring strats

    Yup, tunneling is never addressed by any update directly, because it's an issue with the core game and not a single killer. Bringing in perks like BBQ n Chilly only made tunneling less lucrative, but didn't erase it, really.

  • @SekiSeki said:

    I didn't see a single solution reading through all of that. I think it is fine to bring up criticism but at least give something to work with. All I got was stop making money and remove content from the game. Yes, some issues you bring up are valid but share some ideas for improving the game. Just from reading your post, you seem miserable with the game. If it has held your attention this long, it must be doing something right.

    I think variety is good for the game. I think that what they are doing with the patches is a great direction. They've promised more updates like this in the future, and I am eager to see the direction they take.

    I brought up some ideas in my post, and it's also not my job to give nurse, for example, a completely new base ability. And as a software engineer, I'm not a creative person anyway. I also don't think Bhvr shouldn't stop making money, but it's a bit sad to see the whole game going downhill over the years, when at the same time the owning company puts barely differing items in an in game store and even wants real money for that. You really see where the priorities are at. The game has been holding my attention for so long, because its gameplay felt unique when I first played it, and still does to this day. Also, the alternatives out there aren't so great after all...

    And yeah, variety is great, but they are shoveling their own grave with the game, as it's becoming more and more of a optimization hell and more players getting upset and leaving the game because of that.

  • Also, the regular reminder for the devs, that you can ask (yeah that's an existing concept) Valve for help, if you don't manage to get it to work. IMAGINE!

    So, if you suffer from this fixme:eacbridge:CreateClientAuth Failed to create EAC interface ClientAuthInterfaceV001.

    it's maybe time isn't it? ;)

  • Guys don't overwhelm the DbD devs. This is not an easy thing to implement. /s 😉

  • Having this would be very cool.

  • Change at least button ingame, then go to %LocalAppData%\DeadByDaylight\Saved\Config\WindowsNoEditor and edit Input.ini :

    e.g. this binds Struggle to Mousewheel up and down and to the Spacebar
    ActionMappings=(ActionName="Mash_Camper",Key=MouseScrollDown,bShift=False,bCtrl=False,bAlt=False,bCmd=False) ActionMappings=(ActionName="Mash_Camper",Key=MouseScrollUp,bShift=False,bCtrl=False,bAlt=False,bCmd=False) ActionMappings=(ActionName="Mash_Camper",Key=SpaceBar,bShift=False,bCtrl=False,bAlt=False,bCmd=False)

    A list with all buttons can be found here:
    https://wiki.unrealengine.com/List_of_Key/Gamepad_Input_Names

  • With the recent changes to Steamplay and the addition of the Proton compatibility layer will you ever consider making this game run on that? I heard that EAC is working on Wine builds so it shouldn't be so hard to get this running.

    If not, would you alternatively consider to press this and create a second Steam depot using the EAC Linux Version?

    I'd really love to get away from Windows but things like this make it hard to switch without having to leave the game behind, too... :(