- This topic has 18 replies, 6 voices, and was last updated 13 years ago by
.
-
Posts
-
Going to lump these all together in one thread, as there will be a lot of them, but only when I can be arsed reporting.
Tomorrow morning Rackage have to install server patch R8 as it’s now mandatory from DICE, however below was the inital information on it from Gonzo.
R8 was released earlier today, some GSP’s reported increased server crashes after installing it so we held off deploying it to all servers.
DICE have been looking into it and (at this time) can find no evidence to support this.
As it is now reaching peak gaming time we will not be doing a forced rollout to all servers.
I have made the patch available in Control Panel>Game Updates – if you choose to install it and find out your server is crashing please feel free to rollback to R7.
Official changelog:
* Crashfixes* RCON bugfixes; banList.add can now ban on player name
* Fixes for team & squad handling, both during and between rounds
Report from rackage since R8’s deployment is that GSP’s are finding the new patch much more stable than R7, although still not crash free.
Ha.. I wont admit as I like to transport folks to flags and pick up.. loved doing this in Vietnam.. although doenst happen much in BF3 🙁
anyhoos I believe this happens to Airmessy also.. or someone who piped up in TS last night 🙂
Every time in a plane i crash. Seems to be as soon as i damage something it boots me to desktop. Can fly about without damaging anything and all is good.
i will be up for some heli flag capping tonight if your up for it m8……sounds like a safe way to get the job done if you ask me.
2 squads of 4…..chutin in…..clean up…..hop back in……take the next one.
easy (until hit by a stinger -8 kills and that will be the end of that)
Just to clarify, the crash issues referred to by rackage are server side crashes, i.e. Everyone dumped off servr, amd not client side ones which will i’m sure eventually sorted via client side patches. Our server has crashed on occasion but seems more stable since game release.
For those not in the know, the server patch R9, which was released along with the client patch this week, included some changes to the way the quick match system worked and introduced unranked servers. From our point of view the most significant change was the criteria for our listing as a ranked server. Controversally they reduced the idle timer to 300 seconds, but also allowed us to reduce the number of players to start a round to 4, with no apparent penalty in the quick match system. We immediately tried to fix our server to a minimum of 4 players, but it produced some weird and wonderful errors in game, and we didn’t really have time to experiment so we restored the setting to 6.
This morning however I noticed that R10 has been released and, following a request from the community, EA have given us the ability to modify the idle timer again on ranked servers, so ours has been restored to 900 (which may be a little high, but it’ll do for now). I have also taken the opportunity to experiment with how the “minimum players to restart a round” affects ranked status, and have found that setting this to 1 keeps us ranked. Since this looks good, I’ve reduced the number of players required to start a round to 4, and the round should only restart when the population drops to 1. Note that the R10 patch is currently optional, and is subject to testing atm by GSPs and has already been patched once itself. We have the option to roll it back over the next few days, so please report any major issues since it’s installation this morning.
I’ve not actually been on the server much this last week sicne the patches release but I noticed yesterday that the map list is still reverting back to the older setting, and the banlist, which I’ve cleared about 17 times, keeps repopulating itself. Now I’m not sure if this is an issue with the patch, or the admin program, but I’m going to find out over the next few days, however I need to know whether the server is still randomly restarting itself as it was under the R10 patch (the one before this week’s patching). I’m guessing it is, because the last couple of days it’s been on Canals with the server empty, but I’ve not yet seen it happen, so need to ask you guys?
The R12 patch is rolling out now, it is a large patch so may take some time to do all the servers, I will send another message out when patching is complete.
Changelog
* General crashfixes
* Fixed problem where kits would remain on the level for a long time (>10 minutes); this would eventually make the server keel over
* The Back to Karkand maps are included
Notice that there are two variations on the Conquest gamemode (ConquestSmall0, ConquestSmall1). The differences are mainly to do with the flags. You will see a “#2” after the map name for a server that runs the second Conquest variation.
Game servers can mix and match B2K and non-B2K maps. Players who have not purchased B2K will be warned if they attempt to join a server with B2K maps in the rotation. Quickmatch will not send those players to servers with B2K maps in the rotation either. The guiding principle here is: if possible, avoid having people get kicked from servers.
Server admin manual on the internet
Available now: http://static.cdn.ea.com/dice/u/f/bfbc2/tmp/BF3_PC_Server_R12_893642_Docs_ServerAdministrator.zip
There’s an issue that has already been reported to DICE that the ticket bleed on Karkand begins when waiting for the round to start.
@Alzir wrote:
There’s an issue that has already been reported to DICE that the ticket bleed on Karkand begins when waiting for the round to start.
Mugs
- You must be logged in to reply to this topic.