psikobare
psikobare
About
- Username
- psikobare
- Joined
- Visits
- 11
- Last Active
Comments
-
@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.exeUnloading 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 could perfectly be server-side. When you connect to a server, you announce yourself along many metadata, one of them is probably the client you use. Someone at behaviour probably added a check to prevent people from joining because they feel it isn't ready yet. Just wait patiently for an anouncement.