BooosteRx
BooosteRx
About
- Username
- BooosteRx
- Joined
- Visits
- 51
- Last Active
Comments
-
It should not be removed, because most survivors would yell, but be nerfed, like :
- You start with 2 Token : each time you use Dead Hard, you loose a token. When 0 token, Dead Hard is definitly deactivated for the trial.
- Dead Hard can be used 1 time when you are injured, but you have to be totally healed for using it the next time you are injured, and NOT exhausted.
- 10 seconds after using Dead Hard, the survivor cannot interract with any pallet or windows, during 20 seconds.
- 45 seconds after using Dead Hard, you have to be healed totally, otherwise you are in critical state.
These are some suggestions, you could apply one of these, or mix these, or change the values.
So, Dead Hard should be used wisely, as it gave you an advantage on the moment, but has a consideration.
NB : "No Mither" perk could be a problem with these suggestions, so you should take it into account.
-
@burzzum said:
2 weeks we are working on it 👍️👍️👍️👍️ every game support be
I think there are words missing in your phrase, no ??? I don't understand it🤔
-
I played "Friday the 13th : the game" right now, wich is a game using EasyAntiCheat too, and I had no problem at all.
And for more information, I notice that when I launch this game, the EasyAntiCheat.sys file is "modified" (the date and hour of the last modification of the file is exactly when I launched this game).
But the size of this file now (2327 Ko) is not the same as when it is generated by DBD (3502 Ko).
-
@miketheratguy : do you have BSOD now each time you launch DBD, or did it happened just one time and now the game runs fine ?
-
If it can help, I made a screenshot of the Bluescreenviewer software informations.
BSOD first appeared at 01:05:25 01/09/2021 , and created a dump file. What is weird is that the following BSODs did not generate a dump file, but the BSOD reasons displayed on the screen are the same each time.
By the way, I have tried to desinstall and install DBD, but nothing has change ...
Capture.jpg -
Hi, I have the same problem since yesterday evening. DBD was always running fine on my PC, since I installed it on my computer in 2016.
Even if the splash screen of EasyAntiCheat said my PC was lacking SHA-2 code signing support, I just had to clic OK, DBD worked then, and this for months and months. My line of conduct is : as long as it works, do not change anything !
So, after the BSOD, I installed the SHA-2 code with the KB4474419 update. But nothing changed, I still have BSOD each time I launch the game, after nearly 45 sec. I can sometimes have the time to access to the ingame menu, but not further, BSOD comes.
BUT it happens only when the game is on the foreground. I tried to watch the windows task manager and MSI Afterburner to see if there were any clue about this, and all the time DBD was running in the background, the BSOD doesn't appears !! This for many minutes. As I put DBD on the foreground, 3 secondes later => BSOD !!
I didn't installed any new driver, or hardware, nothing at all, since the last time DBD worked, and I play DBD each day.
The software "Bluescreenviewer" said it was "EasyAntiCheat.sys" wich would be the cause of the problem.
So I tried differents things :
- repairing EasyAntiCheat via the integrated tool in EasyAntiCheat_Setup.exe, located in ...\steamapps\common\Dead by Daylight\EasyAntiCheat
- giving administrator rights to EasyAntiCheat.exe, EasyAntiCheat.sys, EasyAntiCheat_Setup.exe
- deleting EasyAntiCheat.sys (it is recreated the next time the game is launched)
- deleting the folder "EasyAntiCheat" in C:\Program Files (x86), and then choose "install" with EasyAntiCheat_Setup.exe => new folder created, just with EasyAntiCheat.exe inside, not EasyAntiCheat.sys
- deleting (with backup) the "DeadByDaylight" folder in C:\Users\[myname]\AppData\Local => recreated at next launch
- launching the game For Honor that is already installed on my computer, and wich use EasyAntiCheat too => runs fine, no BSOD !
Nothing worked, still BSOD !!
So I guess that maybe EasyAntiCheat has made an update yesterday, and that could be the reason DBD is crashing now, for some people.
Because :
- it worked fine before yesterday
- I changed nothing on my side
- DBD had no patch yesterday
Could you please see if this is a possibility ? I'm really sad that I can't play DBD right now 😥
Thx 😉
ps : sorry for my english, it might be not that good 🤔
Win7 pro 64bit
8GB RAM
i5 760 2.8ghz
GTX 1060 6GB
DeadByDaylight.log -
But if my downloads were corrupted, Steam would have downloaded the 8,8 GB once again, at worst.
So, why 21 GB ???
-
Can a Steam user tell me the size of his patch ?
-
Yes it was up to date, I played a few hours before the patch was out.