hey guys, for the last few days now i've been encountering issues when trying to connect to the server when its full. I queue up and am placed in queue but then when it goes to connect i get constant error messages saying i cannot connect to the server. anyone else having this problem? and if so is it something wrong on my end or the servers?
-
[CN]KentWingslide -
I get it occasionally. I just click to rejoin and usually get in the next try. A couple of times it has taken two or three attempts.
Apache
Where do you put the Bayonet?
Chesty Puller (upon seeing a flamethrower for the first time)
I am all in favor of keeping dangerous weapons out of the hands of fools. Lets start with typewriters.
Frank Lloyd Wright -
Happens to me as well. I believe it is more of an issue with battlelog and the fact that our server is usually full.Comment
-
I seem to get this issue only when trying to join certain servers and it takes 3-5 attempts to get into that server.
Haven't had it trying to join your server yet.Comment
-
That happened to me a few patches back, and got resolved when the next patch rolled out. Looks I can't join CLR till the next patch rolls out.
Comment
-
It seems to work for me when the map is about to change. I plug away just like it was a full server before the que and I get in.Originally posted by TheTurboSloth View PostThat happened to me a few patches back, and got resolved when the next patch rolled out. Looks I can't join CLR till the next patch rolls out.Comment
-
This was posted on Reddit and the Battlelog forums a few weeks ago regarding "corrupted server slots."
http://www.reddit.com/r/battlefield_...d_by_an_admin/
Looks like the BF4 engine has corrupted slot(s) that happen after the servers uptime has surpassed 86,400 seconds (which is one standard day, (60 * 60) * 24)
What happens is, say, on a server with 64 slots, and over a day of uptime, one of the 'free slots' to connect becomes corrupted (it's not actually free per say). When a player actually LEAVES the server, then a legitimate slot opens and you're able to play. If someone tries to connect after you are in the game, they will get the "Could not join Server" error.
The only fix is to restart the server once a day, I'm afraid.
Comment
-
wow thank you for that oneComment
-
Very interesting and helpful, thank you. They released yet another patch, R20, perhaps it helped that??
For some unknown oddball reason they will not post release notes on what exactly these patches fix!!
Unofficially this is what R19 "fixed"
R19 Server Update
-Introduced an update to our anti-cheat system
-Fix for a server crash that was caused by setting the vars.teamXFactionOverride value to 3
-The vars.teamFactionOverride command, with the <team> and <faction_id> parameters has been introduced, replacing the vars.teamXFactionOverride commands
-Vars.playerManDownTime has been removed as this was not working as designed
I have no idea what R20 "fixed".Comment
-
Still exists sadly. Getting the issue right now.Delivering bacon goodness one round at a time.Comment
-
we gotta just fight through all these crappy updates on both client/server side. EA will get it right hopefully and until then the community has to be above all the bs. i know i find myself getting pissed at these ridiculous errors.Comment
-
This has been going on for quite some time. As a Premium BF4 user, the queue appears broken more often than not. I'll attempt a dozen plus times, no luck. Some servers are affected, whilst others are not since they are rarely as full. It's pretty bleak when players can't even queue up to play.Comment
Comment