As I said before: Name any other GAME-ENGINE that handles Multi-GPU as bad as CryEngine...Feel free to enlighten me.

I'm feeling less and less inclined to "enlighten" the people on this thread. It seems that no matter how valid the evidence that's brought to the table, it's always shot down with irrational mumble, claiming that I'm incorrect when the one's making the accusations fail to bring any credible evidence to support their suppositions.

Every game I listed previously utilize their own unique graphic engine, save for APB and Crysis Warhead. If you like, I could list off the multi-GPU issues that those games started off with on AMD's side. Regardless, I really don't need to enlighten you on what game engines have had a rough start utilizing multi-GPU systems. That is irrelevant. What's relevant is that results show that alternating driver profiles and/or versions fix the issue, as well as the fact that AMD addressed the issue for Crysis 2 specifically in their driver release notes.

I'm feeling less and less inclined to "enlighten" the people on this thread. It seems that no matter how valid the evidence that's brought to the table, it's always shot down with irrational mumble, claiming that I'm incorrect when the one's making the accusations fail to bring any credible evidence to support their suppositions.


Quoting AMD and NVidia (not to mention the fact that CryTek acknowledges the issue on their end are still looking into it) doesn't qualify as evidence to you? How about the first hand reports of issues, that also doesn't count as evidence?

Can we all just agree that Crytek and Nvidia just need to procreate and give birth to the solution? (For some ATI would be the partner, I am not forgetting you:/)

Cry-Adam
Joined: 06 11, 2010 /02:09

Posts: 1994

Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 05 26, 2011 /08:41
Re: Crysis 2 Multi GPU support causes insane flickering. 05 26, 2011 /08:41

/merged with main m-gpu flickering thread.

This issue is still being investigated. Sorry i don't have any more info on this issue currently!

but... but... but... lavans6879 does!!!

This thread is so funny!

Thanks for the update Cry-Adam.

Quoting AMD and NVidia (not to mention the fact that CryTek acknowledges the issue on their end are still looking into it) doesn't qualify as evidence to you? How about the first hand reports of issues, that also doesn't count as evidence?

Actually, no, it doesn't. There has been no evidence actually showing that the solution can be resolved via altering the application. However, as AMD's official patch notes states, the issue is related to the drivers. Furthermore, AMD has fully demonstrated a working fix via updating their drivers. Furthermore, I'm not the only person in this thread that has reported that updating AMD's drivers resolved the issue.

Basically what you're trying to do is this. You're trying to argue that grass is blue, simply because someone says so, despite being shown pictures that grass is actually green.

You're citing quotes from individual representitives. I'm quoting actual patch notes straight from AMD. Which do you honestly think holds more weight?

No one's denying what's been stated by these reps. What's being discussed at this time is the claims of those reps vs AMD's patch notes, which again, resolves the issue for a number of people.

Can we all just agree that Crytek and Nvidia just need to procreate and give birth to the solution? (For some ATI would be the partner, I am not forgetting you:/)

ATi have already given us ATi users the solution. A simple crossfire profile update. I didn't even need to update my drivers.

IMHO, unless there's something 'special' about nVidia cards that means the issue lies with Crytek...nVidia needs to get off their lazy backsides and code a profile for it. Because that seemed to work fine with ATi. (Then again whether ATi worked with Crytek or not to fix it, I don't know.)

Quoting AMD and NVidia (not to mention the fact that CryTek acknowledges the issue on their end are still looking into it) doesn't qualify as evidence to you? How about the first hand reports of issues, that also doesn't count as evidence?

Actually, no, it doesn't. There has been no evidence actually showing that the solution can be resolved via altering the application. However, as AMD's official patch notes states, the issue is related to the drivers. Furthermore, AMD has fully demonstrated a working fix via updating their drivers. Furthermore, I'm not the only person in this thread that has reported that updating AMD's drivers resolved the issue.

Basically what you're trying to do is this. You're trying to argue that grass is blue, simply because someone says so, despite being shown pictures that grass is actually green.

You're citing quotes from individual representitives. I'm quoting actual patch notes straight from AMD. Which do you honestly think holds more weight?

Well then, the grass in my garden is clearly blue, because no updates fixed the problem 100% for me. They merely removed one problem, replacing it with another.
Also, don't forget the game worked fine (though not optimized scaling wise) on multi-GPU platforms BEFORE CryTek released their first patch, which then led to the issues. IMO that points towards application end problems

Well then, the grass in my garden is clearly blue, because no updates fixed the problem 100% for me. They merely removed one problem, replacing it with another.
Also, don't forget the game worked fine (though not optimized scaling wise) on multi-GPU platforms BEFORE CryTek released their first patch, which then led to the issues. IMO that points towards application end problems

Then you're either doing something wrong or AMD has yet to provide support for QuadFire systems in Crysis 2.

Well then, the grass in my garden is clearly blue, because no updates fixed the problem 100% for me. They merely removed one problem, replacing it with another.
Also, don't forget the game worked fine (though not optimized scaling wise) on multi-GPU platforms BEFORE CryTek released their first patch, which then led to the issues. IMO that points towards application end problems

Then you're either doing something wrong or AMD has yet to provide support for QuadFire systems in Crysis 2.

How are any of us "doing something wrong" if the game did not have this problem before the update? Dude dial it back some, ur autism is showing!

This problem was recently fixed in the 175.XX version of Nvidia drivers.

http://www.nvidia.com/object/win7-winvista-64bit-275.27-beta-driver.html

I thought I'd just add my experiences with Crysis 2 and crossfire. I have two hd 5770's, phenom II x4, decent ram and mobo and all that.

There was one specific driver that ATI released that solved the problem for me and all was well. Got really decent fps and could actually play it on high (Extreme) settings. My computer was a little loaded with unnecessary crap so I reformatted. After that I installed latest drivers and app profiles and crossfire is nonfunctional once again. The xfire logo comes up saying that it's using it but the frame rates are lower than using a single card and it's really choppy. There's also horrible input lag.

So I tried reinstalling the original drivers and app profiles that worked before, and tried a few other drivers and still can't get it to work.

I just hope ATI/Crytek haven't given up on fixing crossfire. Granted, it worked before but with their new app profiles and drivers it's still not working. Other than the consolization of one of my favorite games of all time, I did like the SP for crysis 2. Story was pretty cool. Don't play MP much cause the cloaking drives me crazy.

Also, even when crossfire was working the game was really choppy. Poor scaling maybe?

Hope they can fix this problem though. Already played through the SP but would like to play through it again on higher difficulty if you guys can fix this whole xfire issue.

This problem was recently fixed in the 175.XX version of Nvidia drivers.

http://www.nvidia.com/object/win7-winvista-64bit-275.27-beta-driver.html

Can u confirm this? What card are you using? For me the only map I rly get flickering on is Seat of Power, does this map run flicker free now? I will try these drivers out when I get home. thank you for the update, I hope this is true!

Just browsed through multiple forum posts on the 175.29 drivers. Several people claim the flickering is not fixed and other people say they are very unstable causing crashes and artifacting. Unfortunately I think I will pass on these, not worth the headache. Since I only play Crysis 2 on single player I think I will be forced to roll back my game version to before 1.1 until 1.5 hopefully fixes these issues:(

Just browsed through multiple forum posts on the 175.29 drivers. Several people claim the flickering is not fixed and other people say they are very unstable causing crashes and artifacting. Unfortunately I think I will pass on these, not worth the headache. Since I only play Crysis 2 on single player I think I will be forced to roll back my game version to before 1.1 until 1.5 hopefully fixes these issues:(

It's possible it only resolves the issue for certain GPU types. For the ones that reported the updated drivers fixing the issue, did they post their system specs? If so, did they use similar cards?

The patch notes indicate that it resolves a flickering issue for the GTX295 on Crysis, but it doesn't indicate if it's Crysis 1/WH or 2.

http://us.download.nvidia.com/Windows/275.27/275.27-Win7-WinVista-Desktop-Release-Notes.pdf

I thought I'd just add my experiences with Crysis 2 and crossfire. I have two hd 5770's, phenom II x4, decent ram and mobo and all that.

There was one specific driver that ATI released that solved the problem for me and all was well. Got really decent fps and could actually play it on high (Extreme) settings. My computer was a little loaded with unnecessary crap so I reformatted. After that I installed latest drivers and app profiles and crossfire is nonfunctional once again. The xfire logo comes up saying that it's using it but the frame rates are lower than using a single card and it's really choppy. There's also horrible input lag.

So I tried reinstalling the original drivers and app profiles that worked before, and tried a few other drivers and still can't get it to work.

I just hope ATI/Crytek haven't given up on fixing crossfire. Granted, it worked before but with their new app profiles and drivers it's still not working. Other than the consolization of one of my favorite games of all time, I did like the SP for crysis 2. Story was pretty cool. Don't play MP much cause the cloaking drives me crazy.

Also, even when crossfire was working the game was really choppy. Poor scaling maybe?

Hope they can fix this problem though. Already played through the SP but would like to play through it again on higher difficulty if you guys can fix this whole xfire issue.

Using Catalyst 11.4 Preview + CAP 11.3 v1 gave me the best scaling while resolving the flickering, averaging around 90FPS with the game maxed out. I just installed Catalyst 11.5a lastnight and it seems to have negatively impacted the scaling, hitting around 60FPS or so when it should be hitting in the low 100's.

When you reinstalled your drivers, did you make sure to install the Catalyst Application Profiles as well?

Just browsed through multiple forum posts on the 175.29 drivers. Several people claim the flickering is not fixed and other people say they are very unstable causing crashes and artifacting. Unfortunately I think I will pass on these, not worth the headache. Since I only play Crysis 2 on single player I think I will be forced to roll back my game version to before 1.1 until 1.5 hopefully fixes these issues:(

It's possible it only resolves the issue for certain GPU types. For the ones that reported the updated drivers fixing the issue, did they post their system specs? If so, did they use similar cards?

The patch notes indicate that it resolves a flickering issue for the GTX295 on Crysis, but it doesn't indicate if it's Crysis 1/WH or 2.

http://us.download.nvidia.com/Windows/275.27/275.27-Win7-WinVista-Desktop-Release-Notes.pdf

I thought I'd just add my experiences with Crysis 2 and crossfire. I have two hd 5770's, phenom II x4, decent ram and mobo and all that.

There was one specific driver that ATI released that solved the problem for me and all was well. Got really decent fps and could actually play it on high (Extreme) settings. My computer was a little loaded with unnecessary crap so I reformatted. After that I installed latest drivers and app profiles and crossfire is nonfunctional once again. The xfire logo comes up saying that it's using it but the frame rates are lower than using a single card and it's really choppy. There's also horrible input lag.

So I tried reinstalling the original drivers and app profiles that worked before, and tried a few other drivers and still can't get it to work.

I just hope ATI/Crytek haven't given up on fixing crossfire. Granted, it worked before but with their new app profiles and drivers it's still not working. Other than the consolization of one of my favorite games of all time, I did like the SP for crysis 2. Story was pretty cool. Don't play MP much cause the cloaking drives me crazy.

Also, even when crossfire was working the game was really choppy. Poor scaling maybe?

Hope they can fix this problem though. Already played through the SP but would like to play through it again on higher difficulty if you guys can fix this whole xfire issue.

Using Catalyst 11.4 Preview + CAP 11.3 v1 gave me the best scaling while resolving the flickering, averaging around 90FPS with the game maxed out. I just installed Catalyst 11.5a lastnight and it seems to have negatively impacted the scaling, hitting around 60FPS or so when it should be hitting in the low 100's.

When you reinstalled your drivers, did you make sure to install the Catalyst Application Profiles as well?

Yeah I read those notes yesterday. Pretty sure that is crysis 1 and I have a 590. Think I am just going to roll the game back to before 1.1 and wait until nvidia releases drivers that claim to fix the issue for my card in teh release notes or until the game is updated with dx-11. I may try 1.5 though as the graphics adjustments and the possibility of setting the game higher then I have it already are tempting.

Well, with the latest drivers, I no longer have to disable my PhysX dedicated card to avoid the massive flickering, and the flicker in nanovision is gone.

The only remaining flickering is on the gun-sight and on the windows of cars like in this vid. http://www.youtube.com/watch?v=Y7nmZ676yvc

So I guess it's mostly playable now, but I'd love to see it totally flicker-free some day.

Well, with the latest drivers, I no longer have to disable my PhysX dedicated card to avoid the massive flickering, and the flicker in nanovision is gone.

The only remaining flickering is on the gun-sight and on the windows of cars like in this vid. http://www.youtube.com/watch?v=Y7nmZ676yvc

So I guess it's mostly playable now, but I'd love to see it totally flicker-free some day.

What about seat of power? The map where it starts to rain. Has the flickering in there been fixed for you?

Are you freaking kidding me Crytek?

Whatever you did with this latest patch, has broken it again. The flicker isn't screen-wide, but now the motion-blur is messed up with SLI again....

crytek..the game is out to long to still not have crossfire/sli support

so this was a nice way to show the people never to buy a crytek game again.. own fould this game is die-ing in MP aswell

great job !