Next Generation Emulation banner
1 - 19 of 64 Posts

Premium Member
5,486 Posts
Discussion Starter · #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).

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;
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.

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.​
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.
This enables the hooking of SetupAPI, only the BeatHazard titles are known to require it thus far, so it should almost never be needed.
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.
This allows the wrapper to trick some games that detect the controller GUID via DirectInput, The first Assassins Creed is one such title.​
This works in conjunction with FakePID= and FakeVID=
Without these, it defaults to the Wired Xbox 360 Controller which are 0x28E and 0x45E respectively.
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.

Premium Member
5,486 Posts
Discussion Starter · #2 · (Edited)
Does my game use XInput? Is it 32-bit or 64-bit? What xinput dll filename does it need?

This is how you can find out, for games not on the Game Compatibility List.

1. CTRL-ALT-DEL > Task Manager > Right click on application name > Select "Go To Process" to get name of process.
2. NB If 32-bit will have " *32" besides process image name, and needs 32-bit x360ce. Otherwise will need 64-bit x360ce.
3. In Task Manager > Performance Tab > Click on "Resource Monitor" to bring up Resource Monitor.
4. In Resorce Manager click on CPU tab. Locate name of process under "Processes" and click box to select.
5. Go to Associated Modules. Click on Module Name to sort alphabetically. Scroll down to see if any "C:\Windows\System32\xinput*.dll" are loaded. Note xinput dll name, and check it is in Windows\System32.
6. NB In "Resource Manager > CPU > Associated Modules" there may be two scroll bars, you have to scroll using both of these.

If you require additional help and information, please read the
x360ce Libraries Tutorial by resolutespider5

Premium Member
5,486 Posts
Discussion Starter · #23 ·
Game: FlatOut Ultimate Carnage
Version: File
Executable: fouc.exe (through launcher.exe)
My system: Dell Inspiron 15R SE (7520), Intel i7-3612QM, 8GB RAM, 2GB AMD Radeon HD 7730M / Intel HD 4000 graphics, 1920 x 1080 screen, 1 TB hard disk. MS Win7 Home Premium SP1 64-bit, DirectX 9.0c / 11, MS Visual C++ 2010/12 Re-distributable x86/x64, MS .Net Framework 4.5
Controller: Saitek P380 Controller.
Controller Driver: HID compliant game controller MS 21/06/2006 6.1.7601.17514
x360ce library: R642 32-bit (
x360ce library filename: xinput1_3.dll
Comments: Needs HookCOM. Also works with all hooks enabled, i.e. HookMask=0x0100003F

how is that P380 working for you?

because the P480 is having all sorts of problems with one of our users, his rumble only works properly in x360ce.exe and actually crashes in dinput8.dll when quitting games or the xinput sdk samples,
if he uses the 2007 windows cabinet driver it crashes HID.dll on exit

Premium Member
5,486 Posts
Discussion Starter · #35 ·
Hookmask Not Required

  1. Batman Arkham Asylum
  2. Batman Arkham City (uses xinput9_1_0.dll)
in the compatibility list

these are entirely Xinput titles, they don't need HookCOM.

NFS13 probably supports DirectInput wheels and force feedback, so hookcom was obvious.

Premium Member
5,486 Posts
Discussion Starter · #39 ·
my copy isn't the GOTY edition, so they may have changed something in the rerelease if thats what you have.

Either way, afaik neither version supports DirectInput at all So unless your control already is an Xbox 360 controller, HookCOM should not be necessary, and you should be using Durazno instead of X360CE.

Premium Member
5,486 Posts
Discussion Starter · #48 · (Edited)
That isn't Fifa 10 in the pending list ;) (edit, nvm, i saw it was listed under not working)

kudo's for reminding me to move Darksiders and Magicka though
if you have the filename.exe for Darksiders 2 that'd help me as well.

the gears and slambolt file names were never reported, thats why they aren't in the GDB.
1 - 19 of 64 Posts