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)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
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


Here's my command line:
C:\Windows\System32\cmd.exe /C start "" /affinity FE "E:\Steam\steamapps\common\Crysis\Bin32\Crysis.exe" %command%
Here's the file path to the game:
E:\Steam\steamapps\common\Crysis\Bin32
Any help would be appreciated
i have 8 core amd processor and my game files in the F partition so what is the command can u help me pls
I only blindly applied hawkhill fixes "About the game not launching (and how to fix it)". Game runs OK, although tweaking graphics is quite unlike tweaking modern games.
Now only have 24 Hz instead of 60 Hz if V-SYNC is enabled but there should be fix for that.
2017 100% Working Fix For Crysis & Crysis Warhead On Windows 10
This First Method Requires That You "Own" Crysis Warhead.
About half an hour ago I purchased Crysis(Steam), Crysis 2(Origin), Crysis Warhead(Steam), and Crysis 3(Origin). I have yet to test my Origin downloads but neither Steam version would launch. I was getting really upset as I had purchased these games from a Third Party Source. No matter what patches I tried to download or anything of that sort fixed Crysis. So I tried launching Crysis Warhead, same freaking error! Checked the files in Warhead and was surprised to see a "Bin64" folder! I Immediately double clicked on the 64bit application and the game launched! Praise Gaiben! After closing the game and attempting to launch it again via steam it wouldn't so...
METHOD 1)
For Crysis Warhead:
1) Download Both Crysis & Crysis Warhead
2) Open the folder where Crysis Warhead is installed
3) You'll see a Bin32 folder and a Bin64 folder
4) Delete the Bin32 folder
5) Rename the Bin64 folder to Bin32
6) Open the new Bin32 folder
7) Delete the "Crysis" application
8) Crysis Warhead Now Works!
For Crysis:
1) Right click and copy that new Bin32 folder you made for Crysis Warhead
2) Paste it into the Crysis install file (replace the old "Bin32" file with the new one from Crysis Warhead.
3) Crysis Now Works!
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.
I chose your answer as a Solution so people can see it more easily when they open this thread.
Thanks!
Edit: I don't know what happened but after uninstalling and reinstalling fixed the issue
I used the 6 core command.
Note: I had trouble at first, but all errors on my part. First, I had to make sure I turned off all compatibility mode settings I modified for every exe file in the Crysis installation folder via the Steam common directory. It won't work if you have it set to windows xp, etc compatibility.
Second, I had to make sure I changed the address in the command line, to fit my installation address. Not just the drive path, but also the folder I created for it.
Thanks again Amanda.