Why matches cancel from pre-disconnects
It's quite frustrating to wait so long for a lobby, only to have the match load up with an immediate cancellation because one or two others disconnected midway. I've been wondering why that happens so often, and only in recent versions did I began to realise.
Some times, my own game freezes during match load. The logo animation stops completely, and the OS regards the entire game process as unresponsive. The only way out of it is to end the task. The number of times this happens to me alone multiplied across the player base must be unreasonably high?
How often does you own game hangs up completely? I feel the developers need to spend some time evaluating the different activities during this initialisation period that can cause the process to not respond to peripheral and OS inputs.
Comments
-
I rarely if ever have the issue of my game freezing up.
The game going back to the lobby with this scenario has only happened around twice out of around 100 matches for myself.
I understand why this change was made as starting a game with 3 players was complained about for years as you were instantly disadvantaged as depending when it happened the game could start with 5 gens still.
0 -
I know why matches cancel; in fact I'd suggested a number of times for a way for the remaining players to vote if they wish to continue playing the match unbalanced, but looks like the developers took the easier route of just cancelling it outright.
What I'm trying to pinpoint is whether players often end up in the situation of their game hanging during match load, will may then explain why many matches start up with less players than expected.
0 -
The high majority of the time, these people aren't "DC'ing" and causing this. Something happens with the game and it drops a player. I can't say why the game drops people which causes the game to result in a "match cancelled", but apparently Behaviour couldn't figure it out either or it was too complex to fix. If you were here in the old days, then you remember all the 2-3 man load outs. It almost always sucked when that happened, especially if you care about rank. If they killer didn't try to farm, you would all be dead soon. It was a total waste of the survivors time. Unless you cared about rank, all the survivors just DC'd from it because it was a lost cause unless the killer was super super terrible. Killer and survivors always ended up with depips for something that wasn't their fault.
Survivor queue's use to be 30 seconds or less for me so the "match cancelled" wasn't a big deal, but I still don't want to return to 2-3 man load outs!
0 -
I closed the game a few times in the past before the match, because I'd load in a game which gets cancelled because someone dc. So I just start looking for a new game and when loading screen comes up I realize I forgot addons and offering
0 -
It happens. Unfortunate but fair.
If you're a survivor and someone is dead by the time you have one gen done, you're screwed. 3 survivors and 4 gens is doomed.
0 -
I know that; I've been playing since 2017, and as mentioned above had suggested many times for alternative options for players when less than four survivors commence the match, since it drastically swings the balance in favour of the killer.
What I'm trying to determine is the technical reason behind the disconnects; if a lot of people experience the game hanging (process not responding) during the match load, thus having to kill the process and re-launch the game all over. If the software instability is not just isolated to my case alone (and I actually play on two separate computers at home with different hardware and OS load-outs), then it lends more suggestion to why this happens quite often.
0 -
Still happens wait too often for me; game hangs while loading into match. If everybody's copy of DBD is as unstable, it'll explain why there're so many prolonged match loadings due to players get cut off.
0
