Problem with Xinput and Crysis

[Xtreme2damax]

Every time I try to load the 64-bit executable of Crysis I get an error stating, "Cryinput.dll could not be loaded" and then goes on about checking to see if Xinput is installed.

I checked to see if Xinput was installed and it is as well as the Xbox360 controller driver for PC since I use a 360 controller, yet Crysis gives me this error every time I try to launch the 64-bit executable.

I should be able to launch it without a problem since I am using Windows XP x64 on a 64-bit Amd processor. The 32-bit executable and the game launches fine, it's just when I try to launch it using the 64-bit executable.

Google is of no help, results either turn up nothing or a fix for Win2K users who are getting this error, however nothing related to this problem for those who are using newer operating systems such as XP-64 or Vista-64.

If anyone has had this error when trying to launch the 64-bit executable of Crysis and have solved it, please post here what you did to fix the issue.

[mad_onion]

um i think it might be because xinput isn't supported (and so won't install) under xp 64bit.

[Xtreme2damax]

  mad_onion said:

um i think it might be because xinput isn't supported (and so won't install) under xp 64bit.

Theres an Xinput driver for Windows common controller for 64-bit and even Microsoft has 64-bit versions of their Xbox360 controller drivers.

Why would there be a 64-bit executable of Crysis and other games that use the 360 controller if Xinput didn't work under 64-bit? I have both the Xinput driver for 64-bit operating systems as well as the 64-bit version of the Xbox360 controller driver, yet I am having this problem whenever trying to launch the 64-bit executable of Crysis.

[mad_onion]

well the 64bit xinput works in vista but i didn't think it was supported under xp 64bit.

[Xtreme2damax]

It should run fine on XP64 as it has been confirmed to do regardless of whether Xinput is supported on XP or not. I am still getting this error even on a fresh install of Crysis.

Every time I try to run the 64-bit Crysis executable under XP64 I get this error and Crysis fails to start, it does not do this however when I run the 32-bit executable.

I wanted to run Crysis in 64-bit as it is slightly faster, but this issue is still occurring. DirectX is fully updated and I have already tried installing the Xinput driver to see if it would help, still a no go.

If anyone else has had this problem or knows how to solve it please let me know as I am still awaiting a solution.

[Unimatrix Xero]

why dot you email EA directly or give them a ring?

[Xtreme2damax]

  Unimatrix Xero said:

why dot you email EA directly or give them a ring?

Because I didn't want to have to bother with that and thought it would be quicker to ask here instead of going through another otherwise useless tech support for a spoonfed response that is most likely has nothing to do with my problem nor solves it.

I hear of tech support horror stories all the time, specifically with companies like EA and Valve so I'm a bit weary about bothering to submit a ticket/email.

I will however use it as a last resort if I am unable to receive a solution through this forum.

[mad_onion]

i think it's unlikely you will get a solution after the thread has been open this long. if anyone knew they would have said. i would go for the last resort.

[Xtreme2damax]

Lol I fixed it and yet the solution was so simple, no need to get help from EA. :p

I finally figured what was wrong, because I was not only having problems with Crysis, but any 64-bit application that used Xinput. Turns out I had the wrong 64-bit xinput1_3.dll in the system32 directory on Windows XP 64-bit.

So I downloaded the latest DirectX redistributable, extracted the latest 64-bit xinput1_3 dll and placed it in the system32 folder and my problem(s) were solved.

I had to do it manually because just running the DirectX updater or installer wasn't replacing the dll with the correct one.