Battlefield Bad Company 2 Clubhouse

[Lionheart]

Originally Posted by AthlonX2

what happened to all the TPU servers?

They got raped

Nah not sure man, I used to play on em when the game first came out, kurgan shall answer this one

[caleb]

Hey

Anybody with clanbase laddering expierience up to start a clan and play some matches ?
Did a lot of that CB stuff a few years back and matches are always 10x the fun on public.
From what Ive seen on CB you need at least 4 to play some ladder.
ATM maybe I have 2 players and a TS server.

[1Kurgan1]

Originally Posted by AthlonX2

what happened to all the TPU servers?

There seemed to only be a few of us that were a strong base of players, maybe 10, but beyond that I don't remember too many others in our servers. They would be popular during peak hours and stay going popular, but as soon as they went down they wouldn't be populated for a long time. So it just wasn't worth it to keep them up sadly.

[sapetto]

New BFBC2 PC patch announced for Wednesday June 30th

We are happy to announce the release of the new patch on June 30th.

All game servers will need to be taken down for updates. The maintenance period starts on Wednesday Jun 30th at 07:00AM (GMT+2). Most of them should be back up by 11:00AM (GMT+2).

Changelog in the link

LINK

[Lionheart]

Originally Posted by sapetto

Changelog in the link

LINK

God... I hope it comes out 2moro

[Pickles24]

Looks like tomorrow the 30th!

"We are happy to announce the release of the new patch on June 30th. All game servers will need to be taken down for updates. The maintenance period starts on Wednesday Jun 30th at 07:00AM (GMT+2). "

[MT Alex]

Originally Posted by AthlonX2

what happened to all the TPU servers?

In my opinion, they suffered from TPUers living in different time zones. Whenever I checked during my free time (GM +7) they were always empty.

[Tatty_One]

Originally Posted by MT Alex

In my opinion, they suffered from TPUers living in different time zones. Whenever I checked during my free time (GM +7) they were always empty.

Isn't that GMT -7?

http://www.worldtimezone.com/

Unless of course you now live in Cambodia.

[GullyFoyle]

Prepare for the patch: Document your key bindings before the upgrade?

http://forums.electronicarts.co.uk/b...l#post14823904

Originally Posted by MikaelKalms

Due to how the config files are structured, you will have to re-do your keyboard customizations with client R8. (If your input config files are pre-R8 then the game will ignore their contents.)

Patch mysteries:

Will the Garand Stats be fixed? They refuse to do the legwork to confirm this on the PC. It's fixed on the consoles, so we can hope.
Will Map Pack 3 be immediately active after the patch? (Laguna Alta Squad Rush, and Nelson Bay Squad Deathmatch)

WTF happened to Map Pack 4?

[1Kurgan1]

Originally Posted by TheLaughingMan

Wow, you read so deep into that you missed it all. I said the M60 is fine the way it is and doesn't seem unbalanced IMO. I then stated that every game will have something or some weapon that everyone can agree it is the way to go, the M60 is BFBC2's. I use the MG36 on non-hardcore because I get a free red dot sight.

Ah, sorry about that, but I still hear people now and then crying about the M60 and it boggles my mind. The MG36 free scope is nice, I just wish it hit a bit better. I used it in BC1, but in BC2 there has been numerous times where at mid range I watch the crosshairs show hits with 7+ bullets and the target lives with very little life, that many bullets from that gun should be death every single time.

[brandonwh64]

Originally Posted by 1Kurgan1

Ah, sorry about that, but I still hear people now and then crying about the M60 and it boggles my mind. The MG36 free scope is nice, I just wish it hit a bit better. I used it in BC1, but in BC2 there has been numerous times where at mid range I watch the crosshairs show hits with 7+ bullets and the target lives with very little life, that many bullets from that gun should be death every single time.

Since i have a sharpe dot on my screen, i use the MG36 with it and it owns! also another favorite of mine is the saw with ACC upgrade

[1Kurgan1]

I stay away from scopes, like the extra slot, The only kit I have issues with that is the Assault kit. I bounce between the M16 and the XM8, seems my play style with that kit changes now and then. Took me a while to figure it out, at first I thought it was patches buffing the weapons, but there hasn't been a patch in a while and sometimes I log on and wonder how the XM8 is so crappy or the M16, then I try the other and own, then the next time I log on it's the exact opposite.

Weird thing is, I don't have that happen with any other kit. And the reason why I think is because the XM8 I use iron sights and more explosives and the M16 I use a Red Dot, just plays out a lot differently, but as Medic or Eng I just use Iron Sights.

[GullyFoyle]

Originally Posted by brandonwh64

Since i have a sharpe dot on my screen

Does the same dot work for all guns? What about different games?

[GullyFoyle]

Well, here is the story that MikaelKalms promised us yesterday on the PC patch issues. Doesn't sound too promising for the future...

This is just a snippet:

Where do the problems begin?

When you begin creating patches.

First off, it turns out that the tools that "cook" the data don't produce binary-identical data all the time. The result after cooking is always functionally identical, but the bit-content may differ slightly. Items in unordered lists change order, uninitialized fields contain random data, that sort of stuff.

Why didn't this get caught sooner? Because you only notice problems of this kind when re-cooking the same data several times, from scratch. And re-cooking all BC2 data takes over 48 hours for a high-end computer. And locating & correcting all places where cooking isn't deterministic down to the bit level would take a lot of time (both calendar time and effective development time). Perhaps that time is better spent elsewhere?

So. If different "cooking" runs produce slightly different results, it is suddenly difficult to look at version A and version B of the data and answer the question, "what are the differences between these two datasets?". It's easy when looking at the source data, but when looking at the cooked data there are a lot of changes which have no effect on the final game experience.

There are about 40.000 source files, and this results in well over 100.000 cooked files. Going through those by hand is not an option. Writing a perfect filter, which knows which differences are benign and which are for real, will take as much time and effort as making the cooking 100% deterministic. Neither that is an option.

So you make a filter which does something in between; be smart, create rules for the file types you know about, and when in doubt - assume that the change is for real. Err on the side of caution.


Then you realize that those shader databases were never designed to be extendable. What happens when a new object is added to a level in a patch? Its mesh & textures are included, no sweat, but what about the shader combinations? How does one create add something to the shader database, when the shader database is an opaque binary block whose entire contents may change when just one object is added to the level?
(One shader database is about 5MB. There are three shader databases per level - one each for DX9, DX10 and DX11.)


And finally, the patch system itself. Yes, it can replace portions of files on-disk. But due to its heritage (from BF Heroes), it is not able to open BFBC2's archive files and apply differences to individual files within the archives.
The only straightforward way is to make all patched-in content arrive in archives on the side of the original archives.



Given the above scenario, we end up with the situation that we have today.

Each patch gets larger than the previous, because the game drifts ever further away from what was shipped on the DVD. Changes that require shader database updates make the patch balloon in size. And we have to be careful and clever when selecting which file types to include and which to ignore when creating the patch.

And that's where we finally ran into real problems. It was too difficult for one person to identify which changes were required and which were not, and how to update the patch generation process to accommodate the latest set of changes. Most of the delay of Client R8 was because there are very few people at DICE who have the in-depth knowledge of the far-spanning corners of the game engine *and* the cooking tools *and* the patch generation process, to work out what is going wrong, why, and how to fix it.

The new content did work a long while ago - but the patch was back then approximately 7GB large. The patch had to get down to less than 1GB, or else some customers in Australia and South Africa would not be able to download it due to bandwith caps.

[Mussels]

:O they care about us aussies!

[AphexDreamer]

Don't know if its been said but they are releasing a patch the 30th

http://www.qj.net/qjnet/games-for-wi...-tomorrow.html

[erocker]

My game is updating right now.

[Perra]

just started updating mine... and there it was done... wow, nice speeds

Time to play a lot today

[AphexDreamer]

Originally Posted by erocker

My game is updating right now.

lol I'm out of it just realized thats tomorrow. Yeah mine updated too.

[Mussels]

you guys steam or retail? my steam hasnt started yet

[AphexDreamer]

Originally Posted by Mussels

you guys steam or retail? my steam hasnt started yet

Steam over here.

Also I got a CTD... don't know what caused it.

[Lionheart]

Gonna check it out

[Scrizz]

so is it good?

[Tatty_One]

So for non steam retail versions of the game, do we need to download?

[Mussels]

Originally Posted by Tatty_One

So for non steam retail versions of the game, do we need to download?

i'd say 'yes'