OHH NOW YOU DECIDE TO FIX MULTI GPU. WELL GUESS WHAT? NO ONE GIVES A SH*T, BECAUSE YOU WAITED TOO LONG. F*CK YOU CEVAT YERLI, SHOVE A dlldo UP YOUR ASS.

Just tested CAP3. Far as I can tell there is no difference between it and CAP1.

1) Flickering remains unless brightness is adjusted
2) really bad performance. <35 FPS in-doors

This is on Extreme, 2560x1440 with 2x5970s.

Getting a bit frustrated at AMD now. Why release something that claims to have "resolved" the issue when clearly insufficient testing was done?

p.s TY for the update Crytek

p.p.s Thank God Portal 2 comes out in less than a week.

CAP3 doesnt seem to change anything for me either on a single HD5970. in addition to flickering, the game stutters on extreme or high on 1920x1080. So in a way it's worse.

4 days to Portal 2 and if no fix by then, I'll probably stop caring

Bye Crysis, hello Portal.... real disappointment, shame you didn't last longer than a fortnight.

guys here is antiflickering from AMD
http://sites.amd.com/us/game/downloads/Pages/crossfirex-app-profiles.aspx

This is rubbish no problem on the demo so the fix should be easy. Revert to what you did before you broke it

CatalystCreator Andrew D
Thanks - a new version of CAP 3 (up soon on Rage3D, and hopefully AMD GAME) will fix AC Brotherhood, also Crysis 2 scaling is a bit better
1 hour ago

I loaded the updated 11.3Cap3 (i checked the serial number in Programs and Features and it was higher than the other 11.3cap3) and I did see improved performance, I can play now, finally!

http://sites.amd.com/us/game/downloads/Pages/crossfirex-app-profiles.aspx

Yeah well don't forget us who have the 4870 X2 with both GPU's Built right into them I can't disable them that I know and still no fix.

Official 11.3 cap3 off ati's website fixed everything for me for the most part. Flickering is gone, although I do get some black lines going up and down the screen once in a while but its really not noticeable. Getting a solid 75-120 fps on max settings on 1680x1050. Using two hd 5770's.

Game looks amazing.

CatalystCreator said, "Any app that you see flickering in with CF (Crossfire) is because the app doesn't work well with AFR."

Here's to Patch 1.3 fixing this issue for everyone, and Crossfire scaling getting even better in time for DX11 !

Did have 11.4 drivers installed and then installed 11.3 CAP3's and ran the game in xfire. What a load of crap. Totally unplayable. It had dark circular shapes directly in my line of vision that moved all over the screen whenever I moved. When I aimed down the sights, anything in the sights was extremely dark.
Disabled xfire and everything was sweet.
Heard that the latest CAPS worked best with the 11.3 drivers, so I uninstalled 11.4's and installed 11.3.
Rebooted and ran the game. no difference.
Renamed Crysis2.exe to Rift.exe and the problem went immediately.
Getting between 45 and 60fps with Vsync enabled and graphics set to hardcoe with my 6870's. Does that seem about right?
Anyway, this needs to get fixed and I reckon that the onus is on Crytek to fix it.

For those of you who have flickering problems with 560, 570 or 580 cards in SLI: turn off MSAA in your autoexec.cfg file, if you have one, otherwise create one with Notepad, and add this line or change value:

r_PostMSAA = 0

The game's MSAA is causing the problems for me. However, you are able to force MSAA through Nvidia Inspector. Look up "Crysis 2 SGSSAA" on Youtube for more information. This may work for older Nvidia cards as well.

5870 CF / W7 64
> nothing worked for me so far
only renaming the .exe in rift.exe is a solution for me to get rid
of this ***** flickering .
I am sick of wasting my time with problems.
2nd playthrough canceled.
perhaps a later try when this piece of pre-release ist out of beta.

EA and Crytek take your money and be happy ....this time.
But i think you made a lot of pc-gamers upset.
its not only the sli/cf problem.
a lot of bugs (the soundbug in one level made me rush it through,nanobug before patch made me also sad).
4 options to tune the engine ? LOL ! had to use an autoexec cfg.
http://cell-systems.net/cfg-maker/client-cfg-maker/create-crysis2%E2%80%9D-autoexec-cfg/
hmm ... a bunch of options and you only give us 4 ? There is a reason that some people
use a gaming-pc and not an xbox or ps3.
Even the advantage to give the pc-gamers better (hires) textures was not a question.

So you created another medium console ported pc-game with an beta release.
And not the wtf blockbuster the gamers expected.
(i can`t remember that Farcry or Crysis was so bugged when released )

you want my money for your game ? ok but give something in exchange !
and i expected either a good ported console game with minor bugs (and i mean minor)
or a really ansome pc-game.

end of rant
know playing hl2 cinematic mode

I just bought the AMD 6990 and now the game is un playable, ¤#"/&%#¤",

When eill there be a patct that can fix the problem??

HD5970 card on a win 7 64 bit OS

- uninstalled ATI catalyst, rebooted, ran Driver Sweeper, rebooted

- downloaded Catalyst Software Suite 11.3 for win 7 64bit (date posted 3/29/2011)
- downloaded Catalyst Application Profiles 11.3 CAP3 (date posted 4/15/2011)
-> http://sites.amd.com/us/game/downloads/Pages/radeon_win7-64.aspx

- installed Catalyst Software Suite 11.3, rebooted
- installed Catalyst Application Profiles 11.3 CAP3, rebooted

- uninstalled Crysis 2. reinstalled, patched to 1.2, rebooted

run the game ... it still flickers...it still effing flickers. no change whatsoever.

I've just about HAD it endlessly updating drivers, CAPs, trying miracle fixes, endlessly rebooting after updates/fixes/etc and wasting DAYS trying to troublehoot this and spend DAYS on these forums.

I got a cupboard full of games and every single one runs on this card. every single one. so its not the card, its not the driver, its not the cap, its your fracking game thats faulty.

Your devs should be ashamed not testing this properly. Such a fraud selling a faulty game that you know PC users can't return to the shop they bought it in. shame on you.

I am SO over this now lol. This is my last post, no more rants from me, and good luck to all you fellow 5970's out there

All I did was take the Crysis2.pak from it's current location and moved it to bin32, once there, I renamed it to deadspace2.exe and I am able to run it with crossfire enabled I'm using HD 5870 Mobility and having no problems getting 50 to 60 FPS.

I'm not exactly that advanced in this, so if I overlooked something or sound like a moron I apologize.

You cant move a .pak-file and rename it into an .exe...well you can, but it wont work.

So no, you're not a moron but there are other words to describe what you are...

I reported your post to the mods...I doubt I'm on their good side considering my posts on this forum, but I hope they'll kick your ass out of here. If anyone follows what you posted, their install will be eff-ed.

I think he meant the .bak file (in backup folder).

Yeah, he probably meant the Crysis2.exe.bak file.
I tried that myself and it did work (partly), but I still had some slight flickering.

Crysis2.exe.bak file this is the file I am talking about in the backup folder, for some reason I am not getting any flickering at all.

I saw this fix in another post, but they only named it to Crysis2.exe.

Crimson, was the game still playable?

I'm not seeing any flickering, I have also updated CCC and put all the 3D settings to max, so far no problems.

p.s

I really only signed up because I saw this thread through google and thought I could help, why are these **** everywhere "Agamemnon_71 " you sound like a 11 year old, what you could of done was help me to clearly articulate the steps I had performed with the overall goal of helping this flickering situation.

Crimson, was the game still playable?

I'm not seeing any flickering, I have also updated CCC and put all the 3D settings to max, so far no problems.Still playable. Just a little flickering around objects like the sun.
Renamed the crysis2.exe file to 'rift' now and the flickering is gone.

For those of you who have flickering problems with 560, 570 or 580 cards in SLI: turn off MSAA in your autoexec.cfg file, if you have one, otherwise create one with Notepad, and add this line or change value:

r_PostMSAA = 0

The game's MSAA is causing the problems for me. However, you are able to force MSAA through Nvidia Inspector. Look up "Crysis 2 SGSSAA" on Youtube for more information. This may work for older Nvidia cards as well.


Nice work around! For those who want to use AA with the fix here's a link to the video on how to set up SGSSAA. Looks nice! You'll need Nvidia inspector for this as well.

http://www.youtube.com/watch?v=fbjr72VYepo