Can't play with anything above "very high" (black spots)

Post » Tue Dec 13, 2011 5:38 pm

Basically, if I have anything in the advanced options menu set to extreme or ultra, I get black spots all over the place and a constant flickering which corresponds to camera movement.

Here is a video of the problem as it manifests itself on my computer.

Everything I know about this glitch (Update):

1. It occurs regardless if I start a new game, resume a game, or replay a level

2. It can be fixed (everything can be ran on ultra) by following these steps after the game has launched (actually starting gameplay is not necessary prior to these steps):
- In advanced options, change the level of post processing, hit apply
- Change the level of post processing back to where you had it, hit apply

You can then start a new game, resume a game, or replay a level without the black spots and flickering everywhere. At least, this works for me. The above steps also work if you do it with motion blur instead (i.e. turn off motion blur, apply, turn motion blur back on, apply)

3. The problem does not occur if everything is set to very high

4. The problem seemingly occurs if anything in the advanced graphics menu is set above very high (extreme or ultra). I say seemingly because I have only tested it fully (and independently) with "game effects" and "objects" thus far.

5. The problem does not seem to be post processing specific

6. The problem does not to be specific to "extreme", post processing or otherwise. It seems to be when anything in the advanced graphics menu is set to either extreme or ultra. Like I said earlier, I have only tested a couple of the options in the advanced menu, but so far it is following the same trend.

7. It's really annoying

System Specs:
Intel i7 930 @2.8 ghz
2x EVGA Nvidia GTX 470 (SLI)
12gb ddr2 ram

Also, I'd like to note that depth of field does not work when set on ultra. That's why I like to put everything on ultra, except post processing which is on extreme, presumably until this issue is fixed as well.

User avatar
Jordan Fletcher
 
Posts: 3355
Joined: Tue Oct 16, 2007 5:27 am

Post » Tue Dec 13, 2011 4:37 am

Maybe your graphics card doesn't support DX11? I bet it has to do something with the DX11 upgrade...
User avatar
Claudz
 
Posts: 3484
Joined: Thu Sep 07, 2006 5:33 am

Post » Tue Dec 13, 2011 2:52 am

Maybe your graphics card doesn't support DX11? I bet it has to do something with the DX11 upgrade...
It definitely does (support DX11)
User avatar
Queen Bitch
 
Posts: 3312
Joined: Fri Dec 15, 2006 2:43 pm

Post » Tue Dec 13, 2011 6:04 pm

This happens with my 2x460s since 1.9... I disabled/enabled motion blur in game. If that fixes it for you, try these two contradictory lines in game.cfg :

r_MotionBlur = 1
r_MotionBlur = 0

I like mine off. You could reverse these lines if you prefer. This works groovy for me, and mine looked just like yours.
User avatar
Naomi Ward
 
Posts: 3450
Joined: Fri Jul 14, 2006 8:37 pm

Post » Tue Dec 13, 2011 4:57 am

This happens with my 2x460s since 1.9... I disabled/enabled motion blur in game. If that fixes it for you, try these two contradictory lines in game.cfg :

r_MotionBlur = 1
r_MotionBlur = 0

I like mine off. You could reverse these lines if you prefer. This works groovy for me, and mine looked just like yours.
I tried this, but it didn't work.

I created autoexec.cfg in the Crysis 2 main directory and reversed and added those lines.

I thought that I would've already had an autoexec.cfg since I have changed the advanced graphics options? Where are those stored?

And, any idea why this isn't working for me? I noticed that disabling/enabling the motion blur fixes the problem in addition to changing the level of post-processing. But for some reason it doesn't seem to work in the autoexec.cfg.
User avatar
kiss my weasel
 
Posts: 3221
Joined: Tue Feb 20, 2007 9:08 am

Post » Tue Dec 13, 2011 10:31 am

Simple fix, turn the general settings to default high, then choose your advanced settings, then choose default extreme, then go to advance once again, the spots should go away.
User avatar
quinnnn
 
Posts: 3503
Joined: Sat Mar 03, 2007 1:11 pm

Post » Tue Dec 13, 2011 6:26 pm

Simple fix, turn the general settings to default high, then choose your advanced settings, then choose default extreme, then go to advance once again, the spots should go away.
This did not work for me. I also tried changing the post processing in the autoexec, like this:

sys_spec_postprocessing 2
sys_spec_postprocessing 3

But that did not work either. Although the autoexec is changing the post processing level, it doesn't seem that it matters unless I manually change it once the game has started. And I don't even have to have loaded a level yet, I can literally double click the Crysis 2 shortcut, go into advanced graphics, change PP to very high, apply, change PP to extreme, apply, and then click "resume game", and I'm good to go.

No matter what I try I can't just hit "resume game". I have to monkey around in the options menu first. Does anyone else know anything else to try? I really thought that the autoexec thing would've worked, and I don't really understand why it's not, because I know that it is changing the post processing..
User avatar
casey macmillan
 
Posts: 3474
Joined: Fri Feb 09, 2007 7:37 pm

Post » Tue Dec 13, 2011 2:57 pm

And, any idea why this isn't working for me? I noticed that disabling/enabling the motion blur fixes the problem in addition to changing the level of post-processing. But for some reason it doesn't seem to work in the autoexec.cfg.It matters when during game load the commands are applied. Look in ...\Saved Games\Crysis2 for game.cfg and add the two lines there. It'll work.

Note, however, that game.cfg will be automatically overwritten by the game when you mess with graphics options. The solution is to mark this game.cfg read-only. Many cvars that wont work in atoexec will work here. Changing that file attribute is a PITA, but -- worth it.
User avatar
Richus Dude
 
Posts: 3381
Joined: Fri Jun 16, 2006 1:17 am

Post » Tue Dec 13, 2011 11:19 am

And, any idea why this isn't working for me? I noticed that disabling/enabling the motion blur fixes the problem in addition to changing the level of post-processing. But for some reason it doesn't seem to work in the autoexec.cfg.It matters when during game load the commands are applied. Look in ...\Saved Games\Crysis2 for game.cfg and add the two lines there. It'll work.

Note, however, that game.cfg will be automatically overwritten by the game when you mess with graphics options. The solution is to mark this game.cfg read-only. Many cvars that wont work in atoexec will work here. Changing that file attribute is a PITA, but -- worth it.
Do you think you could go in a little bit more detail about how to get this working? Because it's still not for me.

I added those two lines in game.cfg, started crysis, and the problem was still there. I didn't change any graphics options and after I closed crysis and checked the game.cfg file, the two additional lines were still there. I don't know how to make it so crysis won't overwrite the file, but it seems to leave the file alone if you don't change any graphics options, like you said.

So what exactly am I doing wrong here? When do the instructions in game.cfg get carried out? Because I can do your fix before I even start the actual gameplay and it will work.. Just doesn't seem to be working from game.cfg for some reason..
User avatar
remi lasisi
 
Posts: 3307
Joined: Sun Jul 02, 2006 2:26 pm

Post » Tue Dec 13, 2011 4:22 am

1. Confirm you are using game.cfg from C:\Users\<username>\Saved Games\Crysis2 ...(win7)
2. Confirm the two r_MotionBlur lines added at the bottom, turning it off, then on (just cuz I havent tried it the other way and cant say it works for sure)
3. Right click the file and select properties then tick the read only box.
4. Start the game...

It sounds like you got it right though. If this doesnt work, I'm out of experience. Dang. I thought it was a done deal. Good luck!
User avatar
Queen of Spades
 
Posts: 3383
Joined: Fri Dec 08, 2006 12:06 pm

Post » Tue Dec 13, 2011 6:36 pm

1. Confirm you are using game.cfg from C:\Users\<username>\Saved Games\Crysis2 ...(win7)
2. Confirm the two r_MotionBlur lines added at the bottom, turning it off, then on (just cuz I havent tried it the other way and cant say it works for sure)
3. Right click the file and select properties then tick the read only box.
4. Start the game...

It sounds like you got it right though. If this doesnt work, I'm out of experience. Dang. I thought it was a done deal. Good luck!
Thanks for the help man. I really thought that idea would've worked as well, but it looks like it doesn't for whatever reason.

Do you know if this is a crytek or nividia problem, and if anything is being done about it?

Also, I found that setting my sli render mode to "force alternate frame rendering 1" fixed the problem, but I lose about 5-6 fps on average.. I don't really like that tradeoff. It's weird because it's so easy to fix.. But it's annoying to have to do it all the time.
User avatar
Rachael
 
Posts: 3412
Joined: Sat Feb 17, 2007 2:10 pm

Post » Tue Dec 13, 2011 5:51 am

this is tedious but have u try completely uninstalling and reinstalling the game?
User avatar
KIng James
 
Posts: 3499
Joined: Wed Sep 26, 2007 2:54 pm

Post » Tue Dec 13, 2011 12:31 pm

also a good thing to try (that always worked for me when this happens) is to go to advanced graphics and change your motion blur setting. if it's a low(most likely to cause problem) change it to medium, apply, then set it to low again if u wish. be sure to do this in game while rendering(aka playing, not in menu)
User avatar
james tait
 
Posts: 3385
Joined: Fri Jun 22, 2007 6:26 pm

Post » Tue Dec 13, 2011 2:33 pm

This reminds me of a flash light bug I get in Metro 2033. Whenever my flash light (I miss spelled that as flesh light lol) is on and I look up I can see a clear circle that moves around on the right hand side.
User avatar
Misty lt
 
Posts: 3400
Joined: Mon Dec 25, 2006 10:06 am

Post » Tue Dec 13, 2011 6:19 am

also a good thing to try (that always worked for me when this happens) is to go to advanced graphics and change your motion blur setting. if it's a low(most likely to cause problem) change it to medium, apply, then set it to low again if u wish. be sure to do this in game while rendering(aka playing, not in menu)
Yes, in fact that is in my original post as one of the things that I discovered would fix the problem (as another user pointed out to me). Actually, I can do that with pretty much anything in addition to the motion blur. I just have to change something, hit apply, and change it back, hit apply, and the problem is gone. Easy fix, but it's still annoying.

And yes, I did uninstall and reinstall everything. Am I the only one having this issue, or is this still something that other players are other trouble with as well? Is there any hope that something will be done to correct this, and also the fact that depth of field does not work when post processing is on ultra? And, any other ideas?
User avatar
Chris Johnston
 
Posts: 3392
Joined: Fri Jul 07, 2006 12:40 pm

Post » Tue Dec 13, 2011 3:00 pm

Well, this fix also seemed to work for me on this problem (before I found the other solution)

r_MotionBlur = 1
r_MotionBlurShutterSpeed = 0.0001


In game.cfg, as before. This one makes your gun blurry, among other things, but it might be worth a test.
User avatar
Siobhan Wallis-McRobert
 
Posts: 3449
Joined: Fri Dec 08, 2006 4:09 pm

Post » Tue Dec 13, 2011 6:29 am

It's almost like all it takes is some sort of re-initialization of the renderer (or whatever it's called) to fix the problem. It's like it doesn't really matter what you do, because anything you change in the graphics menu "resets" it, or something to that effect. I don't know if this is true or not, just speculating. That's what makes me think that this must be an easy fix.

Thanks Ch4nce for the suggestion, I'll try it out. But I don't want to play with a blurry gun lol. Hopefully a "real" solution will present itself soon.. I know that the dx11 patch was introduced only recently, but it'd be nice to have some sort of date or something from crytek that would tell us when it will be fixed. And honestly, I'm surprised there aren't more threads about this. I would think these would be popping up 24/7 if other users were experiencing the same thing..

Also, I noticed that changing my sli rendering mode would fix the problem, but I lose quite a few fps when I'm not using the "nvidia recommended" setting. I ran some fps benchmarks, but they were unnecessary because I could see and feel just how much of a difference it made. I'm not going to cripple my fps and ability to play the game just to remove the shadows..
User avatar
jenny goodwin
 
Posts: 3461
Joined: Wed Sep 13, 2006 4:57 am

Post » Tue Dec 13, 2011 6:50 am

You've tried different drivers? I mean, this is a crysis problem, but different driver versions deal with it differently... I left the 2.80 beta drivers for 275.50 for a different reason, but it seems to me that this problem resurfaced with the 2.80 driver beta....
User avatar
gandalf
 
Posts: 3400
Joined: Wed Feb 21, 2007 6:57 pm

Post » Tue Dec 13, 2011 8:24 am

You've tried different drivers? I mean, this is a crysis problem, but different driver versions deal with it differently... I left the 2.80 beta drivers for 275.50 for a different reason, but it seems to me that this problem resurfaced with the 2.80 driver beta....

Right now I'm running the 275.33 driver for my gtx 470s, which I think is the most current driver.

On a different note, have you ever noticed the little elevation marks randomly disappearing when looking down the sights of the scarab? You know the little white marks that are around the sights.. well they just disappear whenever I look in certain directions.. it's really odd. Seems to do it no matter what I have the graphics set to.
User avatar
Miss Hayley
 
Posts: 3414
Joined: Tue Jun 27, 2006 2:31 am

Post » Tue Dec 13, 2011 2:51 pm

So what's the story? Is this something that either crytek or nvidia is going to fix, or am I the only one still having these problems?
User avatar
Neil
 
Posts: 3357
Joined: Sat Jul 14, 2007 5:08 am

Post » Tue Dec 13, 2011 6:33 am

I guess this is the answer to my question:
1. NVidia graphic problems
- 1. Crysis2 may flicker on the SLI-enabled configurations having a GPU dedicated to PhysX (no matter if PhysX is enabled in NVIDIA control panel)
- 2. Scenes with rain layer show weapon corruption (dx9-only)
Status:
i. NVidia is aware of the issues and currently working on a new driver update
My only question now is, when is this driver update expected to release? I really want to play Crysis 2 :(
User avatar
Amy Gibson
 
Posts: 3540
Joined: Wed Oct 04, 2006 2:11 pm


Return to Crysis