How I got finally Crysis to run on W7 64bit (& Crysis Warhead)

[knuddelholic]

Ok, here are some tips how I finally make Crysis run on my Windows 7 64 bit system on a 1920x1080 resolution after spending hours with different suggestion which didn’t worked by themselves.

In a nutshell those steps should upgrade your game with files to run on 64 systems and prevent after that the black screen which haunted most of us.

I try to make those instructions as clear as possible for those which are less used to such software fixes. (Crysis Warhead solution is in the second posting below !)
Please read the instructions through once first and don't try to start the game halfway through the steps.

Thanks to the players ‘Postal Dude’, ‘embak’ and ‘Spudsy’ for supplying links and important thoughts to the solution.

1. First go to C:\Users\-Administrator- or –your name-\Documents\My Games\Crysis and delete in that folder the complete Profiles folder with its content as those files are created every time you run the game and might mess with your following try to fix it. Thanks ‘Spudsy’ for the tip.

2. Next I got ‘Postal Dude’s’ (PD’s) BIN64 files which I put on a server together with the second file (9KB) needed in point 4. You can find the file (18MB) in this location: www.outfoxed.net/crysis-fix

3. Unzip the file and copy the Bin64 into the main folder of the Crysis game, renamed the existing Bin32 to Bin32.OLD and rename PD’s Bin64 to Bin32. Inside our new Bin32 folder I went to properties from ‘Crysis.exe’ and changed its compatibility mode to Vista & SP2. Do NOT do this with the ‘Crysis64.exe’ file, do it just with the ‘Crysis.exe’.

4. Now I went to a post from ‘embak’ at http://germancrysis.com/viewtopic.php?f=20&t=1702 and got me the small zip file of 10KB ‘Crysis 1_ultrahighqualitycfg_1.3.1.zip ‘ and unzipped it. You can get it also from: www.outfoxed.net/crysis-fix

5. Under C:\Games\SteamLibrary\SteamApps\common\Crysis\Game\Config I renamed the folder CVarGroups to CVarGroups.OLD and then copied ‘embaks’ CVarGroups folder into C:\Games\SteamLibrary\SteamApps\common\Crysis\Game\Config

6. Last step: In C:\Games\SteamLibrary\SteamApps\common\Crysis I renamed autoexec.cfg into autoexec.cfg.OLD and then copied ‘embek’s’ autoexec.cfg into C:\Games\SteamLibrary\SteamApps\common\Crysis


Important This should be it. Do NOT try to start the game between step 2 to 6 or the game will create new profiles in C:\Users\Administrator\Documents\My Games\Crysis which will mess up again any start attempt.

Important I suggest to NEVER use the start button in Steam as it will very likely mess up the profiles and you have to redo the whole procedure. Always start the game via desktop icon.

I tried it several times and it works fine even you might face quite some delay before the EA splash screen comes up.
I suggest NOT messing around with the setup in the option menu as that might mess up again the profiles folder. But the game should now run at least and with pretty nice settings.
Worst case: If you play around with the settings and you have crashes again, just repeat the six steps and you're fine again.

Thanks again to the others which helped with suggestions and provided files. My goal was just to be able to run and enjoy the solo campaigns. For multiplayer you can find enough other posts which help with that issue.

I hope this helps at least some people.
P.S. for Steam: Creating posts in Steam forums with format is such a pain in the @$& .

[knuddelholic]

I can't help at this point as I will avoid Windows 10 as long as I possibly can.
But maybe someone else from the community can jump in with a working solution for Windows10 64 bit for the Crysis 1 Steam version how to make it run?

The first thing I would try is using the original checklist I created from poinr 1 to 3 and ignore 4 to 6 as latter are for modifying the detail settings and see if the game starts that way.
But I presume that the problem lies in the exe file itself. If that's the case then there might be no fix without the help from Crytek.

[_Soj_]

引用自 knuddelholic：

I can't help at this point as I will avoid Windows 10 as long as I possibly can.
But maybe someone else from the community can jump in with a working solution for Windows10 64 bit for the CRysis 1 Steam version how to make it run?

The first thing I would try is using the original checklist I created from poinr 1 to 3 and ignore 4 to 6 as latter are for modifying the detail settings and see if the game starts that way.
But I presume that the problem lies in the exe file itself. If that's the case then there might be no fix without the help from Crytek.

I doubt it's the exe., as a number of people report running it fine with Win10 straight outa the chute.

It's mainly a configuration and SecuROM problem.

[knuddelholic]

I have no idea how well the game runs on W10 or not in general but there are always individual issues some face.

If someone can come up with a summarized checklist like I did puzzling the parts together from the very extensive W7 64 thread we can make a similar thread for W10 if there are more around with configuration issues.

I was more hoping for this thread of experiences from other players who modified Crysis and Warhead beond this stable solution and added mods and increased screen resolutions beyond 1920. I do not like to speculate over an OS I don't have yet.
Unfortunately the feedback is so far more then modest.

[rb42]

Add Crysis64.exe as a non-steam game. I'm pretty sure it simply links to the wrong executable on 64 bit systems.

[Peaceful Joe]

I used to be able to run this game on my 64 bit computer with all the settings maxed out, but now the only way to even laucnch the game is to put -dx9 into the laucnh options. This is unnaceptable because I know that I can definitely have the game running at its full potential. I tried all of the fixes here on steam, but none of them work. There must be something simple that im missing but I can't figure it out.

[ltolman4]

Ok so I followed the instructions at the beginning.

I changed my game.cfg within MyDocuments/Games/Crysis to change my Screen Resolution to 1920x1080

I was able to successfully launch the game. But how do I know for certain all these mods are actually working?

Thanks :)

[knuddelholic]

You're welcome :)

I ran before the checklist with the more basic stuff suggested from 'Postal Dude' before I later implemented the modifications from 'embak'.
It does look better then before.

But I had no access and time to experiment with other mods yet as my main goal was to make the game run at all for those who faced that obnoxious crash at the EA splash screen. Screw the Steam overlay, at least this solution let the game run stable in 64bit.

I would love to see some more feedback of folks who used this summarized solution and let us know if they were able to run other, more elaborate mods with this solution and provide some links to those mods.
If possible I can see to add those mods to the server from my friend or at least a txt file with those links in it to have all useful stuff combined in one spot in case other mirrors are going down.

[colesdav]

Try this
http://steamcommunity.com/app/17300/discussions/0/451852225133478824/

[Sirkut]

Great guide! Worked like a charm! Thanks a lot!

[Workshed]

All I did was set it to run in compatibility mode for Windows XP SP3. Game seems to run fine now.

[knuddelholic]

*bump*

[lonewolf45622]

friend please help, it keeps asking for a disc

[knuddelholic]

You should keep in mind that EVERYtime you run the game it cretaes those profiles. Please follow the guide step by step and it should work. The profile folders must be first all deleted before the guide can work. Good luck.

[ブリッジス テウタ]

Hey, thanks for your guide but there is still a small thing that doesn't work at all : when you provide a link to downloade the two files, it is impossible for me to download Crysis1.2.164Bit[STEAM] => slow speed and, eventually, cancellation of my download. Any solution to this ? Thanks again :-)

[knuddelholic]

Thanks for bringing that to my attention. It's a server from a friend as many public server often deleted those files. I will contact him and see to fix the issue.