CQC noob question. Matches starting with half full lobbies.

Hi
last night i was waiting around and there were 5 people waiting, for maybe 10 mins.

1 person kept dropping out and coming back so i presume this was the only available game in the vicinity.

I was about to log out and call it a day and suddently the countdown started, and we had a game, one which was not full but that was ok.... by the next game it was full and all was good.

however can anyone tell me what it is which caused the game to just start up even tho it was not full (which was WAY better than sitting waiting)

thanks
 
A DM match needs 4 ppl to start. If you start to queue for DM, you wont see anyone else queuing before 4 ppl are queuing at the same time. Sometimes the lobby will get broken, and will be waiting for players eventhough you have more than 4 players in the lobby. I think the only way to fix the broken lobby is for everyone to leave that broken lobby. This is pretty hard since you can't communicate with the players that are not on discord.

Don't know if this answered your question.
 
I think what happened to you is one of the many reason ppl give up on CQC. Players end up in a broken lobby, that will never start the game. It is unfortunate, because CQC is awesome!
 
ahh i see,
this is a disaster of a bug then and means i have been wating for ages and there was not even a chance of getting in a game, if the matchmaking has failed.

like you say, with no way to communitcate and the game continually sucking people into the same group.......

no wonder i struggled.
I take it this is a known bug that FD are aware of?

thanks
 
Last edited:
It happened during their livestream, and one of the developers said they were aware of it. But they have not fixed it =(

i dont understand... surely IF they are aware of the issue then they should just add a fall back that "if a game has not started within 5 mins of the lobby being created, then all players are auto logged out of that lobby and then reconnect again."

this would not fix the issue but would help as a band aid?.
 
It happened during their livestream, and one of the developers said they were aware of it. But they have not fixed it =(
They said they fixed it. (I think 2.2 but I'm not sure)

I suspect there was more than one bug with similar symptoms - certainly I've seen it happen less often recently than it used to, even though it still happens.
 
They said they fixed it. (I think 2.2 but I'm not sure)

I suspect there was more than one bug with similar symptoms - certainly I've seen it happen less often recently than it used to, even though it still happens.

I think you are correct. Perhaps it is time for a new bug report? :eek:
 
Back
Top Bottom