• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

I love Eyefinity

Chris_B said:
Not sure how you're managing to get it working since the bug effects both eyefinity and surround setups, both camps have been bitching about it and dice has yet to shift their lazy fucking asses to get it fixed.

Ive seen plenty of threads on the issue and it occured when an update for bc:nam was issued, apparently it broke bc2 eyefinity but supposodly nam isnt affected. Its been an issue now for nearly 8 months and dice hasnt done shit to rectify it. The same bug occurs on the multiplayer of that turd 2010 moh.
Click to expand...

I run BC2 on low settings to max out fps, and had no such issue.

Leaving BC2 for good when Bf3 hits the shelf.
 
Flopper said:
I run BC2 on low settings to max out fps, and had no such issue.

Leaving BC2 for good when Bf3 hits the shelf.
Click to expand...

Same here, if I turn BC2 graphics down to around medium it seems to run fine...its when i jack everything up to max that I run in CTD issues.
 
USMCGrunt said:
Same here, if I turn BC2 graphics down to around medium it seems to run fine...its when i jack everything up to max that I run in CTD issues.
Click to expand...

trail and error should sort what setting crashes the game
(not for me tho) ;)
 
Kor said:
I like my eyefinity setup, but i'd like it a whole lot more if v-sync worked in crossfire.
Click to expand...

So this is still an issue? I jumped from eyefinity to surround primarily because of this... but I thought it had been sorted by now.. wow!
 
Chris_B said:
Not sure how you're managing to get it working since the bug effects both eyefinity and surround setups, both camps have been bitching about it and dice has yet to shift their lazy fucking asses to get it fixed.

Ive seen plenty of threads on the issue and it occured when an update for bc:nam was issued, apparently it broke bc2 eyefinity but supposodly nam isnt affected. Its been an issue now for nearly 8 months and dice hasnt done shit to rectify it. The same bug occurs on the multiplayer of that turd 2010 moh.
Click to expand...

There's nothing special going on. 6060x1200, 2XAA, everything set to max and HBAO off. I enabled and disabled it, absolutely cannot tell the difference during gameplay at all. The screenshots look a tad more detailed with it on, but when moving it's a moot point.

I can play for hours with no CTD on various SQDM servers. 11.6 cats.
 
revenant said:
So this is still an issue? I jumped from eyefinity to surround primarily because of this... but I thought it had been sorted by now.. wow!
Click to expand...

Nope, still broken and I doubt they will ever fix it (if they do it will be on a newer release of hardware only). I'll be jumping to surround once the 600 series lands as well.
 
You must log in or register to reply here.
Back
Top