Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I think I'm done with this bugfest, but at least it's given me some giggles. I hope that Warhead and Crysis 2 aren't so bad.
I'm reasonably certain this is an issue with newer systems when running the game with either the 64-bit executable, or in DX10 mode. I can't remember which one specifically causes it, but I've never once had any of this happen under 32-bit Windows XP.
Obviously it's 2015 so that's probably not an option for you :P
I'd recommend you try running the game with the -dx9 command option, and if you're using the 64-bit exe, try the 32-bit, and vice versa. (you may have to scour a 64-bit exe off the net somewhere)
Then... and this is important... restart the chapter. Don't just reload your save. Once this nonsense happens, it corrupts your savegame and it will never go away unless you just restart the chapter from scratch.
Good luck.