You must have missed the part where everybody with Crossfire is saying none of these solutions work. The don't work for me, either.
Crysis 2 Multi GPU support causes insane flickering.
» Thu Dec 31, 2009 5:29 am
You must have missed the part where everybody with Crossfire is saying none of these solutions work. The don't work for me, either.
-
Amy Melissa - Posts: 3390
- Joined: Fri Jun 23, 2006 2:35 pm
» Thu Dec 31, 2009 10:10 am
You must have missed the part where everybody with Crossfire is saying none of these solutions work. The don't work for me, either.
Worked perfectly fine for me using a HD5970. Plus there are others posting in the linked thread stating it worked for them as well.
-
Amanda Leis - Posts: 3518
- Joined: Sun Dec 24, 2006 1:57 am
» Thu Dec 31, 2009 7:01 am
I tell you something. On my first Gtx 580 game was sometimes flicker , like horizontal lines and other geometric objects. I was thinking that card is overheating. But i change to other GTX 580 and ...the same problem. For me this game is a mistake. This game was not been released;(
Of course in different drivers.
Of course in different drivers.
-
Lynette Wilson - Posts: 3424
- Joined: Fri Jul 14, 2006 4:20 pm
» Thu Dec 31, 2009 12:09 pm
Nvidia reps themselves have said this flicker is an application issue with how the game handles alternate frame rendering and will need a fix from Crytek.
-
Aman Bhattal - Posts: 3424
- Joined: Sun Dec 17, 2006 12:01 am
» Thu Dec 31, 2009 4:45 pm
Nvidia reps themselves have said this flicker is an application issue with how the game handles alternate frame rendering and will need a fix from Crytek.
I'm sorry, but Nvidia reps are feeding you misinformation. Applications do not communicate with computer drivers, they communicate with an API. In this case, Crysis 2 ( the APP ) is communicating with DirectX 9 ( the API ), which in turn is interpreted by your drivers. FURTHERMORE, AFR ( alternate frame rendering ) is a driver level, multi-GPU specific setting. You cannot trigger a multi-GPU rendering method via the application, regardless if it's AFR, Scissor, or Supertile. It MUST be set via the drivers. Not only that, but a game cannot be developed "with AFR in mind", as the Nvidia reps are implying. Multi-GPU rendering methods aren't handled by the game engine. The drivers must know how to interpret what the engine is trying to render through the API when calculating any multi-GPU render.
To understand this, you might need to know what AFR actually is. AFR is a very raw and unstable multi-GPU method, but is typically the most effective at producing a high FPS compared to other multi-GPU methods. What AFR does is evenly divides the workload between video cards. In dual GPU setups, GPU1 calculates every odd frame, while GPU2 calculates every even frame. This usually leads to graphical "bugs", for lack of a better term. As such, AFR is commonly avoided. The typical go-to multi-GPU rendering method is Scissor, regardless if you're using AMD or Nvidia.
If you want proof on this statement, load up Crysis 2 using Bioshock's SLI profile. You'll find that not only does the flickering stop, but SLI scales properly with the game. This is a CLEAR indication that the issue is related to the drivers, not with the game. Rule of thumb, when troubleshooting a graphical issue such as this, if changing driver level settings resolves the issue, then it's a driver related issue. If it was a problem with the game, then changing driver settings would yield absolutely NO beneficial results. But this is not the case, which was demonstrated when AMD released proper CrossFireX profiles that resolved the issue with the CAP linked above.
I'm sorry, but Nvidia reps are feeding you misinformation. Applications do not communicate with computer drivers, they communicate with an API. In this case, Crysis 2 ( the APP ) is communicating with DirectX 9 ( the API ), which in turn is interpreted by your drivers. FURTHERMORE, AFR ( alternate frame rendering ) is a driver level, multi-GPU specific setting. You cannot trigger a multi-GPU rendering method via the application, regardless if it's AFR, Scissor, or Supertile. It MUST be set via the drivers. Not only that, but a game cannot be developed "with AFR in mind", as the Nvidia reps are implying. Multi-GPU rendering methods aren't handled by the game engine. The drivers must know how to interpret what the engine is trying to render through the API when calculating any multi-GPU render.
To understand this, you might need to know what AFR actually is. AFR is a very raw and unstable multi-GPU method, but is typically the most effective at producing a high FPS compared to other multi-GPU methods. What AFR does is evenly divides the workload between video cards. In dual GPU setups, GPU1 calculates every odd frame, while GPU2 calculates every even frame. This usually leads to graphical "bugs", for lack of a better term. As such, AFR is commonly avoided. The typical go-to multi-GPU rendering method is Scissor, regardless if you're using AMD or Nvidia.
If you want proof on this statement, load up Crysis 2 using Bioshock's SLI profile. You'll find that not only does the flickering stop, but SLI scales properly with the game. This is a CLEAR indication that the issue is related to the drivers, not with the game. Rule of thumb, when troubleshooting a graphical issue such as this, if changing driver level settings resolves the issue, then it's a driver related issue. If it was a problem with the game, then changing driver settings would yield absolutely NO beneficial results. But this is not the case, which was demonstrated when AMD released proper CrossFireX profiles that resolved the issue with the CAP linked above.
-
latrina - Posts: 3440
- Joined: Mon Aug 20, 2007 4:31 pm
» Thu Dec 31, 2009 3:35 am
Latest drivers, Latest CAP. Flickering persists until Brightness is adjusted (problem 1). Adjusting brightness adversely affects performance (problem 2).
Holding out for DX11 patch. Hoping that fixes things as Crytek clearly are content to leave those who still have problems yelling into the blue nowhere.
p.s @Iavans6879 When Crytek updated their list of fixed drivers they failed to update it 1-2 days later when the CAP creator acknowledged that there was a last minute bug with them.
Holding out for DX11 patch. Hoping that fixes things as Crytek clearly are content to leave those who still have problems yelling into the blue nowhere.
p.s @Iavans6879 When Crytek updated their list of fixed drivers they failed to update it 1-2 days later when the CAP creator acknowledged that there was a last minute bug with them.
-
Tinkerbells - Posts: 3432
- Joined: Sat Jun 24, 2006 10:22 pm
» Thu Dec 31, 2009 1:51 pm
p.s @Iavans6879 When Crytek updated their list of fixed drivers they failed to update it 1-2 days later when the CAP creator acknowledged that there was a last minute bug with them.
A last minute bug with what?
Source?
A last minute bug with what?
Source?
-
Jessie Rae Brouillette - Posts: 3469
- Joined: Mon Dec 11, 2006 9:50 am
» Thu Dec 31, 2009 1:39 pm
**** this game anyhow. It's uninstalled and can rot in hell.
-
Lauren Graves - Posts: 3343
- Joined: Fri Aug 04, 2006 6:03 pm
» Thu Dec 31, 2009 10:49 am
Late to the game here..........just bought the game yesterday and decided to read some of the forums and stumbled upon this one. I've been playing the game and I don't have any flickering at all, it runs smooth as silk with my setup.
-
Natasha Biss - Posts: 3491
- Joined: Mon Jul 10, 2006 8:47 am
» Thu Dec 31, 2009 4:49 am
Haven't played in a month, I'm just gonna play Bad Company 2 until I see that it's fixed.
-
Ron - Posts: 3408
- Joined: Tue Jan 16, 2007 4:34 am
» Thu Dec 31, 2009 3:29 am
Nvidia reps themselves have said this flicker is an application issue with how the game handles alternate frame rendering and will need a fix from Crytek.
I'm sorry, but Nvidia reps are feeding you misinformation. Applications do not communicate with computer drivers, they communicate with an API. In this case, Crysis 2 ( the APP ) is communicating with DirectX 9 ( the API ), which in turn is interpreted by your drivers. FURTHERMORE, AFR ( alternate frame rendering ) is a driver level, multi-GPU specific setting. You cannot trigger a multi-GPU rendering method via the application, regardless if it's AFR, Scissor, or Supertile. It MUST be set via the drivers. Not only that, but a game cannot be developed "with AFR in mind", as the Nvidia reps are implying. Multi-GPU rendering methods aren't handled by the game engine. The drivers must know how to interpret what the engine is trying to render through the API when calculating any multi-GPU render.
To understand this, you might need to know what AFR actually is. AFR is a very raw and unstable multi-GPU method, but is typically the most effective at producing a high FPS compared to other multi-GPU methods. What AFR does is evenly divides the workload between video cards. In dual GPU setups, GPU1 calculates every odd frame, while GPU2 calculates every even frame. This usually leads to graphical "bugs", for lack of a better term. As such, AFR is commonly avoided. The typical go-to multi-GPU rendering method is Scissor, regardless if you're using AMD or Nvidia.
If you want proof on this statement, load up Crysis 2 using Bioshock's SLI profile. You'll find that not only does the flickering stop, but SLI scales properly with the game. This is a CLEAR indication that the issue is related to the drivers, not with the game. Rule of thumb, when troubleshooting a graphical issue such as this, if changing driver level settings resolves the issue, then it's a driver related issue. If it was a problem with the game, then changing driver settings would yield absolutely NO beneficial results. But this is not the case, which was demonstrated when AMD released proper CrossFireX profiles that resolved the issue with the CAP linked above.
Looks to me like you just used a lot of time telling us how CryEngine 3 svcks at communicating with the API (DX 9). FRA is indeed a very "raw" way of using multigpu and that makes it a very easy way to do it...that is if your gfx-engine were set up to do just that. If you, on the other hand, code your engine for DX-9 without multigpu support (read: consoles) then you might find yourself in this heap of sh-t.
You've posted four times on this forum, all in this thread. Why are you even here posting if everything works just great with your 5970? The way you try to blame the drivers and hardware in this case makes me suspect you're on "the other side" of this problem...
**** this game anyhow. It's uninstalled and can rot in hell.
+1
I'm sorry, but Nvidia reps are feeding you misinformation. Applications do not communicate with computer drivers, they communicate with an API. In this case, Crysis 2 ( the APP ) is communicating with DirectX 9 ( the API ), which in turn is interpreted by your drivers. FURTHERMORE, AFR ( alternate frame rendering ) is a driver level, multi-GPU specific setting. You cannot trigger a multi-GPU rendering method via the application, regardless if it's AFR, Scissor, or Supertile. It MUST be set via the drivers. Not only that, but a game cannot be developed "with AFR in mind", as the Nvidia reps are implying. Multi-GPU rendering methods aren't handled by the game engine. The drivers must know how to interpret what the engine is trying to render through the API when calculating any multi-GPU render.
To understand this, you might need to know what AFR actually is. AFR is a very raw and unstable multi-GPU method, but is typically the most effective at producing a high FPS compared to other multi-GPU methods. What AFR does is evenly divides the workload between video cards. In dual GPU setups, GPU1 calculates every odd frame, while GPU2 calculates every even frame. This usually leads to graphical "bugs", for lack of a better term. As such, AFR is commonly avoided. The typical go-to multi-GPU rendering method is Scissor, regardless if you're using AMD or Nvidia.
If you want proof on this statement, load up Crysis 2 using Bioshock's SLI profile. You'll find that not only does the flickering stop, but SLI scales properly with the game. This is a CLEAR indication that the issue is related to the drivers, not with the game. Rule of thumb, when troubleshooting a graphical issue such as this, if changing driver level settings resolves the issue, then it's a driver related issue. If it was a problem with the game, then changing driver settings would yield absolutely NO beneficial results. But this is not the case, which was demonstrated when AMD released proper CrossFireX profiles that resolved the issue with the CAP linked above.
Looks to me like you just used a lot of time telling us how CryEngine 3 svcks at communicating with the API (DX 9). FRA is indeed a very "raw" way of using multigpu and that makes it a very easy way to do it...that is if your gfx-engine were set up to do just that. If you, on the other hand, code your engine for DX-9 without multigpu support (read: consoles) then you might find yourself in this heap of sh-t.
You've posted four times on this forum, all in this thread. Why are you even here posting if everything works just great with your 5970? The way you try to blame the drivers and hardware in this case makes me suspect you're on "the other side" of this problem...
**** this game anyhow. It's uninstalled and can rot in hell.
+1
-
Angel Torres - Posts: 3553
- Joined: Thu Oct 25, 2007 7:08 am
» Thu Dec 31, 2009 6:17 am
Haven't played in a month, I'm just gonna play Bad Company 2 until I see that it's fixed.
Looks like you're gonna have to play it for a long time....
Looks like you're gonna have to play it for a long time....
-
A Boy called Marilyn - Posts: 3391
- Joined: Sat May 26, 2007 7:17 am
» Thu Dec 31, 2009 4:21 am
Looks to me like you just used a lot of time telling us how CryEngine 3 svcks at communicating with the API (DX 9). FRA is indeed a very "raw" way of using multigpu and that makes it a very easy way to do it...that is if your gfx-engine were set up to do just that. If you, on the other hand, code your engine for DX-9 without multigpu support (read: consoles) then you might find yourself in this heap of sh-t.
You've posted four times on this forum, all in this thread. Why are you even here posting if everything works just great with your 5970? The way you try to blame the drivers and hardware in this case makes me suspect you're on "the other side" of this problem...
It seems to me you don't quite understand just exactly how unstable and unpredictable AFR actually is. There's not a single graphic engine that works 100% properly with it, even if you use AFR compatibility mode.
You can't change the way a graphic engine interacts with an API exclusively for multi-GPU systems. It doesn't work that way. If it was a problem with how the game interacts with the API, then this issue wouldn't be exclusive to multi-GPU systems. It's the job of your drivers to properly divide the workload of the rendering across each GPU. Some games work out of the box, some don't ( like Crysis 2 ). The games that don't work out of the box needs specific profiles for multi-GPU systems to render properly.
There was a similar issue with the original Crysis and AMD CrossFireX users. Up until Cat 8.4 ( IIRC ), enabling CrossFireX would cause Crysis and Crysis Warhead to run SLOWER than if you were to run it with a single graphics card. AMD users cried to Crytek, begging and pleading them to fix it, some of which threatened to boycott the game. Lo and behold, it wasn't until a few months after the release of the final Crysis and Warhead patch that AMD released a driver which fixed the CrossFireX issue for the AMD users.
Again, this goes back to what resolves the issue and what does not. This is called "troubleshooting". Being an apparent multi-GPU owner yourself, I would hope you would know how to diagnose multi-GPU symptoms. As I've stated before, if fixing a multi-GPU issue was done through the driver level, then you know it's a problem with the game's CrossFireX/SLI profile ( or lack there of ). This was already proven, again, with AMD's CAP update.
Sorry that you're still having this issue, chief. But you're barking up the wrong tree. You'll get more response on this issue if you take the time to submit a driver feedback report to your GPU manufacturer. This isn't something Crytek is going to be able to fix for you. You're going to have to wait and do the work to install proper drivers when your manufacturer gets around to releasing them. Sorry if my answer to the problem isn't the answer you're looking for, but that's how the cookie crumbles, m'friend.
You've posted four times on this forum, all in this thread. Why are you even here posting if everything works just great with your 5970? The way you try to blame the drivers and hardware in this case makes me suspect you're on "the other side" of this problem...
It seems to me you don't quite understand just exactly how unstable and unpredictable AFR actually is. There's not a single graphic engine that works 100% properly with it, even if you use AFR compatibility mode.
You can't change the way a graphic engine interacts with an API exclusively for multi-GPU systems. It doesn't work that way. If it was a problem with how the game interacts with the API, then this issue wouldn't be exclusive to multi-GPU systems. It's the job of your drivers to properly divide the workload of the rendering across each GPU. Some games work out of the box, some don't ( like Crysis 2 ). The games that don't work out of the box needs specific profiles for multi-GPU systems to render properly.
There was a similar issue with the original Crysis and AMD CrossFireX users. Up until Cat 8.4 ( IIRC ), enabling CrossFireX would cause Crysis and Crysis Warhead to run SLOWER than if you were to run it with a single graphics card. AMD users cried to Crytek, begging and pleading them to fix it, some of which threatened to boycott the game. Lo and behold, it wasn't until a few months after the release of the final Crysis and Warhead patch that AMD released a driver which fixed the CrossFireX issue for the AMD users.
Again, this goes back to what resolves the issue and what does not. This is called "troubleshooting". Being an apparent multi-GPU owner yourself, I would hope you would know how to diagnose multi-GPU symptoms. As I've stated before, if fixing a multi-GPU issue was done through the driver level, then you know it's a problem with the game's CrossFireX/SLI profile ( or lack there of ). This was already proven, again, with AMD's CAP update.
Sorry that you're still having this issue, chief. But you're barking up the wrong tree. You'll get more response on this issue if you take the time to submit a driver feedback report to your GPU manufacturer. This isn't something Crytek is going to be able to fix for you. You're going to have to wait and do the work to install proper drivers when your manufacturer gets around to releasing them. Sorry if my answer to the problem isn't the answer you're looking for, but that's how the cookie crumbles, m'friend.
-
Emmi Coolahan - Posts: 3335
- Joined: Wed Jan 24, 2007 9:14 pm
» Thu Dec 31, 2009 1:52 pm
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 03 24, 2011 /05:51
Re: Crysis 2 Multi GPU support causes insane flickering. 03 24, 2011 /05:51
Hi there, thanks for posting the vid in the OP, it's handy to have that kind of information.
We are aware of this issue and are working towards resolving it ASAP so that you can enjoy the huge SLI frame rates!
In the mean time, i believe it will work if you disable SLI/CF? Can you confirm this is the case?
Thanks!
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 13, 2011 /09:45
Re: Crysis 2 Multi GPU support causes insane flickering. 04 13, 2011 /09:45
I know i've posted a few times in this thread. We can't please everyone unfortunately because if we repeat a few times a week "hey guys, we're still working on this issue" until the issue is fixed then people get upset that we just repeat ourselves and don't offer anything new. If we say nothing (other than an acknowledgment) and wait for actual new information then after a few days people get upset that we don't post anything.
Either way, someone gets annoyed. I prefer to not post until i have more information, that way you guys are only getting the latest and not just copy/paste. For the record, DX11 development has zero impact on resolving this issue. We realise this issue is effecting a lot of people and hopefully we can resolve it ASAP.
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 14, 2011 /07:00
Re: Crysis 2 Multi GPU support causes insane flickering. 04 14, 2011 /07:00
Hi guys,
We've spoken with the team who are investigating this issue and they're still working on it. There's no ETA for a fix just yet but we'll hopefully have more information on the issue next week. Again, apologies for the delay with fixing this issue as we realise it's affecting many users. Your patience is much appreciated!
Thanks!
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 03 24, 2011 /05:51
Re: Crysis 2 Multi GPU support causes insane flickering. 03 24, 2011 /05:51
Hi there, thanks for posting the vid in the OP, it's handy to have that kind of information.
We are aware of this issue and are working towards resolving it ASAP so that you can enjoy the huge SLI frame rates!
In the mean time, i believe it will work if you disable SLI/CF? Can you confirm this is the case?
Thanks!
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 13, 2011 /09:45
Re: Crysis 2 Multi GPU support causes insane flickering. 04 13, 2011 /09:45
I know i've posted a few times in this thread. We can't please everyone unfortunately because if we repeat a few times a week "hey guys, we're still working on this issue" until the issue is fixed then people get upset that we just repeat ourselves and don't offer anything new. If we say nothing (other than an acknowledgment) and wait for actual new information then after a few days people get upset that we don't post anything.
Either way, someone gets annoyed. I prefer to not post until i have more information, that way you guys are only getting the latest and not just copy/paste. For the record, DX11 development has zero impact on resolving this issue. We realise this issue is effecting a lot of people and hopefully we can resolve it ASAP.
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 14, 2011 /07:00
Re: Crysis 2 Multi GPU support causes insane flickering. 04 14, 2011 /07:00
Hi guys,
We've spoken with the team who are investigating this issue and they're still working on it. There's no ETA for a fix just yet but we'll hopefully have more information on the issue next week. Again, apologies for the delay with fixing this issue as we realise it's affecting many users. Your patience is much appreciated!
Thanks!
-
sarah simon-rogaume - Posts: 3383
- Joined: Thu Mar 15, 2007 4:41 am
» Thu Dec 31, 2009 9:16 am
Last i heard, nVIDIA used AFR 1, AFR 2, and SFR. AMD uses AFR only correct me if i'm wrong.
-
Yama Pi - Posts: 3384
- Joined: Wed Apr 18, 2007 3:51 am
» Thu Dec 31, 2009 6:44 am
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 03 24, 2011 /05:51
Re: Crysis 2 Multi GPU support causes insane flickering. 03 24, 2011 /05:51
Hi there, thanks for posting the vid in the OP, it's handy to have that kind of information.
We are aware of this issue and are working towards resolving it ASAP so that you can enjoy the huge SLI frame rates!
In the mean time, i believe it will work if you disable SLI/CF? Can you confirm this is the case?
Thanks!
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 13, 2011 /09:45
Re: Crysis 2 Multi GPU support causes insane flickering. 04 13, 2011 /09:45
I know i've posted a few times in this thread. We can't please everyone unfortunately because if we repeat a few times a week "hey guys, we're still working on this issue" until the issue is fixed then people get upset that we just repeat ourselves and don't offer anything new. If we say nothing (other than an acknowledgment) and wait for actual new information then after a few days people get upset that we don't post anything.
Either way, someone gets annoyed. I prefer to not post until i have more information, that way you guys are only getting the latest and not just copy/paste. For the record, DX11 development has zero impact on resolving this issue. We realise this issue is effecting a lot of people and hopefully we can resolve it ASAP.
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 14, 2011 /07:00
Re: Crysis 2 Multi GPU support causes insane flickering. 04 14, 2011 /07:00
Hi guys,
We've spoken with the team who are investigating this issue and they're still working on it. There's no ETA for a fix just yet but we'll hopefully have more information on the issue next week. Again, apologies for the delay with fixing this issue as we realise it's affecting many users. Your patience is much appreciated!
Thanks!
Funny that a Crytek rep would conveniently admit fault to an issue that's been proven to be resolved by changing multi-GPU driver profiles and/or updating CAP versions.
Last i heard, nVIDIA used AFR 1, AFR 2, and SFR. AMD uses AFR only correct me if i'm wrong.
AMD uses AFR, Scissor, and Supertile
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 03 24, 2011 /05:51
Re: Crysis 2 Multi GPU support causes insane flickering. 03 24, 2011 /05:51
Hi there, thanks for posting the vid in the OP, it's handy to have that kind of information.
We are aware of this issue and are working towards resolving it ASAP so that you can enjoy the huge SLI frame rates!
In the mean time, i believe it will work if you disable SLI/CF? Can you confirm this is the case?
Thanks!
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 13, 2011 /09:45
Re: Crysis 2 Multi GPU support causes insane flickering. 04 13, 2011 /09:45
I know i've posted a few times in this thread. We can't please everyone unfortunately because if we repeat a few times a week "hey guys, we're still working on this issue" until the issue is fixed then people get upset that we just repeat ourselves and don't offer anything new. If we say nothing (other than an acknowledgment) and wait for actual new information then after a few days people get upset that we don't post anything.
Either way, someone gets annoyed. I prefer to not post until i have more information, that way you guys are only getting the latest and not just copy/paste. For the record, DX11 development has zero impact on resolving this issue. We realise this issue is effecting a lot of people and hopefully we can resolve it ASAP.
Cry-Adam
Joined: 06 11, 2010 /10:09
Posts: 1872
Location: Germany
Post subject: Re: Crysis 2 Multi GPU support causes insane flickering.Posted: 04 14, 2011 /07:00
Re: Crysis 2 Multi GPU support causes insane flickering. 04 14, 2011 /07:00
Hi guys,
We've spoken with the team who are investigating this issue and they're still working on it. There's no ETA for a fix just yet but we'll hopefully have more information on the issue next week. Again, apologies for the delay with fixing this issue as we realise it's affecting many users. Your patience is much appreciated!
Thanks!
Funny that a Crytek rep would conveniently admit fault to an issue that's been proven to be resolved by changing multi-GPU driver profiles and/or updating CAP versions.
Last i heard, nVIDIA used AFR 1, AFR 2, and SFR. AMD uses AFR only correct me if i'm wrong.
AMD uses AFR, Scissor, and Supertile
-
Colton Idonthavealastna - Posts: 3337
- Joined: Sun Sep 30, 2007 2:13 am
» Thu Dec 31, 2009 2:03 pm
Looks to me like you just used a lot of time telling us how CryEngine 3 svcks at communicating with the API (DX 9). FRA is indeed a very "raw" way of using multigpu and that makes it a very easy way to do it...that is if your gfx-engine were set up to do just that. If you, on the other hand, code your engine for DX-9 without multigpu support (read: consoles) then you might find yourself in this heap of sh-t.
You've posted four times on this forum, all in this thread. Why are you even here posting if everything works just great with your 5970? The way you try to blame the drivers and hardware in this case makes me suspect you're on "the other side" of this problem...
It seems to me you don't quite understand just exactly how unstable and unpredictable AFR actually is. There's not a single graphic engine that works 100% properly with it, even if you use AFR compatibility mode.
You can't change the way a graphic engine interacts with an API exclusively for multi-GPU systems. It doesn't work that way. If it was a problem with how the game interacts with the API, then this issue wouldn't be exclusive to multi-GPU systems. It's the job of your drivers to properly divide the workload of the rendering across each GPU. Some games work out of the box, some don't ( like Crysis 2 ). The games that don't work out of the box needs specific profiles for multi-GPU systems to render properly.
There was a similar issue with the original Crysis and AMD CrossFireX users. Up until Cat 8.4 ( IIRC ), enabling CrossFireX would cause Crysis and Crysis Warhead to run SLOWER than if you were to run it with a single graphics card. AMD users cried to Crytek, begging and pleading them to fix it, some of which threatened to boycott the game. Lo and behold, it wasn't until a few months after the release of the final Crysis and Warhead patch that AMD released a driver which fixed the CrossFireX issue for the AMD users.
Again, this goes back to what resolves the issue and what does not. This is called "troubleshooting". Being an apparent multi-GPU owner yourself, I would hope you would know how to diagnose multi-GPU symptoms. As I've stated before, if fixing a multi-GPU issue was done through the driver level, then you know it's a problem with the game's CrossFireX/SLI profile ( or lack there of ). This was already proven, again, with AMD's CAP update.
Sorry that you're still having this issue, chief. But you're barking up the wrong tree. You'll get more response on this issue if you take the time to submit a driver feedback report to your GPU manufacturer. This isn't something Crytek is going to be able to fix for you. You're going to have to wait and do the work to install proper drivers when your manufacturer gets around to releasing them. Sorry if my answer to the problem isn't the answer you're looking for, but that's how the cookie crumbles, m'friend.
Well, Andrew D from AMD who is a catalyst creator goes against your statements in his recent tweets.
With regards to the flickering and Crytek not being able to fix anything:
'Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis … (cont) http://deck.ly/~yZGDR'
He later said:
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
So again, Crytek needs to be involved in solving these issues and increasing CF performance.
And with regards to AFR:
'Basically if texture surfaces are dependent between frames, then AFR (alternate frame rendering) won't work - which if what CF uses'
I'm guessing 'if' is a typo and is meant to be 'is'.
You've posted four times on this forum, all in this thread. Why are you even here posting if everything works just great with your 5970? The way you try to blame the drivers and hardware in this case makes me suspect you're on "the other side" of this problem...
It seems to me you don't quite understand just exactly how unstable and unpredictable AFR actually is. There's not a single graphic engine that works 100% properly with it, even if you use AFR compatibility mode.
You can't change the way a graphic engine interacts with an API exclusively for multi-GPU systems. It doesn't work that way. If it was a problem with how the game interacts with the API, then this issue wouldn't be exclusive to multi-GPU systems. It's the job of your drivers to properly divide the workload of the rendering across each GPU. Some games work out of the box, some don't ( like Crysis 2 ). The games that don't work out of the box needs specific profiles for multi-GPU systems to render properly.
There was a similar issue with the original Crysis and AMD CrossFireX users. Up until Cat 8.4 ( IIRC ), enabling CrossFireX would cause Crysis and Crysis Warhead to run SLOWER than if you were to run it with a single graphics card. AMD users cried to Crytek, begging and pleading them to fix it, some of which threatened to boycott the game. Lo and behold, it wasn't until a few months after the release of the final Crysis and Warhead patch that AMD released a driver which fixed the CrossFireX issue for the AMD users.
Again, this goes back to what resolves the issue and what does not. This is called "troubleshooting". Being an apparent multi-GPU owner yourself, I would hope you would know how to diagnose multi-GPU symptoms. As I've stated before, if fixing a multi-GPU issue was done through the driver level, then you know it's a problem with the game's CrossFireX/SLI profile ( or lack there of ). This was already proven, again, with AMD's CAP update.
Sorry that you're still having this issue, chief. But you're barking up the wrong tree. You'll get more response on this issue if you take the time to submit a driver feedback report to your GPU manufacturer. This isn't something Crytek is going to be able to fix for you. You're going to have to wait and do the work to install proper drivers when your manufacturer gets around to releasing them. Sorry if my answer to the problem isn't the answer you're looking for, but that's how the cookie crumbles, m'friend.
Well, Andrew D from AMD who is a catalyst creator goes against your statements in his recent tweets.
With regards to the flickering and Crytek not being able to fix anything:
'Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis … (cont) http://deck.ly/~yZGDR'
He later said:
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
So again, Crytek needs to be involved in solving these issues and increasing CF performance.
And with regards to AFR:
'Basically if texture surfaces are dependent between frames, then AFR (alternate frame rendering) won't work - which if what CF uses'
I'm guessing 'if' is a typo and is meant to be 'is'.
-
..xX Vin Xx.. - Posts: 3531
- Joined: Sun Jun 18, 2006 6:33 pm
» Thu Dec 31, 2009 2:03 pm
I'm running with two 5850 cards in Crossfire and had flickering. This with the latest game updates and drivers/profiles from AMD. Strangely enough, what fixed it for me was just adjusting the brightness in the game. Just a minor adjustment (either lowering it or making it higher) removed all the flickering. Anybody else experience this?
-
Setal Vara - Posts: 3390
- Joined: Thu Nov 16, 2006 1:24 pm
» Thu Dec 31, 2009 2:32 pm
Well, Andrew D from AMD who is a catalyst creator goes against your statements in his recent tweets.
With regards to the flickering and Crytek not being able to fix anything:
'Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis … (cont) http://deck.ly/~yZGDR'
He later said:
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
So again, Crytek needs to be involved in solving these issues and increasing CF performance.
And with regards to AFR:
'Basically if texture surfaces are dependent between frames, then AFR (alternate frame rendering) won't work - which if what CF uses'
I'm guessing 'if' is a typo and is meant to be 'is'.
You say that Andrew is going against my statements, which is well and fine, but he has some contradictory elements in his own tweets.
Continuing from the tweet page you linked above
Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis 2 for example - higher performance is possible today with a different profile, but causes flickering
The bold statement above contradicts the following statement below.
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
Furthermore, the BioShock CF profile does not cause flickering. This, again, contradicts his own statements about changing profiles.
I love reps who can't keep their stories straight.
With regards to the flickering and Crytek not being able to fix anything:
'Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis … (cont) http://deck.ly/~yZGDR'
He later said:
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
So again, Crytek needs to be involved in solving these issues and increasing CF performance.
And with regards to AFR:
'Basically if texture surfaces are dependent between frames, then AFR (alternate frame rendering) won't work - which if what CF uses'
I'm guessing 'if' is a typo and is meant to be 'is'.
You say that Andrew is going against my statements, which is well and fine, but he has some contradictory elements in his own tweets.
Continuing from the tweet page you linked above
Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis 2 for example - higher performance is possible today with a different profile, but causes flickering
The bold statement above contradicts the following statement below.
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
Furthermore, the BioShock CF profile does not cause flickering. This, again, contradicts his own statements about changing profiles.
I love reps who can't keep their stories straight.
-
Angela - Posts: 3492
- Joined: Mon Mar 05, 2007 8:33 am
» Thu Dec 31, 2009 2:59 pm
Since the AFR mode is the most efficient we recommend aiming for your APPLICATION to work well with this mode. To achieve this you should try to reduce inter-frame dependencies. A common cause of an inter-frame dependency is when the result in a render target is reused in the next frame. This can be because of light-trail or motion blur effects or simply that the APPLICATION as an optimization doesn’t update the render target every frame.
http://developer.amd.com/media/gpu_assets/Programming_for_CrossFire.pdf
Please reply quickly, I'm done laughing from your previous posts already.
lavans6879 just got...
Maximum OWNED !!!
http://developer.amd.com/media/gpu_assets/Programming_for_CrossFire.pdf
Please reply quickly, I'm done laughing from your previous posts already.
lavans6879 just got...
Maximum OWNED !!!
-
Andy durkan - Posts: 3459
- Joined: Fri Aug 03, 2007 3:05 pm
» Thu Dec 31, 2009 5:23 am
Since the AFR mode is the most efficient we recommend aiming for your APPLICATION to work well with this mode. To achieve this you should try to reduce inter-frame dependencies. A common cause of an inter-frame dependency is when the result in a render target is reused in the next frame. This can be because of light-trail or motion blur effects or simply that the APPLICATION as an optimization doesn’t update the render target every frame.
http://developer.amd.com/media/gpu_assets/Programming_for_CrossFire.pdf
Please reply quickly, I'm done laughing from your previous posts already.
lavans6879 just got...
Maximum OWNED !!!
Again?
How many times does it need to be said that the APP can be fixed by changing the driver profile? How many times does someone need to mention that if changing a driver setting resolves the issue, that it's not a problem with the game?
http://www.google.com/#sclient=psy&hl=en&safe=off&source=hp&q=crysis+2+bioshock+crossfire&aq=f&aqi=&aql=&oq=&pbx=1&bav=on.2,or.r_gc.r_pw.&fp=a316b5cdb3fe9040
I don't understand why that's so difficult for you to understand. If you can resolve the issue by alternating drivers ( as seen in the post about the CAPs ), then do you honestly think it's a problem with the game? I would like to hear your answer on this, as you seem to be so knowledgeable about multi-GPU systems, yet back your statements with out of context quotes.
Furthermore, try setting a game that works with CF to AFR. You'll find that the results are different than if you were to leave them to driver default.
http://developer.amd.com/media/gpu_assets/Programming_for_CrossFire.pdf
Please reply quickly, I'm done laughing from your previous posts already.
lavans6879 just got...
Maximum OWNED !!!
Again?
How many times does it need to be said that the APP can be fixed by changing the driver profile? How many times does someone need to mention that if changing a driver setting resolves the issue, that it's not a problem with the game?
http://www.google.com/#sclient=psy&hl=en&safe=off&source=hp&q=crysis+2+bioshock+crossfire&aq=f&aqi=&aql=&oq=&pbx=1&bav=on.2,or.r_gc.r_pw.&fp=a316b5cdb3fe9040
I don't understand why that's so difficult for you to understand. If you can resolve the issue by alternating drivers ( as seen in the post about the CAPs ), then do you honestly think it's a problem with the game? I would like to hear your answer on this, as you seem to be so knowledgeable about multi-GPU systems, yet back your statements with out of context quotes.
Furthermore, try setting a game that works with CF to AFR. You'll find that the results are different than if you were to leave them to driver default.
-
Jesus Sanchez - Posts: 3455
- Joined: Sun Oct 21, 2007 11:15 am
» Thu Dec 31, 2009 2:37 am
Well, Andrew D from AMD who is a catalyst creator goes against your statements in his recent tweets.
With regards to the flickering and Crytek not being able to fix anything:
'Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis … (cont) http://deck.ly/~yZGDR'
He later said:
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
So again, Crytek needs to be involved in solving these issues and increasing CF performance.
And with regards to AFR:
'Basically if texture surfaces are dependent between frames, then AFR (alternate frame rendering) won't work - which if what CF uses'
I'm guessing 'if' is a typo and is meant to be 'is'.
You say that Andrew is going against my statements, which is well and fine, but he has some contradictory elements in his own tweets.
Continuing from the tweet page you linked above
Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis 2 for example - higher performance is possible today with a different profile, but causes flickering
The bold statement above contradicts the following statement below.
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
Furthermore, the BioShock CF profile does not cause flickering. This, again, contradicts his own statements about changing profiles.
I love reps who can't keep their stories straight.
How exactly does he contradict himself? He is saying that higher performing profiles causes flickering. To stop flickering, and therefore increase performance, the app (i.e. Crysis 2) needs to be updated.
He then goes onto to say that for Crysis 2 to have increased performance, it needs updating. I don't see the contradiction here.
Crysis 2 isn't AFR-friendly and using high performing profiles causes flickering. To stop flickering, Crysis 2 needs updating.
Also, although Bioshock doesn't cause flickering, it's performance is well below what is should be. Some parts of the game just don't scale at all.
And the flickering still isn't completely fixed. It still see flickering when using nano vision.
I'm afraid we're going to have to agree to disagree on this one. But I'm going with the guy who actually writes the Catalyst software.
With regards to the flickering and Crytek not being able to fix anything:
'Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis … (cont) http://deck.ly/~yZGDR'
He later said:
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
So again, Crytek needs to be involved in solving these issues and increasing CF performance.
And with regards to AFR:
'Basically if texture surfaces are dependent between frames, then AFR (alternate frame rendering) won't work - which if what CF uses'
I'm guessing 'if' is a typo and is meant to be 'is'.
You say that Andrew is going against my statements, which is well and fine, but he has some contradictory elements in his own tweets.
Continuing from the tweet page you linked above
Any app that you see flickering in with CF is because the app doesn't work well with AFR - Shift 2, Crysis 2 for example - higher performance is possible today with a different profile, but causes flickering
The bold statement above contradicts the following statement below.
'From a CAP perspective for Shift 2 and Crysis 2 - nothing more can be done for CF scaling unless the apps are updated...'
Furthermore, the BioShock CF profile does not cause flickering. This, again, contradicts his own statements about changing profiles.
I love reps who can't keep their stories straight.
How exactly does he contradict himself? He is saying that higher performing profiles causes flickering. To stop flickering, and therefore increase performance, the app (i.e. Crysis 2) needs to be updated.
He then goes onto to say that for Crysis 2 to have increased performance, it needs updating. I don't see the contradiction here.
Crysis 2 isn't AFR-friendly and using high performing profiles causes flickering. To stop flickering, Crysis 2 needs updating.
Also, although Bioshock doesn't cause flickering, it's performance is well below what is should be. Some parts of the game just don't scale at all.
And the flickering still isn't completely fixed. It still see flickering when using nano vision.
I'm afraid we're going to have to agree to disagree on this one. But I'm going with the guy who actually writes the Catalyst software.
-
Richard Dixon - Posts: 3461
- Joined: Thu Jun 07, 2007 1:29 pm
» Thu Dec 31, 2009 2:24 pm
Note to all ^^: Stop feeding the troll (aka lavans6879)
http://scientopia.org/blogs/voltagegate/files/2010/12/Trollface-Coolface-Problem-Know-Your-Meme1.png
http://scientopia.org/blogs/voltagegate/files/2010/12/Trollface-Coolface-Problem-Know-Your-Meme1.png
-
Misty lt - Posts: 3400
- Joined: Mon Dec 25, 2006 10:06 am
» Thu Dec 31, 2009 3:12 pm
How exactly does he contradict himself? He is saying that higher performing profiles causes flickering. To stop flickering, and therefore increase performance, the app (i.e. Crysis 2) needs to be updated.
He then goes onto to say that for Crysis 2 to have increased performance, it needs updating. I don't see the contradiction here.
Crysis 2 isn't AFR-friendly and using high performing profiles causes flickering. To stop flickering, Crysis 2 needs updating.
Also, although Bioshock doesn't cause flickering, it's performance is well below what is should be. Some parts of the game just don't scale at all.
And the flickering still isn't completely fixed. It still see flickering when using nano vision.
I'm afraid we're going to have to agree to disagree on this one. But I'm going with the guy who actually writes the Catalyst software.
Simple, he contradicts himself by saying that you can't get higher CF performance unless Crysis 2 is updated, but then turns around and says that you can by using different CF profiles.
Furthermore, he states that Crysis 2 will continue to flicker regardless of what is done, short of updating Crysis 2. This is also incorrect because the Bioshock CAP does not cause flickering at the cost of scaling, and AMD's CAP resolves the flickering.
Note to all ^^: Stop feeding the troll (aka lavans6879)
http://scientopia.org/blogs/voltagegate/files/2010/12/Trollface-Coolface-Problem-Know-Your-Meme1.png
How am I a troll? By suggesting to people to go with what's proven to work and update their drivers, rather than waiting for a magical fix from Crytek?
He then goes onto to say that for Crysis 2 to have increased performance, it needs updating. I don't see the contradiction here.
Crysis 2 isn't AFR-friendly and using high performing profiles causes flickering. To stop flickering, Crysis 2 needs updating.
Also, although Bioshock doesn't cause flickering, it's performance is well below what is should be. Some parts of the game just don't scale at all.
And the flickering still isn't completely fixed. It still see flickering when using nano vision.
I'm afraid we're going to have to agree to disagree on this one. But I'm going with the guy who actually writes the Catalyst software.
Simple, he contradicts himself by saying that you can't get higher CF performance unless Crysis 2 is updated, but then turns around and says that you can by using different CF profiles.
Furthermore, he states that Crysis 2 will continue to flicker regardless of what is done, short of updating Crysis 2. This is also incorrect because the Bioshock CAP does not cause flickering at the cost of scaling, and AMD's CAP resolves the flickering.
Note to all ^^: Stop feeding the troll (aka lavans6879)
http://scientopia.org/blogs/voltagegate/files/2010/12/Trollface-Coolface-Problem-Know-Your-Meme1.png
How am I a troll? By suggesting to people to go with what's proven to work and update their drivers, rather than waiting for a magical fix from Crytek?
-
Brooks Hardison - Posts: 3410
- Joined: Fri Sep 07, 2007 3:14 am