Crysis fix - how to play with AMD (especially Ryzen), DRM fix

[Kurasan]

So there have been a lot of silly tutorials here, like renaming Bin64 to Bin32 or copying files from Warhead into Crysis 1 or running Crysis with those special affinity commands, all of them are kind of silly and over-complicated. None of those would really help you to run it on for example Ryzen, just because Crysis assumes that if CPU is from AMD, it must support 3DNow! instructions, which are long deprecated since AMD FX series.

All you have to do to fix Crysis is to install this patch: https://crymp.net/ and simply use shortcut it creates on Desktop in order to play + you get working multiplayer as an extra.

Another nice thing is that this patch will not rewrite any of the original game files and those worried about safety, whole patch is actually open-source

[Ceejay]

See I did not need to do any of that.
I added this into the launch options, it ran fine on my fx8350 and it allows my ryzen 3600 to work too.

C:\Windows\System32\cmd.exe /C start "" /affinity FE "C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

Due to the amount of different hardwar and software, some fixes work with some configurations some do not.

I know for instance if you have a quad or six core FX you need to use a different value other then FE to get them working.

I also think only 8 of my 12 threads are working fine on my ryzen, which makes sense since FE is to enable all 8 cores on the 8350 to work, but I have no idea what value to use other than FE, plus it still runs the game at full speed so not too bothered :)

[Kurasan]

Well, using this patch you play Crysis natively on all kinds of CPUs and you don't need to struggle with finding right value for affinity + you get some other benefits like ability to run Very High settings in DX9 mode and also to run multiple instances of game in same time + you also don't need to struggle with compatibility modes.

For example on my Ryzen CPU, not even setting affinity helped just because my CPU didn't support instruction Crysis tried to utilize, so it just crashed midgame.

[Ceejay]

The patch is indeed useful. I am just pointing out that some people with AMD will not need the patch either.

Why install a patch, when you can cut and paste the launch command? (and also have no issues with dx9 or struggle with compatibility modes either).

I found some of other values too. still higher cores may need a different value, but as I say my Ryzen 3600 (12 thread) seems to work fine with the 8 core command.

If you have an AMD processor with 8 cores, set the following launch command:

C:\Windows\System32\cmd.exe /C start "" /affinity FE "C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

If you have a 6-core AMD like a FX 6300, the command is:
C:\Windows\System32\cmd.exe /C start "" /affinity 3E "C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

If you have a 4 core, try this:
C:\Windows\System32\cmd.exe /C start "" /affinity E "C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

If the launch commands do not work then your patch is a great idea.

[DrunkenCoder]

Hmmm… the start commands won't work for me. The only thing I get is a message box titled “Steam Error” with the message “Application load error 5:0000065434”

[Ceejay]

Originally posted by DrunkenCoder:

Hmmm… the start commands won't work for me. The only thing I get is a message box titled “Steam Error” with the message “Application load error 5:0000065434”

Maybe the patch will work for you then :)

I also assume there are values that work with other AMD's, but I cannot see a pattern in the values to guess what they should be, someone may know, but then this game is ancient and ryzens are new, so maybe no one is even looking into it.

[DrunkenCoder]

Yes, it does. I wonder why there are no 64-Bit executables, though. The "patch" assumes they're there (creating a new Bin64 folder).

Regarding the affinity setting: It's a hexadecimal bit mask. FE converts to 11111110 binary, telling Windows to run the crysis exe on core 0 exclusively (read the mask from right to left).

3E and E lead to similar masks, only with less 1's. You can use the Win10 calculator in programmers mode to see the pattern.

[Ceejay]

Originally posted by DrunkenCoder:

Yes, it does. I wonder why there are no 64-Bit executables, though. The "patch" assumes they're there (creating a new Bin64 folder).

Regarding the affinity setting: It's a hexadecimal bit mask. FE converts to 11111110 binary, telling Windows to run the crysis exe on core 0 exclusively (read the mask from right to left).

3E and E lead to similar masks, only with less 1's. You can use the Win10 calculator in programmers mode to see the pattern.

Ah so the 1's represent the cores not to use, so fx;s having eight cores there are seven 1's and 0 is the eigth core. Hmm, I shall have to check if the 8th core on the 3600 is being used primarily by crysis. Should be able to work out the other cores then....

hmm using fe on my 3600 is making thread 10 do all the work......So while I think I get how it works with fx's in telling the game which core, not sure how fe is telling the 3600 to use thread 10, I would have expected thread 8....ah well at least it works which is the main thing.

[Kurasan]

Originally posted by DrunkenCoder:

Yes, it does. I wonder why there are no 64-Bit executables, though. The "patch" assumes they're there (creating a new Bin64 folder).

Regarding the affinity setting: It's a hexadecimal bit mask. FE converts to 11111110 binary, telling Windows to run the crysis exe on core 0 exclusively (read the mask from right to left).

3E and E lead to similar masks, only with less 1's. You can use the Win10 calculator in programmers mode to see the pattern.

Yes, patch creates Bin64 even if there is none, but patch actually works even with 32 bit version of game, so you can enjoy playing 32-bit Crysis even on AMD! :D

Difference between 32bit and 64bit versions of this game is, that 32bit version utilises SSE instructions for math, so game runs a little bit faster while 64bit doesn't.

Problem with 32bit on AMD has always been that game assumed that if CPU is from AMD, then game can use 3DNow! instructions, but AMD CPUs since FX series deprecated these instructions and therefore game would simply crash at start, so this patch fixes it and 32bit game works on AMD.

And if you think about it, it gives sense that 64bit worked on AMD, just because game never utilised those instructions anyway, so there was no way for it to crash, but also performance was crappy :D

[Ceejay]

Originally posted by Kolaka Masaka:

Originally posted by DrunkenCoder:

Yes, it does. I wonder why there are no 64-Bit executables, though. The "patch" assumes they're there (creating a new Bin64 folder).

Regarding the affinity setting: It's a hexadecimal bit mask. FE converts to 11111110 binary, telling Windows to run the crysis exe on core 0 exclusively (read the mask from right to left).

3E and E lead to similar masks, only with less 1's. You can use the Win10 calculator in programmers mode to see the pattern.

Yes, patch creates Bin64 even if there is none, but patch actually works even with 32 bit version of game, so you can enjoy playing 32-bit Crysis even on AMD! :D

Difference between 32bit and 64bit versions of this game is, that 32bit version utilises SSE instructions for math, so game runs a little bit faster while 64bit doesn't.

Problem with 32bit on AMD has always been that game assumed that if CPU is from AMD, then game can use 3DNow! instructions, but AMD CPUs since FX series deprecated these instructions and therefore game would simply crash at start, so this patch fixes it and 32bit game works on AMD.

And if you think about it, it gives sense that 64bit worked on AMD, just because game never utilised those instructions anyway, so there was no way for it to crash, but also performance was crappy :D

I wonder if the launch command also somehow tells the game to ignore 3dnow then?

I lifted the info out of another thread, which also has lots of AMD users running the game fine with the launch commands.

https://steamcommunity.com/app/17300/discussions/0/351660338694333489/

The majority of the times it seems to not work is if people are not putting in the correct path to the game. (at least in that thread, you have tried and it did not work).

Shame there is no sticky to add all these fixes too.

[kAlvaro]

Thank you very much for the tip. The game wouldn't even start in my Ryzen 7 2700, this tool fixes it without any hassle.

For those who are confused by the term "patch", it's actually a program called "Crysis Multiplayer Network client mod". Just hit "Download client" and run the wizard.

[Ziksu ♥♥♥♥♥♥♥]

ok

[Fazure]

Thank you! This worked for my R5 3600X. I had to revert to the original installation as it didn't work with the Bin64 fix that everyone else has been suggesting.

[Specialist]

Originally posted by Ceejay:

See I did not need to do any of that.
I added this into the launch options, it ran fine on my fx8350 and it allows my ryzen 3600 to work too.

C:\Windows\System32\cmd.exe /C start "" /affinity FE "C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

Due to the amount of different hardwar and software, some fixes work with some configurations some do not.

I know for instance if you have a quad or six core FX you need to use a different value other then FE to get them working.

I also think only 8 of my 12 threads are working fine on my ryzen, which makes sense since FE is to enable all 8 cores on the 8350 to work, but I have no idea what value to use other than FE, plus it still runs the game at full speed so not too bothered :)

This worked on my 3600X.

[Lolyko-o]

Originally posted by Kolaka Masaka:

So there have been a lot of silly tutorials here, like renaming Bin64 to Bin32 or copying files from Warhead into Crysis 1 or running Crysis with those special affinity commands, all of them are kind of silly and over-complicated. None of those would really help you to run it on for example Ryzen, just because Crysis assumes that if CPU is from AMD, it must support 3DNow! instructions, which are long deprecated since AMD FX series.

All you have to do to fix Crysis is to install this patch: https://crymp.net/ and simply use shortcut it creates on Desktop in order to play + you get working multiplayer as an extra.

Another nice thing is that this patch will not rewrite any of the original game files and those worried about safety, whole patch is actually open-source

Hi, thanks for this. I was able to start the game with this, but even so, it keeps pulling me to the desktop after several minutes.
Anything else I could do?
I have a Ryzen9 3900X and an RTX 2080TI.

[Lolyko-o]

I answer myself :) If the game still crashes when installing the patch, run the 32 bit (.exe), in Windows Vista Servi Pack 2 compatibility mode.
At least that's how it has been working for me for several hours straight.