Artifacts on Crysis 3 (A LOT)

Hi. As you can see here I'm getting a lot of artifacts on Crysis 3. You can clearly see them on Psycho, but I'm getting other random artifacts on the screen.

My specs: Radeon HD6990 | core i7 920 @4.0GHz (Watercooled, very stable and tested) | OCZ Vertex 4 120GB |

I'm playing the game at 1920x1080, with 13.2B5 and 13.2B6 drivers (I tested both, uninstalling and cleaning with driver sweeper). I only get that huge amount of artifacts if I play on VERY HIGH. If I change to HIGH, there are still a few artifacts, but a lot less.

I can play any other game at full settings without any issue, I never had artifacts before (Battlefield 3, Borderlands 2, Starcraft II...etc).

Is something wrong with my card? Something wrong with the drivers? Something wrong with the game?

Thanks in advance.

 

I was getting those same artifacts with the object detail set to very high, set it to high and not only does it almost double ur frame rate but all the artifacts go as well...

 

Yeah, maybe I'll play on HIGH anyway, but I just want to know what is causing these artifacts. I want to know if it is a problem that a new patch or driver will fix, or if it's something related to my card, because I didn't see anywhere someone with the same problem as me

BTW, on HIGH I get rid of these artifacts (the ones you see on Psycho), but the helicopters flying, for example, have some kind of black square around them. I cannot screen the black square because it flickers and it's too difficult to catch on a screen.

Somebody else experiencing these artifacts?

 

Hi Jeffarese,

I have exactly the same problem as you are describing. Mainly artifacts all over Psycho's body and massive artifacts flying around the screen, long trails of them. Only when I drop advanced settings 'object' from 'very high' to 'high' do they disappear. It's also worth mentioning I practically have the same set up as you - i7 920 (stable OC at 4ghz) and I have 2x6950 (flashed). I'm using the 13.2 beta 6 driver, which does sometimes crash when trying to start up game (never in game). Also crossfire does not always work in game (I have to toggle to desktop from game and back again to make work). Anyway you are not the only one with this problem. Let me know if you find a fix. Thanks.

 

Playing an beta unfinished game with unfinished beta driver is the cause of garbage on screen.

 

True.

 

Perhaps it's a new nanosuit ability

 

I loled hard.

I hope that some new patch or driver can fix the artifacts then. Thanks

 

Thanks for sharing your experience. It's nice to see I am not alone haha.

 

No problem. Do you like the game so far?

 

Well, I love the jungle-like destructed cities and the nanosuit. I know it's not the best game, but I really enjoy it. What's your thought?

 

Well apart from just losing all my progress (somehow Origin does not recognise my saved games) I think it's awesome!! However the issue I have is that the gun models are way to close - so I'm using Cvars to change some of the settings but does not seem to change r_drawnearfov. Also gonna have to restart the whole game on post human warrior!

 

If I set Objects to very high i get the same problems, have to run it on High just to get rid of the errors.
I'm running the game at 2560x1400

 

the tessellation is bugged, enter this command in the console and it will fix it.
e_TessellationMaxDistance 0

 

So when will AMD release their new drivers? BETA 6 has a lot of problems.

I get the same artifacts by the way.

 

Your command solved the big artifacts on Psycho, but I'm still having the flickering squares around the helicopters at begining of chapter 3. Anybody else?

 

Yeah, the command also solved the problems for me.
Still having small blinking square boxes on screen though

 

thank you. had the same thing. now the artifacts on psycho is gone.

but what it does. is disabling tessellation altogether right?
so i still want this effect. is the problem only at psycho model, and we need to wait for them to fix the buggy model (and can use it in levels that psycho does not appear)? or cant we use the tessellation effect at all?

 

I know you don't want to hear this, but it sounds very much like when my 6950 started dieing.

 

Well it seems the problem is solved.
i changed the "tessellation mod" from the catalyst to "AMD OPTIMSED"
and entered e_TessellationMaxDistance 1 and psycho isnt buggy anymore.
(btw i updated it to 13.2 beta).

please try it and let me know if its works for you.