Hello again!

Seems that there is a fix that works more properly!

It's similiar to the "rift.exe" solution, only a different profile, what actually happens is Catalyst applies different options to the application:

Instead of changing the "Crysis2.exe" to "rift.exe", set it to "FEAR.exe". This worked pretty good for me!

* No more flickering
* Maximum framerate (Crossfire enabled)
* For AMD users

But there may be a little disadvantage for this fix: slight mouse lag. Just like in V-sync.

I'm calling out all other users to spread the word to other AMD users to finally play Crysis 2 decently, I hope this works for the most of ya!

Well, thank you man, seriously. I can't even count all that I have tried, not to mention renaming the crysis2.exe file in every way. Ironically, during one of my earlier attempts I did try fear.exe and fear2.exe but guess what, I typed both lower case saved the first letter. Out of frustration, I never thought about re-trying something that obvious, so thanks for sharing this. I finally gained enough fps that allow me to enjoy the game.

If you get mouse lag with FEAR.exe you can try bioshock.exe
For me, bioshock.exe runs twice as fast as rift.exe and I have no mouse lag.

I can confirm that the new AMD catalyst version 11.3 for ATI graphic cards is doing the job!! Check my video!

Nice frame rates, fully functional Crossfire!!.
My setup, I get Nice Frame rates 60-70 fps settings:
2 x 6870 Crossfire
Q9550 Core2Quad OC @ 3612 MHz
8 Gb GEiL Ram, CL 7, OC @ 1480 MHz
resolution: 1920x1200
Crysis settings Extreme

I can confirm that the new AMD catalyst version 11.3 for ATI graphic cards is doing the job!! Check my video!

Nice frame rates, fully functional Crossfire!!.
My setup, I get Nice Frame rates 60-70 fps settings:
2 x 6870 Crossfire
Q9550 Core2Quad OC @ 3612 MHz
8 Gb GEiL Ram, CL 7, OC @ 1480 MHz
resolution: 1920x1200
Crysis settings Extreme

Unfortunately, the last Catalyst 11.3 plus Cap profile don't solve the problem to computers that have Ati radeon cards, but can only use the vendor proprietary drivers like DELL or Alienware. I still have to try the new patch, which I will do later today, let's see how it goes.