24 replies to this topic

[Kiyobi]

Whenever a round ends, I get kicked back to the garage screen. When I try to join another match, nothing happens and I just go back to my garage.

I suspect that this is because I'm still technically connected to my previous game_ If I leave the game on my own at the results screen when the round is over, I'm able to join another game. I also think this is the case because in one instance, I was hearing someone's mic while I was in the garage.

Kinda sucks, since I had a good round with a communicating mate in a TDM, but them's the breaks.

[Sotanaht]

Same thing is happening to me, and apparently a lot of people.  After being kicked back to the garage, I was still able to communicate on voice chat with the people from my previous game, who confirmed having the same issue.

[Blastcaps]

getting same though when going back to match type selection it's then I get either "connection refused" "player is on a server already" seems to have happened after I got a rocketeer as well as the default rookie assualt.

[CommandoMan9000]

try turning the game client off, than reboot it

temporary fix

[Tzukasa]

Happens to me too I have to close the game completely and log back in.. Sometimes that doesn't even fix it.. Please meteor resolve this asap! Its the number one issue with the game atvm. That and xp not applying.

[killf4ce]

yep this was also happening in the closed beta so they are aware of it....

[Fantus_Longhorn]

I'm getting the same. Closing the game and launcher seems to be the most reliable way to get it working again.

[Jonathan_Strange]

I think I have the same thing here. Match ends, it gets ready to load the next match, says getting the server ready then I'm bumped to the garage. Sometimes can get into a new match, other times I have to restart the client. The getting bumped out of the que happens each time, the need to restart the client seems random so far...

[aigon666]

Same here, but only get that error one time.

[Kitohru]

Yep, this seems to be a recurring issue, and hearing people from the match just played, confirms that we are still connected to the server after returning(more accurately bumped) to the garage screen.

[Nukerock]

Same problem

[Unholy_Champion]

Happened to me too.

[SaberTruth]

I have even tried restarting my PC, still keeps saying that I can not connect to host every time I try to join a match.

[DM30]

I can confirm the same thing happening to me, although no one in that match was using heasets so I can't confirm on still being able to talk to other players. Got bumped back to the Garage, and then all attempts to join other matches resulted in "connection refused: Player is already on another server."

[Deadmaull]

still happening to me

[killf4ce]

what cards are people using_ i only ask as i recently played on my laptop which has an old nvidia card and x86 windows w7 without the problem at all - back to my DT which has an amd card and is x64 w7 and the problem persists (with or without radeon pro/sweetfx/msi afterburner running)

just wondering if it might be an x86/64 or amd issue_

am tempted to do a windows reinstall just  to see if its ok or not on a fresh install...

[The_Silencer]

Today this has happened to me too. Kicked off to the garage whilst the server was preparing a new match and keeping an eternal sync. Had to manually crash the game client.

[The_Silencer]

Now it's happening to me 2 of 3 games. Always the same: after a match and whilst the server is preparing the next one.. Hope this helps.

[AC3OF5P4D3S]

Wow this has been going on for awhile now and still no fix. I have to exit the client after every match. I haven't been able to play back to back matches one time yet. Nothing scares away new players more then a broken game that has to be reset after each match.

[SS396]

@AC3OF5P4D3S

Have you modified your ini files_  I had modified mine and H0bo posted in my other thread (general area) that he had the issue too when he had modified his also.  I have since reverted back to factory ini's and I have not experienced the issue near as often.

Its a bug, these things take time to find let alone figure out how to fix it without impacting others.