Next Generation Emulation banner
1 - 20 of 30 Posts

shade-666

· Registered
Joined
·
5 Posts
Discussion starter · #1 ·
Really wierd, tried almost all modes and still no "beep" (game doesn't see my gamepad as from xbox, although i can use almost all keys but they all wrong and cannot be changed even in options menu) . Iam using Win 7 64bit so iam running game as 64bit but when i try run game as a 32 bit version (32bit folder) the game starts with beep and the controls seems all fine but the game after loading screen become black and nothings happen.
 
Discussion starter · #4 ·
I have the same problem, I can not run x360ce with the 64-bit library, I recognize the gamepad but in red and does not sound the beep as when in green. any solutions?
same here and i think the suspect is that we're using a 32bit drivers for our gamepad/converters
i try to find some other 64bit drivers to confirm this
 
not the case

You just haven't installed the necessary Visual C++ 2011 redists for x64

or as follows

I have the same problem, I can not run x360ce with the 64-bit library, I recognize the gamepad but in red and does not sound the beep as when in green. any solutions?

the configuration app CANNOT be used with the 64bit lib, you configure the inf with the 32bit version and then move the ini to the games folder. (or configure with x86 and then replace with x64)
 
the configuration app CANNOT be used with the 64bit lib, you configure the inf with the 32bit version and then move the ini to the games folder. (or configure with x86 and then replace with x64)
only just to place the file x360ce.ini and xinput1_3.dll (64bits) in the game folder and should operate? or gamepad driver need 64bit version?
 
only just to place the file x360ce.ini and xinput1_3.dll (64bits) in the game folder and should operate? or gamepad driver need 64bit version?
In the folder with the 64-bit executable you should put: xinput1_3.dll (64bits), x360ce.ini, x360ce.gdb. And dinput8.dll (64-bit) if needed.

You might have to enable gamepads in the game too.

When you install a gamepad on Windows 64-bit it will automatically be a 64-bit driver. If you manually install a driver it should be for Windows 64-bit. This is the case even if you want to play 32-bit games, which use 32-bit x360ce.
 
In the folder with the 64-bit executable you should put: xinput1_3.dll (64bits), x360ce.ini, x360ce.gdb. And dinput8.dll (64-bit) if needed.

You might have to enable gamepads in the game too.

When you install a gamepad on Windows 64-bit it will automatically be a 64-bit driver. If you manually install a driver it should be for Windows 64-bit. This is the case even if you want to play 32-bit games, which use 32-bit x360ce.
I understand, but without the app as configure the x360ce.ini? I have to do it manually? or I can paste the x360ce.ini me to believe the 32bit app?
 
well, I got the game detects the x360ce 64bit, however I get an error when running the game. see image, any solution?
6. Because the App version does not match the Library version, an error message may come up: “Configuration file version does not match x360ce version”. You can suppress by adding Version=1 to the [Options] section of x360.ini, see below. You can also edit the [InputHook] section, see below.
Please read the stickies.
 
Please read the stickies.
but if the only thing I did was extract the files that tell me this library "x360ce_lib64_r789_VS2010" and paste it there and throws me that error. :???: I understand, I will try that you tell me.

edit: even so by modifying the. ini, adding those lines still gives me that error: S
 
but if the only thing I did was extract the files that tell me this library "x360ce_lib64_r789_VS2010" and paste it there and throws me that error. :???: I understand, I will try that you tell me.

edit: even so by modifying the. ini, adding those lines still gives me that error: S
Have you ever used x360ce with a 32-bit game, that is nearly all games? If so you can copy the x360ce.ini from that game, and use it with Outlast.

Note that the x360ce 64-bit library doesn't come with x360ce.ini, only x360ce.sample.ini. This cannot be used unless it is heavily modified, something that is not that easy. See the tutorial at http://forums.ngemu.com/showthread.php?t=155310
 
Have you ever used x360ce with a 32-bit game, that is nearly all games? If so you can copy the x360ce.ini from that game, and use it with Outlast.

Note that the x360ce 64-bit library doesn't come with x360ce.ini, only x360ce.sample.ini. This cannot be used unless it is heavily modified, something that is not that easy. See the tutorial at http://forums.ngemu.com/showthread.php?t=155310
yes friend, it works perfectly the version "x360ce.App-2.1.2.191" 32 bits in all my 32-bit games .. it is the first time I try with a game of 64-bit, from there my inexperience with 64bit library. and the multiple mistakes that I had. :???:

edit: I found the tutorial the following:
• x360ce.sample.ini: this file is not required. It is a sample file for x360ce.ini, which contains settings for xinput1_3.dll, which are both controller and game specific. HOWEVER x360ce.ini IS REQUIRED, and it is simplest to put this in the same folder as xinput1_3.dll.

then I copy a x360ce.ini of some of my 32bit games and paste it on the game 64bit next to x360ce.gdb and xinput1_3.dll of the library 64bits i add the line version = 1 to x360ce.ini and not appeared the error, however I do not hear the beep in the game, so I guess not recognized the gamepad, as it continues to stick invested. I'm beginning to think that the game is not compatible with the emulator yet.

sorry my bad english my language is Spanish, thanks for all the help.
 
It could need a HookMask or library filename change. See:


Q2. I can't find my game in the Game Compatibility List. What [InputHook] and x360ce Library filename should I use?


Start with the following [InputHook] in x360ce.ini:

[InputHook]
HookLL=0
HookCOM=0
HookSA=0
HookWT=0
HookDI=0
HookPIDVID=0
HookName=0


And then enable the hooks (=1) as you go along. HookCOM is usually needed if you have ghosted input, or the controller maps wrongly. HookDI and HookPIDVID are sometimes needed if the controller isn't recognised by the game. The other four hooks are very rarely needed, but enable them if it doesn't work.

The other possibility is that you need to rename xinput1_3.dll (x360ce Library). The easiest thing to do is to go to, in x360ce.exe, Options > Installed Files, and make sure all the boxes are ticked. This clones xinput1_3.dll under these new filenames. If that works, try to narrow it down to the actual filename used. Note: this does not work with 64-bit Libraries: it must be done by manually changing the filename.

If you get it to work, please report your game executable name, InputHook and Library filename to http://forums.ngemu.com/showthread.php?t=155113
 
1 - 20 of 30 Posts