Crysis & Win7

Technology and Gaming Help and Support
#1

I bought Crysis on Steam a couple weeks ago during a sale, and every time I change any settings, it crashes, even if it’s just a simple button reassignment. Restarting the computer works every once and a while as a temporary remedy, but it’s still a major pain in the ass. I’ve tried updating drivers, using compatibility modes, reinstalling, cleaning the registry, defragmenting, and the patches were already applied. And interestingly enough, Warhead has no issues whatsoever. Has anyone else had this problem? Is there a permanent solution?

(If relevant) Specs:
Core2 Quad 9550 @ 3.4Ghz
Kingston 8GB DDR2 - 1066
Nvidia GTX260 Core216
Windows 7 Pro x64

#2

I registered just so that I could answer your question. As far as I know, partly from experience, as I’ve had this problem before myself, the original Crysis game cannot be run on a x64 operating system if it is bought and downloaded from Steam. You’ll run into the same problem with most Valve games such as HL and HL2, Portal, and TF2. It’s unfortunate, and annoying, yes, but you can still play the game if you install a x86 OS.

I wouldn’t bother Googling for solutions either, as you’ll simply end up finding the same results. I searched for hours for a solution and could not find one. They never released a patch of any kind. Store-bought copies of the game can be run on x64, but not if you have downloaded the game from Steam.

Sorry, and good luck.

#3

I have no problem in any of those games in windows 7 ultimate x 64 with steam
However, if you are having trouble with changing settings in crysis, simply make an autoexec file in that directory setting the game to the desired settings when the game starts.
It’s a crappy work around, but it does the job.
The only initial problem with crysis I had was that catalyst drivers had the scaling options disabled, so the screen was a bit wonky when changing resolutions.

#4

I dont think its Windows 7 64bit cause I have the Win7 Ultimate 64bit retail right now and used to run build 7000, 7057, and 7100 all in 64bit and I never encountered a problem with em.

#5

I had Vista Ult x64 since the beginning of 2007 and ever since I was able to run hl,hl2,portal,tf2 and the retail version of Crysis (don’t know about steam version).
I have never encountered a problem like this.
Have you tried reinstalling Steam? That usually works with these problems.

#6

Thanks for the replies so far, guys. As a quick update, I looked through my Crysis files and noticed that Steam didn’t install a 64 bit executable, which is is apparently included with the “retail” version of the game, and I’ve got a feeling that’s why I’m running into these problems. Just to see what would happen, I copied the Bin64 folder from Warhead to the Crysis directory and ran the Crysis64 exe from there. It started up fine and even let me change the settings without any problems, but crashed after the opening movie when starting a new game.

I’ve opened a support ticket with Steam about this issue and to request the proper Bin64 directory, though I doubt they’ll do anything about it. In either case, I don’t think I’ll buying any more games through them.

#7

I have a kinda good pc , but when you guys post a Spec like this, I always get the feeling that I’m using a commodore 64 :frowning:

#8

He’s got a bit of a GPU bottleneck, though. :confused:

#9

Uh, not really no.
a single GTX 260 is a powerful enough card, the core 216 model is a bit more so.
I was able to run most everything at 1920*1200 just fine.
If he only has like a 22inch monitor ( which is common ) that GPU is STILL overkill.

#10

I’ve just downgraded from 7 to XP on my laptop and my games run 100% faster.

I had to make a custom nLite CD and manually integrate the new sata drivers so that XP would recognize the laptop’s HDD. I wasted all night doing that but it’s worth it.

#11

What I mean is that he has a lot of room to grow without upgrading his CPU, not that his graphics are necessarily holding him back.

#12

That shouldn’t be a problem if you have an XP SP2 or later disk.

#13

And they still haven’t given me an answer in any form. I’m normally pretty patient, but this is ridiculous.

It’s kinda intentional. I got the card at a good price, and plan on upgrading it when DX11 cards go mainstream. I just hope my processor will still be viable when that time comes around.

Currently using a 23in @ 1920x1080 and a 22in @ 1680x1050. It seems to strain a little while running Cryostasis maxed out, but that’s probably from the PhysX processing, because the graphics aren’t really that spectacular.

I doubt your games run twice as fast, unless your laptop is junk and only got 2fps before then 4fps after.

Or if his laptop BIOS supports the IDE hard drive compatibility mode.

#14

Same issue here. Found no fixes. I simply edited my CFG’s to the settings I wanted so I wouldn’t have to worry about changing settings and having it crash.

Had no issues before Windows 7.

#15

I might be bumping this thread a little, but I finally got a reply from EA. It only took a month for them to tell me to reinstall the game and install patches. Then the rep told me the game was never compatible with 64-bit operating systems because it hasn’t been “officially” tested. What kind of bullshit answer is that? Even the demo of the game had 64bit binaries and it worked perfectly fine on my PC. It’s like they’re trying to make it look like I wasn’t paying attention to compatibility issues that don’t exist, so yeah, they’re starting to piss me off.

Just had to let off a little steam…

#16

Oh , since you bumped the thread, I might as well add my findings. Uninstall the game, and delete all of your user files. (located in your documents). Re-install, and install all patches BEFORE hotfix 1.21. The game will run perfectly.

Something in hotfix 1.21 does NOT like Windows 7.

#17

'tseems the grapes are sour :freeman:

#18

I have had some issues with crysis myself, which is why I can empathize with you. You mentioned that copying the 64bin from Warhead made the options work, but not the actual game. Now I know nothing about thse types of things whatsoever, but maybe the reason why the options worked after that is because both Crysis and warhead use the same options information, but the actual gameplay and stuff is different between the two so it didn’t work. You mentioned that the demo worked on 64bit, why don’t you reinstall it and copy the 64bin over to your actual folder. Because they are from the same game, they might be more compatible. But like I said, I have no knowledge over this stuff whatsoever. I’m just spitballing here, and it will probably be just a waste of time. But its worth a shot, right?

#19

@Sitten_duck

I actually just tried that yesterday. There was also an idea on a different forum to use the Crysis Wars Bin64 and merge it with certain files from the demo. Neither worked. It would hang before loading the game, just like when I tried using the Warhead Bin64.

@Deathmonkey7:

I’ve tried doing that as well, but for some reason, I’m unable to install any patches at all. Each attempt comes up with an error. I haven’t verified this, but I heard that the Steam download already includes all released patches, so there’s not really much else I can do on that front.

Thanks for the replies guys. Nothing has worked so far, but at least you’re giving me better ideas than the EA support is.

#20

Sry that didn’t work. It sounds like you have tried everything, but just in the off chance that you forgot this more obvious one I’ll bring it up. If you have Win7 Professional or Ultimate, you could try XP compatibility mode when playing it. I don’t know if it will change anything.

Other than that, the only thing I can think of is partitioning your HDDs and putting XP 64/32 bit, or Win7 32bit on it and run it there. Its lame, but you just might have to do that to play some games.

Founded in 2004, Leakfree.org became one of the first online communities dedicated to Valve’s Source engine development. It is more famously known for the formation of Black Mesa: Source under the 'Leakfree Modification Team' handle in September 2004.