Forum Replies Created
-
Posts
-
That’s worth fuck all…did you forget to tone the hacks down or were you on a server with a couple of suckers for your punishment?
How many medals was that? I got 41k with three medals a couple of nights ago, but was also a late arrival in game.
Fucking phone….
As a final point I suggest an alternative way to manage this. Firstly i’d opt for hardcore over customisation atm becauee of how the browser works, and you know how I detest hardcore but every cloud has a silver lining. I think we would find ourselves frustrated by a lot of hardcore settings, but loving others. Through the hardcore experiment we could identify the settings we like and find the airy fairy happy place that most of us like, assuming it works in terms of server maintaince.
Another way to do this is to nominate a night for a customisation experiment and then vote on the single setting we’d most like changed, then see how this affects our numbers.
Sorry or double post, on my phone, but just want to add that i’m not opposed to servr customisation but that custom settings have so far been unsuccessful for us in maintaining server population, and that needs testing. There are also a lot of custom settings i’d prioritise over ff, eg kill cam and vehicle/player heal. This whole thead smacks of inconsidered impulse.
Hardcore and ff only are two completely seperate arguments and shoukdn’t be muddled together in an impulsive poll.
@=xdc=maniac wrote:
If not Hardcore, what about in the future just putting on FF? Or how about another thread with one of them votey thingys? I personally don’t mind if we have hardcore or not, but I prefer FF to be on. Either way its all good!
It might be ok having FF on but it delists us from the quick join thing and may make it harder to maintain a player count on the server. We shouldn’t vote on something until we’ve tested it’s affects first, and we all know what we’re voting for.
Anyway, weren’t we talking about a monday night hardcore session?
Hang on there needs to be debate on this because, by itself, this will delist us from any quick join priority EA have, and we haven’t tested this, nor have we tested how it works alongside other non hardcore settings.
I’m in the unusual position atm at being able to compare ISP’s from the same computer, and while a ping test with virgin (cable) is coming out with an A score atm and actually with an excellent ping of 26ms, there is jitter on the connection compared with nothing on the new connection (ADSL).
I wonder if it’s this Jitter that perhaps the BF3 net code has issues with, leading to rubber banding, and I’ll put it to the test over the next few days.
Only great if you like it messy, and I’d vote against a friday or weekend night, as that’s when I have most game time and I honestly detest hardcore. I can live with finding a random server or occasional games on a Monday but I suggest trying it first then having a month long discussion about setting it up as a regular thing or setting the server on hardcore more often.
Very easy to setup CC btw, just click hardcore on the admin program and restart server (may not even need a restart).
Yea I always spot everything I can, in particular aircraft and tanks. Incidently the spotting icon disappears if obscured by terrain or effects like smoke now.
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.
That’s horrendous! Mine wasn’t even that bad last year prior to their network upgrade in the area when I couldn’t even play tf2. How the fuck do you play so well in bf3!
For comparison though:
I’m 250 miles further from a server and performing much better with same ISP. Having said that I’ve run that test at ten thirty and my problems are worst between 7 and 10 usually. I also suspect EA’s server code contributes to my rubber banding as well….but still virgin are shit in some areas, or at least they’re happy with average too often, which is useless for gaming.
