When reporting a bug, please follow the template provided, otherwise the report will be declined. The information requested is vital to allow us to correctly reproduce and then fix what you are reporting.
Visit the Kill Switch Master List for more information on these and other current known issues: https://forums.bhvr.com/dead-by-daylight/kb/articles/299-kill-switch-master-list
We encourage you to be as honest as possible in letting us know how you feel about the game. The information and answers provided are anonymous, not shared with any third-party, and will not be used for purposes other than survey analysis.
Access the survey HERE!
Too many performance issues and lag on ps4, specially as killer (how and when they happen)
Example 1
Step 1 : Boot the game
Step 2 : Play as killer in a public match
Step 3 : you activate your power (like pulling up a hatchet or pulling out the tentacle or aim down your sight) or any survivor performs an action/interaction (like finish or touch a gen/ use dead hard/ vault/ open an exit gate/ etcetera)
Step 4 : your game gets frozen for 1 second or more
(THIS ALSO STANDS FOR SURVIVOR GAMEPLAY, SAME ISSUE AND SAME SITUATION)
Example 2
Step 1; you boot the game
Step 2: you join a swf
Step 3: you found a match and check your ping
Step 4: you and usually every other member of the swf notices that has constant 150 ms or more (not a wifi problem)
(THIS HAPPENS ALMOST EVERY MATCH, THERE'S ALMOST NO ONE MATCH THAT HAS AT LEAST ONE OF THE SURVIVORS WITH CONSTANT 150 MS)
ADDITIONAL INFORMATION (performance issue)
- any character performing any action or interaction
- any perks, when you use them usually the game freezes too
- any map (but specially racoon city)
- Frequency of the issue: a lot of times in one singular match
ADDITIONAL INFORMATION (lag problem)
- any character performing any action or interaction
- any perks
- any map
- frequency of the issue: as i said, there is almost no one match that has at least one of the survivors with constant 150 ms or more
DOCUMENTS TO ADD
there is no need to add anything, i think the devs already know about this issue, i just try to give as much information as possible.