It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hello,

Crysis goes back to the desktop as I opened it. I couldn't start the game. I got the Origin version. I read in the forums that you are troubled. I heard that the GOG version was running smoothly and I went and bought the GOG version, but again it was disappointing. The 32-bit version and the 64-bit version do not both open. I tried everything written on the internet and could not open it again. Crysis-2 and 3 are running smoothly. The only problem is that Crysis is not working. Does anyone have any unusual advice? or I'll ask for a refund.
My system is,

AMD Ryzen 2600X
32GB Ram
GeForce RTX 2080
Windows 10 x64

Thanks...
--
Post edited June 07, 2019 by Themken
avatar
hasskabal: Hello,

Crysis goes back to the desktop as I opened it. I couldn't start the game. I got the Origin version. I read in the forums that you are troubled. I heard that the GOG version was running smoothly and I went and bought the GOG version, but again it was disappointing. The 32-bit version and the 64-bit version do not both open. I tried everything written on the internet and could not open it again. Crysis-2 and 3 are running smoothly. The only problem is that Crysis is not working. Does anyone have any unusual advice? or I'll ask for a refund.
My system is,

AMD Ryzen 2600X
32GB Ram
GeForce RTX 2080
Windows 10 x64

Thanks...
I don't have Windows 10, but problems like this sometimes occur if you aren't running as the administrator.

Try to run it as the administrator and also set compatibility on the executable file to Windows XP or Windows 7.
Run as if on XP sounds like it would then revert to the DX9 version but I am not sure of that.
So there is a certain issue, which is likely a result of Crytek assuming (not unreasonably) that AMD CPUs will always have support for "3D Now" instructions. Turns out, they no longer do, but since that assumption was made, the flag is set to use their code paths instead of MMX / SEE ones. This is one potential crash that happens on AMD CPUs now with 32bit version.

Other, that may happen with 64bit version (at least happened to me) is related to float operations, where - for some reason - the MXCSR register is not using default flags, where trying to convert double to float (using cvtsd2ss instruction). I have no idea why, but I managed to fix that as well.

Here is a fix for 32bit version - https://community.pcgamingwiki.com/files/file/1411-crysis-amds-3d-now-fix/
And this one may help with 64bit - https://community.pcgamingwiki.com/files/file/1412-crysis-64bit-unhandlead-point-inexact-result-exception-fix/

--Edit --
I wrote a more in-depth explanation of both issues:
https://suimachine.github.io/reverse/2019/09/24/Fixing-Crysis.html
Post edited September 24, 2019 by Suicide_Machine
avatar
Suicide_Machine:
A big thank you for such thorough work!