AMD 6970 Crysis 3 artifacts.

MTDEW

Diamond Member
Oct 31, 1999
4,284
37
91
Using my 6970's in Crysis 3, i get artifacts if I set Object detail to Very High.
Its that way no matter what drivers Ive ever tried with my 6970's.
SEE here for a thread and pics. (notice Psycho especially, at very high object detail, his character model just freaks out!)
MYCrysis Thread
More here

Pic of Psycho corruption

Yet my other rig with 7950's has never had the issue.

It doesnt matter if i run single card or x-fired, the 6xxx cards get artifacts if object detail is set to very high.
Selecting just high solves the issue.

So my question is, can anyone with an AMD 6xxx series card run Crysis 3 at very high (especially object detail) with no issues?

I would have thought AMD would have fixed this for the 6xxx series owners by now.
Its not a very good feeling thinking that proper driver support for my 7xxx cards may just be an "afterthought" also when AMD launches their next GPU's.
I mean the 6xxx cards aren't that old, those owners still deserve proper driver support IMO.
 
Last edited:

Carfax83

Diamond Member
Nov 1, 2010
6,841
1,536
136
Doesn't the AMD 6000 series have weak tessellation capabilities relatively speaking, to the 7000 series? I know that setting object detail to very high enables tessellation. Perhaps the tessellation units are being overwhelmed, but I don't think that should display any corruption like what you're seeing.

Yeah, it's probably just due to insufficient driver optimization. Isn't there an AMD optimized setting in the drivers for tessellation?
 

MTDEW

Diamond Member
Oct 31, 1999
4,284
37
91
Agreed, although having weaker tessellation, it still shouldn't cause artifacts or graphics corruption like that.
But yes, its definitely tessellation that isn't optimized correctly for the 6xxx and 5xxx series cards in the drivers for Crysis 3.

I did try changing the tessellation settings in CCC, the default is AMD optimized setting and then tried all the other settings available and although it does improve performance lowering the settings, it doesn't fix the corruption issue.

I know if i didn't own a pair of 7950's in my other rig, I would be a lot more disappointed that AMD hasn't even addressed the issue with the 6xxx series cards.
From other threads, it seems the 5xxx series cards have the same issue also.

As i said above, it doesn't help my confidence in my 7950's being properly supported in the future.
 

Jacky60

Golden Member
Jan 3, 2010
1,123
0
0
I had same problem, fiddled with settings and Pyscho was back to normal and it looked better. It was annoying and I can't remember how I sorted it. Having said that a 5870 would barely be capable of handling Crysis3 surely so I can understand it not being a priority.
 
Last edited:

MTDEW

Diamond Member
Oct 31, 1999
4,284
37
91
I had same problem, fiddled with settings and Pyscho was back to normal and it looked better. It was annoying and I can't remember how I sorted it. Having said that a 5870 would barely be capable of handling Crysis3 surely so I can understand it not being a priority.
Yeah, but your rig in your sig is more than capable of handling Crysis 3.
Do you know if you have the issue on your 6990's?
I have yet to see anyone with a 6xxx series card on any forum not have the issue on very high settings.

EDIT: I wonder what would happen if i used an older driver that was before the 7xxx series cards were released.
Anyone know for sure what driver version would be old enough to be before the 7xxx series launched?
(my memory sucks, ive updated drivers too many times since then to remember)
ANSWER: Nope, old drivers don't fix the issue either.
There goes my theory of GCN optimizations in the drivers messing up earlier GPU's.
 
Last edited:

Carfax83

Diamond Member
Nov 1, 2010
6,841
1,536
136
Yeah man, it looks like a driver problem. When multiple people are experiencing the same problem with the same hardware and software settings, it's obvious.

I think you and any other 6000 series owners should petition Catalyst maker and have him look into the problem for you, because it can only be fixed on AMD's end.