Errata for BF3 PC Server R5

[MikaelKalms]

Here is a short list of the most critical bugs in Server R5, which are currently not covered in the manual:

* The game server is not able to run any gamemodes in up-to-64 players mode. Here is the current number of max players:
Conquest - 32 players
Conquest64 - 64 players
Rush - 32 players
Squad Rush - 8 players
Squad Deathmatch - 16 players
Team Deathmatch - 24 players
This will be changed in future server releases.


* There have been a lot of questions regarding join queues and reserved slots. The join queue, and reserved slots with them, are currently disabled while we are weeding out other problems with game servers.
Both will be enabled in the future.

* There are problems with the game server kicking players willfully. The message "You were kicked by an administrator" is a catch-all phrase - it means that the game server disconnected you, for whatever reason (idle timeout, PB kick, real admin kick, ...). We are working to improve in each of the areas, and to get more descriptive error messaging in place.

Now there are many smaller problems present as well. The above is the list of the most frequently encountered ones.

[sHuRuLuNi]

Originally Posted by MikaelKalms

Here is a short list of the most critical bugs in Server R5, which are currently not covered in the manual:

* The game server is not able to run any gamemodes in up-to-64 players mode. Here is the current number of max players:
Conquest - 32 players
Conquest64 - 64 players
Rush - 32 players
Squad Rush - 8 players
Squad Deathmatch - 16 players
Team Deathmatch - 24 players
This will be changed in future server releases.


* There have been a lot of questions regarding join queues and reserved slots. The join queue, and reserved slots with them, are currently disabled while we are weeding out other problems with game servers.
Both will be enabled in the future.

* There are problems with the game server kicking players willfully. The message "You were kicked by an administrator" is a catch-all phrase - it means that the game server disconnected you, for whatever reason (idle timeout, PB kick, real admin kick, ...). We are working to improve in each of the areas, and to get more descriptive error messaging in place.

Now there are many smaller problems present as well. The above is the list of the most frequently encountered ones.

Hi Mikael,

Just rented a server - and wanted to put all CQ maps in the list AND Damavand Peak RUSH (because of the basejump) - but since my server is 64 slots - if it is full and the map changes to to DP - will 32 players simply get kicked?
How can I make DP in Rush to also have 64 slots - I don't want the server to randomly kick 32 players ---


-----------
Play on SlaughterField now: http://battlelog.battlefield.com/bf3...es-of-Albania/

[arpski]

Thanks for info Mikael .

[RambJo3]

What happens if a server changes to a map I haven't bought?

[browha]

Originally Posted by sHuRuLuNi

Hi Mikael,

Just rented a server - and wanted to put all CQ maps in the list AND Damavand Peak RUSH (because of the basejump) - but since my server is 64 slots - if it is full and the map changes to to DP - will 32 players simply get kicked?
How can I make DP in Rush to also have 64 slots - I don't want the server to randomly kick 32 players ---


-----------
Play on SlaughterField now: Battlelog / Sign in

Er, all maps in BF3 are available in all game modes.

[browha]

Originally Posted by RambJo3

What happens if a server changes to a map I haven't bought?

This is currently not an issue with BF3

[browha]

Nice work Mikael. I hope to have all the crashing issues sorted soon - our servers have been much more stable since R5.

by the way, the poster is sweet. Ty.

[sHuRuLuNi]

Originally Posted by browha

Er, all maps in BF3 are available in all game modes.

I don't think you understood me.

I have a 64 slot server. Suppose the server is full with 64 players, playin on Caspian Border - then the next map comes, which is Damavand Peak in RUSH MODE (with only 32 players!) - now what happens? Will half of the players get kicked?

[browha]

Originally Posted by sHuRuLuNi

I don't think you understood me.

I have a 64 slot server. Suppose the server is full with 64 players, playin on Caspian Border - then the next map comes, which is Damavand Peak in RUSH MODE (with only 32 players!) - now what happens? Will half of the players get kicked?

Ah, i misunderstood, my apologies.

Yes, that is correct currently. When the next patch is out (from what I understand, few days time) this should be fixed, according to Mikael's post above.

[RambJo3]

Originally Posted by browha

This is currently not an issue with BF3

I know it's not now, but I'm thinking in the future. Whether people are charged for maps deeply influences my purchase of this game.

And buy that I mean:

free maps - I will buy
even one paid map - lol no.

[browha]

Originally Posted by RambJo3

I know it's not now, but I'm thinking in the future. Whether people are charged for maps deeply influences my purchase of this game.

And buy that I mean:

free maps - I will buy
even one paid map - lol no.

The back to karkand will be a map pack released - at cost if you dont preorder it for free - in a month or two months time. That, though unconfirmed, I believe is likely to run on an entirely seperate map rotation to the current set of BF3 maps.

[xyzeratul]

the R5 server make things a bit more stable, but still like a beta verison.

I say that cuz disconnect from server is less in R5, but still not acceptable, I even seen servers just drop mass of players during map changing, going lag crazy or even offline for no reason(servers even not full)

I hope DICE roll out the next game update quick, before some1 send real bullets to your company....

[tutoss]

What?? 2 days from release and 5 server patches already?? BC2 style

[browha]

Originally Posted by tutoss

What?? 2 days from release and 5 server patches already?? BC2 style

Learn2facts - release version was R3, R4 was never mandatory and very few if any GSPs implemented it.

[xyzeratul]

Originally Posted by browha

Learn2facts - release version was R3, R4 was never mandatory and very few if any GSPs implemented it.

yea, I remember BC2's 1st server version was R4 or something, but till R7, the game final became "playable" for most of ppl.

guess we have a long way to go hum?

[browha]

Originally Posted by xyzeratul

yea, I remember BC2's 1st server version was R4 or something, but till R7, the game final became "playable" for most of ppl.

guess we have a long way to go hum?

I personally expect the next patch to fix most if not all of the most prolific crashing issues. The mean server lifetime, hopefully, after that patch will be on the order of 5-7 days.

[Sethonan]

Originally Posted by xyzeratul

yea, I remember BC2's 1st server version was R4 or something, but till R7, the game final became "playable" for most of ppl.

guess we have a long way to go hum?

I have not seen rubber banding so far; this launch is as many light years ahead from BC2 as BC2 was from BF2.

[fausto412]

Originally Posted by MikaelKalms

Here is a short list of the most critical bugs in Server R5, which are currently not covered in the manual:

* The game server is not able to run any gamemodes in up-to-64 players mode. Here is the current number of max players:
Conquest - 32 players
Conquest64 - 64 players
Rush - 32 players
Squad Rush - 8 players
Squad Deathmatch - 16 players
Team Deathmatch - 24 players
This will be changed in future server releases.


* There have been a lot of questions regarding join queues and reserved slots. The join queue, and reserved slots with them, are currently disabled while we are weeding out other problems with game servers.
Both will be enabled in the future.

* There are problems with the game server kicking players willfully. The message "You were kicked by an administrator" is a catch-all phrase - it means that the game server disconnected you, for whatever reason (idle timeout, PB kick, real admin kick, ...). We are working to improve in each of the areas, and to get more descriptive error messaging in place.

Now there are many smaller problems present as well. The above is the list of the most frequently encountered ones.

you are the man!

[fausto412]

Originally Posted by Sethonan

I have not seen rubber banding so far; this launch is as many light years ahead from BC2 as BC2 was from BF2.

i had rubber banding last night.

[carbonic]

I like how you write this here, but don't make sure all players who are "just" on Battlelog knows it as well.

That forum in there is just crazy with people not even knowing if you are aware of their problems..

[tutoss]

Originally Posted by browha

Learn2facts - release version was R3, R4 was never mandatory and very few if any GSPs implemented it.

3-4 patches in 2 days is a lot anyway.

[hezri]

hi please settle the issue that is holding the reserve slot back.. i need the reserve slot to be enabled!! server is full and reserve slot player cant get in

[DMUniBoNGeR]

Can we have the ability to create a squad or at least join an empty one?

It can't be that hard to implement can it? I can live with battlelog, but when I can't get into the same squad as my clan mates on my own server then this isn't acceptable. Please guys make it happen.

Cheers

[f0CUS]

Originally Posted by tutoss

3-4 patches in 2 days is a lot anyway.

Release patch: R3
Current patch: R5
Difference: 2
"Release date": 24th

That means there were 2 patches in 4 days. Not 3-4 in 2 days.

But are you saying you would rather wait a month or something between patches?

[WileECyte]

Originally Posted by DMUniBoNGeR

Can we have the ability to create a squad or at least join an empty one?

It can't be that hard to implement can it? I can live with battlelog, but when I can't get into the same squad as my clan mates on my own server then this isn't acceptable. Please guys make it happen.

Cheers

You can. It's not overly obvious how to do so. Click 'Cancel Squad Join' and then click on an empty squad and then click the join button. The interface needs a bit of work.