Crysis
Toquita 2016 年 6 月 25 日 下午 1:40
2
3
8
1
[TUTORIAL] How to PROPERLY run Crysis on Windows 10 64-bit
If you read this forum you'll see lots of threads with suspicious content (to say the least), like unofficial "patches", or even cracks for the game.

Well, now your problems are gone. No need to install shady programs, patches or cracks, or create bat scripts. You can start Crysis through Steam, all it takes is one simple command.

I assume the launch problems happen only on 64-bit machines, but let me know if you're having problems on 32-bit Windows.

--------------------------------------------------------------------------------

To start, open your Crysis Launch Properties.

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%

I have a 6-core AMD (FX 6300), so my 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 FX, try this:
C:\Windows\System32\cmd.exe /C start "" /affinity E "C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

Done!

https://i.imgur.com/WeRv7fY.png

(Most of the credits go to: http://germancrysis.com/viewtopic.php?f=34&t=1740)
最後修改者:Toquita; 2016 年 6 月 29 日 上午 2:56
引用自 aveamurechi:
I have a Ryzen 9 3950x on Windows 10 2004. For me I had to use the command in initial post with affinity set to FFFE. The game would then start. In order to get a resolution that does not appear in the game menu (1920x1080) I had to go to the Crysis folder in the Documents/MyGames folder on C and change the width and height parameters in the game.cfg file I found there. After that the game runs nice with my native monitor resolution of 1920x1080.

Since this seems to be not widely known:
the /affinity command receives a parameter as HEX value, which converted into binary specifies to Windows which cores to use to run the game.

E.G:
- on a 4 core system if you set the affinity to 3 (HEX) then you get in binary 0011 which means that cores 0 and 1 will be used and cores 2 and 3 will not be used.
- in my case by specifying an affinity FFFE, I get in bynary: 1111 1111 1111 1110. Which means that basically just core 0 will not be used, but all other cores will be used. (The Least Significan bit - LSB is always rightmost in binary, and core counting starts from 0)

The initial post in this thread seems to follow the rule that the core 0 should never be used. And their examples also adhere to this rule. Why that is I do not know, but I extended the same rule to a 16 core processor, and it worked for me.

Oh, and don't install the GameSpy Comrade thing; it's not necessary for the core game (it's just a multiplayer middleware) and the GameSpy servers are long offline.

Personally I did not try the other way of making it run (with the BIN32/64 folders taken from the warhead expansion... yuck). This affinity thing seems much cleaner to me, and it worked, so...

Hope this helps.
< >
目前顯示第 136-150 則留言,共 299
Kekacang 2018 年 5 月 4 日 下午 8:29 
Either I'm an idiot or there's something wrong with my system, so please help me.

I have a Ryzen 5 1600X running and I already tried the command that you gave but I still can't run the program properly, it just keeps on crashing. I have 2 drives in my system and I installed the game on my 2nd HDD, which is my storage drive. Here's the command that I put in:

C:\Windows\System32\cmd.exe /C start "" /affinity 3E "D:\Program Files\steamapps\common\Crysis\Bin32\Crysis.exe" %command%

The location of my game is as follow:
D:Program Files\steamapps\common\Crysis\Bin32\Crysis.exe

Anyone know where I did wrong?
Toquita 2018 年 5 月 4 日 下午 9:08 
Do you run Windows 32-bit? Because it seems you're missing the "(x86)" and also the "Steam" parts.

Try the following command:

C:\Windows\System32\cmd.exe /C start "" /affinity 3E "D:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%
soupial 2018 年 5 月 11 日 下午 5:28 
This fixed it! Thank you!
Kekacang 2018 年 5 月 13 日 下午 12:03 
引用自 Toquinha
Do you run Windows 32-bit? Because it seems you're missing the "(x86)" and also the "Steam" parts.

Try the following command:

C:\Windows\System32\cmd.exe /C start "" /affinity 3E "D:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%
No. I run Windows 10 Pro 64bit. Any idea?
Toquita 2018 年 5 月 13 日 下午 12:30 
Paste here the directory where Crysis is installed. Mine's like this:

C:\Program Files (x86)\Steam\steamapps\common\Crysis\Bin32\Crysis.exe
Macanoid 2018 年 5 月 13 日 下午 2:06 
Ryzen 3 1200 CPU & windows 10 64-bit. This worked for me, just needed to replace game location with my own directory. Game runs smooth, thanks for this fix!
Bad! 2018 年 5 月 14 日 上午 10:26 
Only AMD?
Kekstroin 2018 年 5 月 16 日 下午 5:06 
The game is open but when I play a new game it stays on the black screen.Can you help me?

(Sorry for english. I use Google Translate ^^ )
computaquark 2018 年 5 月 17 日 上午 8:45 
Works for FX 9830p with RX 460 on windows 10 creators. 4 core fx solution.
Derp 2018 年 5 月 22 日 上午 7:29 
Oh my ♥♥♥♥♥♥♥ god dude you are a legend. Works on a ryzen 3 2200g if anyone was wondering. I kept trying to do the Bin.64 thing but never gets past the intro. Thanks to you i can replay my childhood game. Thanks alot!
Joseph4499 2018 年 6 月 25 日 下午 2:19 
I know its to years later now but you are an absolute star! Got it running perfectly! Had to change it around some because my directory was different but it works.

C:\Windows\System32\cmd.exe /C start "" /affinity FE "M:\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%
SolivaN 2018 年 6 月 26 日 下午 7:05 
YOU ARE GREAT, THANK YOU FOR YOUR HELP! :steamhappy:
captain_nacho 2018 年 6 月 26 日 下午 8:05 
Thanks. Really hope that this works. Hope to see if this PC can run Crysis!
captain_nacho 2018 年 6 月 26 日 下午 8:09 
Still not working. Game boots up, shows black screen, and shuts down about 30 seconds later. Will I have to get a refund or something?
Toquita 2018 年 6 月 26 日 下午 8:56 
If you actually did the command correctly and it still didn't work (unlikely but possible), then yes you should get a refund.
< >
目前顯示第 136-150 則留言,共 299
每頁顯示: 1530 50