Next Generation Emulation banner
Not open for further replies.
1 - 2 of 2 Posts

Premium Member
5,082 Posts
Discussion Starter · #1 · (Edited)
"Xbox 360 Controller Emulator" allows your controller (gamepad, joystick, wheel, ...), function as "Xbox 360 Controller". For example, lets you play games such as "Grand Theft Auto" (GTA) or "Mafia II" using Logitech Wheel.
System Requirements

  1. Only Windows XP SP3 and newer systems are supported.
  2. .NET 3.5 (Also installs 2.0 and 3.5) (Included in Windows 7)
  3. .NET 4.0 (link to 4.5, also installs 4.0) (Included with Windows 8)
    • .NET 4.5 is not supported on Windows XP SP3, download .NET 4.0 from here.
  4. DirectX End-User Runtimes (June 2010) (Required regardless of OS)
  5. Depending on the DLL, either or both of the following
  • Windows 7 includes .net 3.5 and its updates to .net 2.0 and 3.0
  • For Windows XP and Vista, users can obtain it from the above link, and Windows 8 users can enable it in Programs and Features - Turn Windows Features on and off.
  • .Net MUST be installed prior to the DirectX webupdate as it checks that .Net 2.0/3.0/3.5 is installed and skips the Managed DirectX framework if it is not.
  • The full DirectX Redistributable will always install the file, however its best to have .net 3.5 installed anyhow as quite a few Xinput titles utilise .net for internal dependencies.

"Xbox 360 Controller Emulator" files:
xinput1_3.dll (Library) - Wrapper library that translates the XInput calls to DirectInput calls, for support old, no XInput compatible GamePads.
x360ce.exe - (Application) - Allows edit and test Library settings.
x360ce.ini - (Configuration) - Contain Library settings (button, axis, slider maps).
x360ce.gdb - (Game Database) Includes required hookmasks for various games)
Dinput8.dll - (DirectInput 8 spoof/wrapping file to improve x360ce compatibility in rare cases - So only use if instructed to!)



Run this program from the same directory as the game executable. Xinput library files exist with several different names and some games require a change in its name.

Known names:

  • xinput1_4.dll (Windows 8 only, for metro apps - not supported because it requires signing)
  • xinput1_3.dll
  • xinput1_2.dll
  • xinput1_1.dll
  • xinput9_1_0.dll
Game Database (GDB) and Configuration (Ini) files can be copied to %Allusersprofile%\X360CE on NT6 (Vista/7/8) or %Allusersprofile%\Application Data\X360CE on NT5.1 (XP), Or left in the same directory as the game executable (.EXE)

Games based on source engine in most cases have the dll placed inside the /Bin/ subfolder, as it it is loaded by inputsystem.dll instead of the game executable.


Delete x360ce.exe, x360ce.ini and all xinput dll from game executable directory.


Wheel doesn't work in the game, but it works inside x360ce Application.
Some games will only operate when the controller is considered to be the gamepad, even if it is the steering wheel. Try to:

  1. Run x360ce.exe
  2. Select tab with your Wheel Controller.
  3. Open [Advanced] tab page.
  4. Set "Device Type" drop down list value to: GamePad
  5. Click [Save] button.
  6. Close x360ce Application, run game.
How to reduce wheel dead zone (GTA, Mafia II, ...)?

  1. Run x360ce.exe
  2. Select tab with your Wheel Controller.
  3. Open [Advanced] tab page.
  4. Select "Enabled (XInput, 80%)" from "AntiDeadZone" drop down in order to reduce dead zone by 80%.
  5. Click [Save] button.
  6. Close x360ce Application, run game.
Note: Some games have control issues when the dead zone is reduced by 100%.​
Do I need to run x360ce Application during the game?
No, You do not need. Close x360ce during the game, because the game does not need it, and the application uses computer resources. The application is just a GUI for editing the x360ce.ini and test controller.

Warning - Configuration file version does not match x360ce version.
This occurs because the current version of the application is not completely compatible with the DLL just yet.
You can resolve this by adding Version=1 under the [Options] section in x360ce.ini

Controller tab won't turn green / Red light on Controller 1,2 etc.
This can occur for a number of reasons.

  1. The configuration utility DOES NOT work with the 64bit version of x360ce, it will only work with the 32bit version. This is the case regardless of whether your windows is 32bit or 64bit.
  2. The DInput state of the control might be incorrect due to previous application crashing and not unloading the control or some other reason. Opening up Joy.cpl (Set Up Usb Game Controllers) and clicking the Advanced button, and then Okaying out of the window that appears can fix it.
  3. The controller profile loaded may match the name of the control but not actually be for the controller you own - in this case you might see button numbers or axes mapped that do not appear in the joy.cpl test page.
  4. The controller profile might have PassThrough set. A growing number of profiles have been uploaded that do this, i have no idea why as it disables x360ce and just bloats the list of available profiles.
  5. There just might not be a profile for your control at all - The light should turn green once atleast the 2 sticks, triggers and Dpad are assigned. Sometimes the application needs to be restarted after assigning these for the light to turn green.
1 - 2 of 2 Posts
Not open for further replies.