I thought this may be of interest to any one trying to bug fix the crossfire flicker, maybe its been mentioned before, but I haven't seen it.

Basically since C2 is slightly **** on cross fire. I decided to entertain my self on a different game ( Assassins Creed BH) until a patch came out.


After a blast on AC BH I went on to C2 to check for any updates and found none so I went straight back into AC BH.

Oddly enough the flicker followed me =S. So now AC which was running absolutely fine before is flickering to? So I logged in and out of windows , booted AC back up and it was all fine again no flicker?

I repeated this 3 times to reduce the chance of coincidence. Anyway I figure you guys or Crytek might find this info useful in some way.

Maybe test it for your selves see what you get?

The flicker seems to be due to the lighting glow/flare effects being rendered on one GPU and not the other. If you enable vsync and force AFR (alternate frame rendering) one will see seizure-inducing flicker (on one frame, off the next).

There's also a second issue with 'gamma' or something similar, where one frame is rendered at 1 brightness, and the other at a different one. Going into options->brightness and changing it a notch seems to help.

Nice info cheers.

I managed to fix it forcing a Bioshock setting on it with RadeonPro as suggested in the forum.

I just found it really strange that it would carry the issues over to a totally different game. As if its corrupting commands in the Ati Driver when I start Crysis 2. ( This is without having RadeonPro Enabled.)

This happened to me as well, but just logging off my windows name and logging back in fixed the problem for me as well.

I have been able to duplicate it though.

This happened to me as well, but just logging off my windows name and logging back in fixed the problem for me as well.

I have been able to duplicate it though.


That's interesting, definitely disproves a coincidence then. So just out of curiosity which 2 games was it?

If the issue is caused by Bloom/HDR not rendered on GPU #2, wouldn't the console command "r_HDRLevel=0" fix the problem?

Hi there - I noticed this too. I run an HD5970 2GB and when I try to play Crysis 2, I get the infamous screen flickering. I then tried to run Shogun 2 and the flickering followed. This is 100% repeatable. Crysis 2 seems to screw with the display and leave something hanging in memory.

the only cure is then a full reboot.

Hi there - I noticed this too. I run an HD5970 2GB and when I try to play Crysis 2, I get the infamous screen flickering. I then tried to run Shogun 2 and the flickering followed. This is 100% repeatable. Crysis 2 seems to screw with the display and leave something hanging in memory.

the only cure is then a full reboot.


Ahh, at least you know Crysis 2 is the cause and you can just restart to get the other game working. I wish the same could be said for Crysis 2 its self =/. Try a log in and out? works fine for me and much quicker .

Hope they fix this soon, the game is so much fun, but I don't like the idea of my other investment ( GPU 2 ) sitting doing nothing.