Next Generation Emulation banner

Report game compatibility here.

124K views 270 replies 102 participants last post by  adearya0207 
#1 · (Edited)
For games NOT listed in the Game Compatibility List

As of r574, compatibility is very different, this thread will be for reporting which hookmasks work for which games, how to use the hookmasks and I will compile a list of games already included in the GDB and link each post for each game in the list.

HookMode is removed entirely as of r574!.

Some games do not require a hookmask for some reason, but others do, particularly those that use unusual methods for detecting Xbox360 pads or support both Xinput and DirectInput pads(these are usually requiring HookCOM).


X360CE.GDB
In the GDB file, the HookMasks (HookMask=) are written using a combination of these hex values

  • LoadLibrary(HookLL) = 0x00000001;
  • COM(HookCOM) = 0x00000002;
  • SetupAPI (HookSA) = 0x00000020;
  • WinVerifyTrust(HookWT) = 0x01000000
  • DirectInput (HookDI) = 0x00000004;
  • ProductID/VendorID (HookPIDVID) = 0x00000008;
  • Spoof name (HookName) = 0x00000010;
Hookmask 0x0100003F enables all of the above for example.
Typically, only a single value will be required in the GDB.

There are also some other values that are really only useful to the developers such as

  • Stop hooking(HOOKSTOP) = 0x02000000;
  • Disable (HOOKDISABLE) = 0x80000000;
X360CE.INI
In the INI, they are entered under the [InputHook] section as

  • HookLL=(0/1)
  • HookCOM=(0/1)
  • HookSA=(0/1)
  • HookWT=(0/1)
  • HOOKDI=(0/1)
  • HOOKPIDVID=(0/1)
  • HookName=(0/1)
Whilst you can just enable all 4 and forget it, it is advised to only use one of the first 3 at a time, with the 4th (HookWT) only being used specifically in games that require it, we will not simply enable all modes for a game in the GDB without significant proof (and self replication) of it being required as this may introduce undesired behavior
Don't hesitate to report if you find any games that crash with all them set, it would be good if it could eventually default to all on and be done with it.
See the thread rules below for further information.

HookCOM
Games that support both Direct and X Input API's may end up displaying both controllers in game, resulting in ghosted input or being able to start a 2 player game using a single control (SF4/SSF4 and DMC for example). HookCOM allows the game to mask the controller's directinput capabilities, which is advised by microsoft themselves on TechNet. HookCOM is the method required in most cases of games not working.​
HookLL
Many XACT games (that is, the Xbox360/PC cross platform games) require HookLL to run properly. As they do not load the xinput runtime directly, Dinput8 wrapper is required to redirect back to the local X360CE binary instead of loading the default xinput1/9_x binary.
HookSA
This enables the hooking of SetupAPI, only the BeatHazard titles are known to require it thus far, so it should almost never be needed.
HookWT
This enables the hooking of WinVerifyTrust. This is required for games which utilise WVT for Process Integrity checking.
Only Gears of War is known to use it at this point, so it should almost never be needed.
HOOKDI
This allows the wrapper to trick some games that detect the controller GUID via DirectInput, The first Assassins Creed is one such title.​
HOOKPIDVID
This works in conjunction with FakePID= and FakeVID=
Without these, it defaults to the Wired Xbox 360 Controller which are 0x28E and 0x45E respectively.
HookName
This allows x360ce to return a different oemname than that of the controller installed. For instance, in Assassins Creed it changes the name of the xinput device to Xbox 360 Controller. While this is generally not required for functionality, the game mini ninja's is known to check for "Xbox 360 Controller" in the registry and will not work if the name is anything else.
Some games will work even without any of the above set, It would be good to know these as well.

Thread Rules:

  1. This thread is specifically for reporting games found to be compatible.
  2. When reporting game compatibility, the HookMask(s) used, full game title and executable name are required for adding to the GDB.
  3. If you find a game crashing that is listed in the second post, its likely not the wrapper, but an issue with your controllers drivers - particularly if it uses an obscure (probably bad) Force Feedback driver. Start your own thread or report the issue to the issue tracker.
  4. If a game is not working with any settings, start a thread of your own or report it to the issue tracker.
  5. Do not post in this thread about a game already listed unless you have evidence that settings provided by the original reporter are wrong.
 
See less See more
#197 ·
The EXE for Sonic Generations is SonicGenerations.exe. It has a config tool that includes input config. EXE for that is ConfigurationTool.exe.

In case you need it, EXE for Bioshock 2 is Bioshock2.exe. Single player and multiplayer have separate EXE files, but same filename.
 
#201 · (Edited)
Hi, not sure where i'm suppose to post this, but i've an issue, i use 360 controller to play rocket league, a friend of mine asked me to try this emulateur with a playstation gamepad, which is working, the thing is, now my 360 controller doesn't work for this game ( works for others games, but not rocket league ) i tried to delete the files ( the . exe, since i didn't see any new .dll ) a system folder reset, but still not working, any ideas? i'm redownloading the game at the moment, if it doesn't work, it's probably because i've do to something which i don't know.
 
#204 · (Edited)
The following games work fine with the default hook mask:
Code:
[nuclearthrone.exe]
Name = Nuclear Throne
HookMask = 0x00000002

[Sequence.exe]
Name = Before the Echo
HookMask = 0x00000002

[Spelunky.exe]
Name = Spelunky
HookMask = 0x00000002

[Starwhal.exe]
Name = Starwhal
HookMask = 0x00000002

[TowerFall.exe]
Name = TowerFall Ascension
HookMask = 0x00000002
Update of CompatibilityList in the repository: #309 (pull request)
 
#210 · (Edited by Moderator)
> The thing is that I have downloaded the 360ce thing, i have putted it in my NFS rivals folder. I have setupped it like i would like to, but the thing is the game has kinda setted the wheel settings to me. Its like in the 360 software i have setted the A button to be X in my controller, but in game A button is something else...
>
> Iam usining the logitech driving force GT and i would love to get your help with this so i can enjoy NFS rivals more.
>

Edit by mod

We don't contact by email or skype.
 
#211 ·
I'm using a Saitek Cyborg pad on Windows 10 and I've had pretty good success until recently.

The last two games I've tried have the same problem. Ori and the Blind Forest and Hyper Light Drifter.

The games recognize the controller well enough, and I get the chime when the game starts so I know it is loading the correct x_input dlls.

However, the mapping is completely screwed up. The face buttons don't match (ie everything works great in x360ce, but to get 'X' in game I press 'A' on the pad), which is easy enough to fix with a little remapping, but then I find that Start is mapped to RT, so the game is interpreting IHAxis3 as the Start button. The Start and Back buttons don't seem to do anything at all.

I've been scrambling trying to get something to work. If I can't get this figured out before Dark Souls 3 is released I'm likely to turn terribly violent in real life.

Any suggestions?
 
#220 ·
guys anyone got Mother Russia Bleeds to work?
i manage to get it to detect my gamepad but it also detect the keyboard as player one ,gamepad as player two and again keyboard as player three....!!!! disconnecting the keyboard doesn't help
it works with xinput1_3 X64
any help?
 
#221 ·
New compatible game:

Everspace (EA/Beta)

EVERSPACE.exe / RSG-Win64-Shipping.exe
xinput1_3.dll

x360ce_x64.exe must first be run/configured in the main EVERSPACE directory.
after configuration, copy the created x360ce.ini & xinput1_3.dll files into the EVERSPACE\RSG\Binaries\Win64 directory.
backup the existing xinput1_3.dll file in the EVERSPACE\RSG\Binaries\Win64 folder first if you plan on ever using a standard xinput device.
No HookMasks.
 
#222 · (Edited)
New compatible game:

Everspace (EA/Beta)

EVERSPACE.exe / RSG-Win64-Shipping.exe
xinput1_3.dll

x360ce_x64.exe must first be run/configured in the main EVERSPACE directory.
after configuration, copy the created x360ce.ini & xinput1_3.dll files into the EVERSPACE\RSG\Binaries\Win64 directory.
backup the existing xinput1_3.dll file in the EVERSPACE\RSG\Binaries\Win64 folder first if you plan on ever using a standard xinput device.
No HookMasks.

Hi, thanks for the report, I have still trouble to make it work, though. It seems that I can either perturb the whole xinput loading if the .dll and .ini files are NOT left in the main EVERSPACE directory or have no effect at all if the files are copied. I checked that with an Xbox controller with a modified layout. Nevertheless, my direct input "Black Widow" do not respond in any way within the game.

Any thoughts ?

EDIT :

I found the solution :

I needed to check the "DInput File" under 64-bit in order to make my settings apply... Not sure I understand the whole thing...
 
#223 ·
Glad you found a solution, the only thing I could think to try was maybe launching from the RSG-Win64-shipping.exe instead of everspace.exe, but it seems you just needed to set up the dll file correctly, which is tricky when first using x360ce. if you know its a 32 or 64 bit program you can just check every dll file in the list and it will create them all, but most will be unnecessary. The wiki (and this thread) shows which ones are needed specifically for which games though.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top