Crysis & 1.1 Patch = very buggy.

Anyone able to play it without any problems? Anytime the assualt scope is attached the screen becomes all white or clear. Its hard to explain but heres an example with a screenshot.

 

Nobody else gets this problem? I went to EA's forums for crysis and there was a thread with a user with the EXACT problem.

 

YES. I think the game was less buggier without the patch. I got that, in addition, I got a bug where sometimes, my weapon does not appear. So when they do not appear, the game thinks that I have no weapon, so I can't fire (which got me pissed off and made me decide to restart the game and beat it using only my fists )
I also get these bugs where if I were to kill some enemies, and then save, and when I load the game after I get killed, the dead enemies are "standing up" but their legs are beneath the ground.

I've had no bug issues with the game when it was not patched. Bugs only came when the game either was played using custom config files or patched.

 

Whats even more strange is that i uninstalled it and reinstalled it without the patch and its STILL doing that!!!!!!! (Rips hair out)

 

As you can see, the bugs you find is more of a infestation rather than a random encounter.

 

Its frustrating why its doing that. I uninstalled it again and am running spyware, virus checks and doing disk optimazations and will then reinstall it. I made sure all trace of crysis were gone so when i install it hopefully itll be fixed. Im not going to load my save games because maybe its in there so im going to have to play it again. Reason its annoying is becase i beat the game and it worked fine. And i want to install the patch because i do see a big gain in performance for me.

 

Try different drivers. www.laptopvideo2go.com anything above 169.04 should help out. Also did you delete the registry value and the crytek folder after you uninstalled? You should definately remove all traces of crysis, then run ccleaner to get rid of the registry values, etc.

 

I did all of that EXCEPT clear it from the registry, DAMN hopefully it wont do it again. If not im going to try that and reinstall it once again.

 

alright well its doing it again so i decided to play with the settings. I figured out its an issue with the AA. I had it at 2x. I turned it off and it worked fine and then i put it at 4x and the rest of them and it worked fine. Seems to be a bug with the 2x AA.