You must be signed in to perform this action.
Bug: Hard Lock Issue in Survivor Lobby During Play While You Wait
226 °C
Bug #5412
Hard Lock Issue in Survivor Lobby During Play While You Wait
| Status: | Open |
| Priority: |
Critical |
| Added by: |
|
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
You end up in an empty Survivor Lobby where noone will join and you can't quit out, you must Shutdown your console/pc or open task manager to force DBD to shut down
|
| Expected Result: |
Usually when both queues pop in Play While You Wait, it will prioritize the Killer queue pop as thats what you originally intended. Though it seems that if both queue pops are close enough together [maybe frame perfect] the game s**** itself and doesn't know which to take first, if thats the case, it shouldn't be, the Killer Pop should always be prioritized if it comes first. maybe an internal buffer time would help as if the game finds a Killer lobby fast enough, it'll just automatically cancel the Survivor search
|
| Severity: |
Blocker
|
| Reproducibility: |
Sometimes
|
| Platform: |
Steam
|
| Additional Notes & Comments: |
Not set
|
Steps to Reproduce
- Select Killer in the menu and select Play While You Wait
- Ready Up for a Play While You Wait Survivor Match
- If you are unlucky enough, both queues will pop at the same time
- If they do, the game will try to put you in both lobbies at the same time, locking you to an empty Survivor lobby where theres no sound and no menu interactions work
- Quit out does not function, no other menu buttons function, Alt+F4 does not close the game, the close button on the desktop does not work
- End Task in Task Manager or Shutdown your system to break the Hard Lock
Explanation
If you select Play While You Wait as Killer and both the Killer and Survivor queues pop at the same time, your game will be Hard Locked in the Survivor Lobby with no sound and you will not be able to interact with ANY menu item
Watchers
Screenshots
None
Video Clips
None
Log Files
None
No comments yet.
Loading comments...
Loading comments...
0 comments loaded
You need to join this project to comment on issues.
Join Project