Widescreen Gaming Forum

I have been playing VN (which is rubbish compared to vanilla IMO) without a crash too. However I can go weeks without crashes then all of a sudden get a heap in one evening.

Verdict still not out for me yet, in a month or so with no crashes, maybe :)

Yeah from what I was told the fix hasn't made it into live yet. Should be ASAP though.

Maybe Vietnam had it already? Who knows.

Hey guys, my first post here ...

I'm an avid player of BFBC2; and I too have been having random c2d's every now and then in the original. I notice no crashes in Vietnam, not a single one and I've played it a ton since release.

There are a few fixes for c2d's in the original bad company 2 - try lowering your direct X version via the config file to 9 or 10 - this can work.

Good to hear that DICE are aware of the bug however - hope they fix the problem shortly.

I have to say; playing bfbc2 maxed at 8100 x 1440 is a treat

Hey guys, my first post here ...


I have to say; playing bfbc2 maxed at 8100 x 1440 is a treat

Damn, son. That's some RESOLUTION :) :hide

Ive also noticed that I only get crashes in BC2 but vietnam works like a dream

Ive also noticed that I only get crashes in BC2 but vietnam works like a dream

I'm having the same experience myself. So I've been sticking with Vietnam for now.

[quote]Ive also noticed that I only get crashes in BC2 but vietnam works like a dream

I'm having the same experience myself. So I've been sticking with Vietnam for now.

Me three.

Looks like the clowns at DICE have still left this issue unresolved. This game worked fine in Surround months ago, but I tried it last night in Eyefinity and discovered frequent CTDs and, subsequently, threads like this one.

The CTD with NV Surround (rather than the random once every round or none for a week with Eyefinity) for me has been one crash on the first round I play then it is fine for the rest of the evening. It has done that every time I play... all very weird.

[quote][quote]Ive also noticed that I only get crashes in BC2 but vietnam works like a dream

I'm having the same experience myself. So I've been sticking with Vietnam for now.

Me three.

Me 4. Unfortunately my clan has moved back to BC2 for competitions and they won't let me play until I can promise that I won't crash out mid-game.

I cannot make that promise.

I am going to install Windows 7 SP1 as I've heard that has some multi-monitor fixes. Will report back.

Was also thinking that this could have something to do with and old sound-card in my machine, but too many of you are having the problem. (Old Creative X-fi.)

I get the same random CTD in Need for Speed Shift.

The frequency of crashes is affected by my physx settings in Nvidia control panel, but maybe I'm imagining that with all you ATi guys suffering too.

Me 4. Unfortunately my clan has moved back to BC2 for competitions and they won't let me play until I can promise that I won't crash out mid-game.

I cannot make that promise.

I am going to install Windows 7 SP1 as I've heard that has some multi-monitor fixes. Will report back.

Was also thinking that this could have something to do with and old sound-card in my machine, but too many of you are having the problem. (Old Creative X-fi.)

I get the same random CTD in Need for Speed Shift.

The frequency of crashes is affected by my physx settings in Nvidia control panel, but maybe I'm imagining that with all you ATi guys suffering too.

This has nothing to do with anything but DICE's typical incompetence.

To repeat, the game was working fine before they themselves fucked it up in the latest patch. It's inexcusable to not have immediately fixed something they already had working and then broke.

Sadly, I must confirm that installing SP1 (and in fact an entirely new partition just for BC2 and nothing else) did NOT fix the problem.

3 Crashes in 40 minutes last night, then I gave up and went back to single screen (with Nvidia 3D) and had no more problem at all.



Does anyone know whether Dice even cares about this, or are we "widescreen gamers" in such a minority that they don't care?


(One would assume that they should look after us FIRST, as we are the trend-setters, and obviously have too much money for our toys.)

They care... they have a patch almost ready to deploy with the fix for these crashes. Just wish it would come out soon :)

They care... they have a patch almost ready to deploy with the fix for these crashes. Just wish it would come out soon :)

I'm not holding my breath. It was nearly 2 months ago that was said and still nothing.

I have noticed that when I OC my cards I get the CTD almost routinely. Now if I go down to stock speeds (Below EVGA Superclocked) speeds I get 100% playable expierence. Is it just me or am I way off base for the troubleshooting that you guys are going for?

I have noticed that when I OC my cards I get the CTD almost routinely. Now if I go down to stock speeds (Below EVGA Superclocked) speeds I get 100% playable expierence. Is it just me or am I way off base for the troubleshooting that you guys are going for?

My cards aren't OC'ed at all.

so what exactly is causing the crashes

so what exactly is causing the crashes

Not sure, but it's not in our configs. The dev I was communicating with didn't say specifically what it was, but that they had identified the cause and fixed it in a beta client. After testing I can confirm that on my system the crashing has stopped. I think it's just that they wanted to roll the fix into their next client update, but due to how convoluted a process that is for bc2 it might be that other parts of the update are holding it back.

[quote]so what exactly is causing the crashes

Not sure, but it's not in our configs. The dev I was communicating with didn't say specifically what it was, but that they had identified the cause and fixed it in a beta client. After testing I can confirm that on my system the crashing has stopped. I think it's just that they wanted to roll the fix into their next client update, but due to how convoluted a process that is for bc2 it might be that other parts of the update are holding it back.

Well it would be nice to have a fix in place before BF3 it out. Otherwise, what is point?

Oh and how much do you want to bet the same issue is going to show up in BF3?

Oh and how much do you want to bet the same issue is going to show up in BF3?

Well, since they've fixed it internally and know what caused it, my guess is no, it won't be in BF3.