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!
'Player Disconnected From The Match While Loading' during the middle of a game
Match Cancelled: A player disconnected from the match while loading (Error code: 500) during the middle of a game that was being played.
All players, including myself (as survivor) had loaded into the match other than one survivor, who had the DC symbol above their name in the UI at the bottom-left from the moment the match started. All gens had spawned as they normally would, and the match played on for around 2-3 minutes as normal with 3 survivors and 1 killer.
After these 2-3 minutes, the game suddenly ended and we were all kicked to the post-match screen, despite the fact the match had been played out otherwise normally. I can confirm this, since all players were active in the chat at the end (other than the survivor that had presumably disconnected). None of us were rewarded bloodpoints etc.
I'm presuming this is a bug, since based on my understanding, the error should only occur immediately after the loading screen rather than during the middle of a match, but if I'm wrong, then ignore everything I've written xD.
My Platform: Steam (Windows 10)
(All other players were Steam players too)
Map: The Underground Complex
Killer: Pyramid Head
Occurred on the current version of the game, never experienced the issue before.
Post-match screen after we were kicked.
Comments
-
Update: I'm aware of the pinned thread about what seems to be a similar issue. I wasn't sure if this was the same issue or not, but the descriptions of what occurred in the issue described by the pinned thread seemed different to mine, so I posted a separate thread. Apologies if I have done this wrong.
0