New client patch soon

[Vreki]

With a bit of luck, we could get a client update today. I haven't seen any patch notes yet, but lets hope some of the more annoying problems will be fixed.

ETA: It is out now, here are the patch notes

This update is about performance and stability again. We are not doing any changes to the game's datafiles.

* Reduced input "lag"
On machines where the CPU would out-run the GPU, sometimes the GPU would queue up several frames' worth of rendering commands.
This could lead to the game having a high framerate, but input still feeling very sluggish.

Now there's a limiter on how many frames the CPU is allowed to be "ahead" of the GPU.
Control this setting via Settings.ini. Default setting: RenderAheadLimit=2

* Performance optimizations with biggest improvements on dual-core machines
* Fixed black "masks"
o The soot on buildings with holes in them had a bugged renderpath. We switched that over to a more well-tested renderpath.
* Improved hit-detection
o We've gone through the hit detection logic, and client+server will now give more consistent results.
* Fix for some "rubberbanding" issues
o C4 should stay attached to vehicles and not rubberband around
* Reduced spikes/dips in framerate
* Various fixes for alt+tab related CTD on Dx9
* More fixes for random CTD on Dx9
* Fix for crash when you're in a vehicle that gets destroyed

There was a race condition in the code;
System 1 thought "oh hey, you're leaving vehicle X"
System 2 thought "the vehicle got destroyed, let's remove it"

If system 2 ran before system 1, chaos would ensue.
This was actually fixed in the retail version since a month, but it was only when we got detailed crash reports from the community that we understood *why* the Beta was crashing.

Likely bugs in this build
I wouldn't be surprised if it (still) has trouble remembering your settings between rounds. It would be nice to have that fixed too, but it's better to get a patch out now, and look at the settings issues afterward.

The EA maintenance is purely backend on the servers that handle accounts, server browser and stats etc for all EA games.
However, we are working on a new client seperate to this maintenance window which is with QA at the minute but they are delayed by this maintenance.
R6 is already out with the hosting providers btw.

We are looking at today but depending on maintenance it might get pushed out. So keep your fingers crossed that the QA process goes well on it

Source: http://forums.electronicarts.co.uk/b...azajaytee.html

[Kylee!]

Re: New client patch soon

Hmmm, I look forward to this.

[vanilla]

Re: New client patch soon

Should be nice. =)

[iQue]

Re: New client patch soon

Sweet. I've taken a break from the beta because the C4 suiciding just gets too annoying, and Stalker:CoP takes all my time. Hopefully this will get me into it again.

[Cicchetti]

Re: New client patch soon

Once the servers are back online QA have to do some checks, and then they can release it. It might not be today though sadly.

[Scinto]

Re: New client patch soon

UPDATE: The maintenance has been restarted due to issues on restarting the service under load. The EA servers will be down for another 45 minutes. In which time we are working on a new server and client to be released for when the servers come back online.

Was posted at 5:50pm so was 75mins at the time.

I have the changelog, it will go out when we are 100% the client is stable to be released.

[jimykx]

Re: New client patch soon

hmmm. Interesting. i would wonder if we could have a new map to the beta. XD haha

[Lordsethonan]

Re: New client patch soon

No new map; servers back up; but client patch tomorrow at the soonest.

[Soldat]

Re: New client patch soon

Thats good news, I hope this means I can take my safety orange vest off now....

[Vreki]

Re: New client patch soon

We just got the results back from QA for the new patch version and unfortunately it isn't good news. Multiple CTD's and performance issues. This of course means we won't be releasing a patch today.

Sorry guys, maybe tomorrow
I'll keep you updated with our plans during tomorrow.

[Scinto]

Re: New client patch soon

Dont see it coming tomorrow either tbh if it hit QA in that state its gonna take some time to fix..

[jimykx]

Re: New client patch soon

Still got no update

[iQue]

Re: New client patch soon

We just got the results back from QA for the new patch version and unfortunately it isn't good news. Multiple CTD's and performance issues. This of course means we won't be releasing a patch today.

Sorry guys, maybe tomorrow
I'll keep you updated with our plans during tomorrow.

[Lordsethonan]

Re: New client patch soon

It looks like it was released again to QA; maybe today during the afternoon (It's 1:30 PM here, so there is still some time).

[Vreki]

Re: New client patch soon

The patch could already be out now!
And the changelog looks good, although there doesn't seem to be any balancing changes like weapon damage or objectives resistance to C4.

New Client (R3) Coming NOW (before 10am GMT) and Changelog
So QA found out a debug setting we used for logging errors was causing the CTD's after DICE left last night. As such the patch is good to be released and is going live within the hour.
Steam users will have to wait until this evening to update as we need Valve to wake up to make it live their end. If you want to run the latest version you can uninstall the Steam version and grab the client from any host here: Battlefield Blog and use the same login details as before.

You can update automatically when loading BFBC2 or you can manually run the updater from your install directory (run as Administrator if you experience update issues or errors)

As promised here is the Changelog for R3 as provided by Kalms.



Quote:
This update is about performance and stability again. We are not doing any changes to the game's datafiles.

* Reduced input "lag"
On machines where the CPU would out-run the GPU, sometimes the GPU would queue up several frames' worth of rendering commands.
This could lead to the game having a high framerate, but input still feeling very sluggish.

Now there's a limiter on how many frames the CPU is allowed to be "ahead" of the GPU.
Control this setting via Settings.ini. Default setting: RenderAheadLimit=2

* Performance optimizations with biggest improvements on dual-core machines
* Fixed black "masks"
o The soot on buildings with holes in them had a bugged renderpath. We switched that over to a more well-tested renderpath.
* Improved hit-detection
o We've gone through the hit detection logic, and client+server will now give more consistent results.
* Fix for some "rubberbanding" issues
o C4 should stay attached to vehicles and not rubberband around
* Reduced spikes/dips in framerate
* Various fixes for alt+tab related CTD on Dx9
* More fixes for random CTD on Dx9
* Fix for crash when you're in a vehicle that gets destroyed

There was a race condition in the code;
System 1 thought "oh hey, you're leaving vehicle X"
System 2 thought "the vehicle got destroyed, let's remove it"

If system 2 ran before system 1, chaos would ensue.
This was actually fixed in the retail version since a month, but it was only when we got detailed crash reports from the community that we understood *why* the Beta was crashing.

Likely bugs in this build
I wouldn't be surprised if it (still) has trouble remembering your settings between rounds. It would be nice to have that fixed too, but it's better to get a patch out now, and look at the settings issues afterward.

-Mikael Kalms
__________________