x360ce
Primary repository for the x360ce library, front-end and tools.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/x360ce/x360ce with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/x360ce/x360ce'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/x360ce--x360ce)HTML
<a href="/listings/x360ce--x360ce"><img src="/api/listings/x360ce--x360ce/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.MD · README · 266 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- "Xbox 360 Controller Emulator" allows your controller (gamepad, joystick, wheel, etc.) to function as an Xbox 360 controller. For example, it lets you play games such as "Grand Theft Auto" (GTA) or "Mafia II" using a Logitech Wheel.
- IMPORTANT: Please download and run digitally signed files only! If someone asks to disable antivirus or exclude X360CE app from anti-virus - DON'T! Report any suspicion in [Issues](https://github.com/x360ce/x360ce/issues) and we will try to resolve any false positive with anti-virus developers.
- Every signed build is published on the [Releases page](https://github.com/x360ce/x360ce/releases).
- # Download v4.x
- Digitally Signed Application and Virtual Gamepad Emulation Bus 1.21.442.0 on Windows 10 and later, or 1.16.112.0 on older Windows
- Download `x360ce.zip` from the [latest v4 release](https://github.com/x360ce/x360ce/releases) - for All games
- Note: version 4.x use Virtual Gamepad Emulation. Instructions can be found here: [Help.v4](docs/Help.v4.md)
- ## Mapping formulas (v4.x)
- A mapping row can hold a formula instead of a single control. Press the small `fx` button beside
- the row and type one, starting with `=`.
- =a5*2 double the trigger, so it reaches full at a half press
- =a1*0.5 halve the stick, for aiming through a scope
- =a1*abs(a1) fine control near the centre, full speed at the edge
- =max(a1,0) use only one half of a pedal axis
- Sources are written the way mappings are stored: `a1` is axis 1, `b2` is button 2, `s1` is
- slider 1. An axis reads from -1 to 1 when it drives a stick and from 0 to 1 when it drives a
- trigger, matching what the row already did. `now` reads the milliseconds since the program
- started; divide it by 1000 for seconds or by 60000 for minutes.
- The formula takes effect as it is typed, so a number can be adjusted and the difference felt at
- once. The `fx` button says whether it works: green while the formula is understood and driving
- the row, red while it is written down and not. Point at a red one to read what is wrong with it.
- A formula replaces the dead zone, anti dead zone and sensitivity for its row rather than being
- applied on top of them.
- **A formula is limited to 128 characters**, which is the width a mapping is stored in.
- The Help page lists every operator, function and source.
- ## Where settings are kept (v4.x)
- Settings live in `C:\ProgramData\X360CE\Settings`. Anyone may create a file there, but only
- the account that created it may change it afterwards, so on a shared computer a second user can
- find the settings read-only.
- Open **Options** then **Settings** to see the folder in use and to choose another one. Your own
- user folder, `%LOCALAPPDATA%\Jocys.com\X360 Controller Emulator`, belongs to you alone and cannot be locked by
- another account. The settings you already have can be moved with it: every file is copied and
- checked against the original, and nothing is removed unless all of them match.
- If saving ever fails, the program says so and offers to try again or to move to your own folder.
- ## Force feedback pass through (v4.x)
- An Xbox controller offers its motors through XInput and nowhere else, so a game's rumble cannot
- be sent back to it the way it is sent to other controllers. **Force Feedback Pass Through**, on
- the Force Feedback tab, hands the rumble to a real controller instead.
- Leave the destination on **Auto (Real)** to use the real controller behind the mapping, or choose
- **XInput 1** to **4** to name one yourself.
- The Test sliders drive the same path a game does, pass through included, so the destination can be
- checked without starting a game.
- ## Wheel centering spring (v4.x)
- A game made for a gamepad sends only rumble, so a wheel turns freely between bumps. The **Wheel**
- tab of a controller holds the wheel at its centre the way a car's steering does: the force grows
- from the centre to a peak, then eases off towards the stop. Pick a car from the **Car** list, or set
- **Centre**, **Peak**, **Lightening**, **Damping** and **Speed** yourself; a chart shows the force at
- every angle, and its dot follows the wheel as it turns. With hands off the wheel, **Auto** measures
- the wheel's friction and sets **Strength** to beat it.
- [How a real car centres its steering wheel](docs/Help.WheelCentering.md) says what each setting
- copies from a real car, with the measurements and standards behind it.
- ## Plugins (v4.x)
- A plugin adds a device x360ce cannot read by itself, or one that exists only in code, such as a
- controller fed over the network. It is one DLL built from one `.cs` file with `dotnet build`, put into
- a folder of its own in the **Plugins** folder of the x360ce data folder, where it loads at once. Plugins signed by the
- publisher of x360ce load by themselves; others wait for **Allow third-party plugins** on the
- **Options** tab's **Plugins** page, which lists every plugin and why one did not load. The Test
- Controller, a pretend controller for trying a mapping without hardware, is a plugin inside x360ce:
- **Add Plugin Device** on the **Devices** tab adds it. `x360ce.exe /PluginKit=<folder>` writes a
- folder to start a plugin in. [Plugins](docs/Help.Plugins.md) says how to write one.
- ## Putting controllers in order (v4.x)
- The **XInput Devices** page can move a controller to a different place, for games that read only
- the first one. Switching a real controller off and on again needs Administrator, so the program
- starts one elevated copy for that step and closes it again. Anything it switches off is written
- down first, so a run that is interrupted is undone at the next start.
- ## AI assistants (v4.x)
- x360ce has no AI inside. If you use an AI assistant of your own, it can map and tune your controllers for you, through the program's own AI assistant access rather than your screen, mouse or keyboard. It is off until you switch it on, on the Options tab's AI page. [AI assistants](docs/Help.AiAssistants.md) starts with a worked example and how to check what the assistant did, then shows how to set it up, ChatGPT on the web included.
- > **For AI assistants and agents.** Both programs describe themselves; read these rather than
- > guessing: [skills/x360ce](skills/x360ce) is the skill, and its `references/` hold the help and
- > every control with its purpose for each program, written by the programs
- > ([ui-tree-v4.md](skills/x360ce/references/ui-tree-v4.md),
- > [ui-tree-v3.md](skills/x360ce/references/ui-tree-v3.md); `x360ce.exe /Skill` prints the copy for
- > the version you run); [docs/Help.v4.md](docs/Help.v4.md) and [docs/Help.v3.md](docs/Help.v3.md)
- > are the help each program shows; [AGENTS.md](AGENTS.md) holds the rules for working on the code. To operate a running copy, register `x360ce.exe /Mcp`
- > as an MCP server or call `x360ce.exe /Ai=<tool>`; both need AI assistant access switched on in
- > the program's Options, where it is off by default.
- # Download v3.x
- Digitally Signed Application and Libraries
- Download `x360ce_x86.zip` from the [latest v3 release](https://github.com/x360ce/x360ce/releases) - for 32-bit games
- Download `x360ce_x64.zip` from the [latest v3 release](https://github.com/x360ce/x360ce/releases) - for 64-bit games
- DInput.dll Plugin (required for some games):
- The 32-bit and 64-bit plugin is built from `Native/dinput8` and embedded in `x360ce.exe`. It is no longer kept as a committed binary, so there is no separate file to download for it.
- # Reporting Issues
- **!!! Denuvo protected games are not supported !!!**
- List of denuvo protected games is [here](https://en.wikipedia.org/wiki/Denuvo#List_of_Denuvo_games)
- Report only crashes or other bugs, note that the Issue tracker is not a help desk!
- **DO NOT ASK FOR HELP IN INSTALLATION OR CONFIGURATION!!!**
- **If you have questions about installation or configuration, please go to our [forum @NGemu - x360ce](http://www.ngemu.com/forums/x360ce.140)**
- # Compatibility
- Version 3 works inside each game, and some games need a HookMask: see [What do HookMasks do?](docs/Help.v3.md#what-do-hookmasks-do)
- # System Requirements
- 1. Windows 10 or newer.
- 1. [.NET Framework 4.x](http://www.microsoft.com/en-us/download/details.aspx?id=48130) (included in Windows 10 and 11)
- 1. [DirectX End-User Runtime (June 2010)](http://www.microsoft.com/en-us/download/details.aspx?id=8109) (required regardless of OS)
- 1. Microsoft Visual C++ v14 Redistributable (Visual Studio 2017–2026): [x86](https://aka.ms/vc14/vc_redist.x86.exe) and [x64](https://aka.ms/vc14/vc_redist.x64.exe) (**for x64 systems install both x86 and x64 redistributables**)
- Notes:
- * Most game's executables are 32-bit and require x86 x360ce and also the x86 redistributable.
- # Files
- xinput1\_3.dll (Wrapper Library) - Translates XInput calls to DirectInput calls - supports old, non-XInput compatible GamePads.<br />
- x360ce.exe - (Application) - Allows for editing and testing of Library settings.<br />
- x360ce.ini - (Configuration) - Contain Library settings (button, axis, slider maps).<br />
- x360ce.gdb - (Game Database) Includes required hookmasks for various games).<br />
- Dinput8.dll - (DirectInput 8 spoof/wrapping file to improve x360ce compatibility in rare cases).<br />
- # Installation
- 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 / metro apps only)
- * 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 be left in the same directory as the game's executable (.EXE)
- Note:
- * In most cases games based on the Source engine have the DLL placed inside the /Bin/ sub folder, as it is loaded by inputsystem.dll instead of the game executable.
- * The DLL is not currently fully supported by the App, recent versions incorporate HookMasks and fully remove HookModes, and requires placing Version=1 under [options] in the x360ce.ini to quieten a warning about incorrect version.
- # Uninstallation
- Delete x360ce.exe, x360ce.ini and all XInput DLLs from the game's executable directory.
- ## Important for version 4.x
- Close the program from its own window. It removes the virtual controller while it shuts down. If the program is ended from Task Manager or crashes, the virtual controller is left behind, and Windows can be left unsure which controllers you have.
- HID Guardian can no longer be installed. If an older version installed it, remove it from within the program rather than deleting its files by hand.
- ### How to remove HID Guardian if access to your Mouse and Keyboard is lost (X360CE v4.x)
- Instructions: [How to Uninstall HID Guardian When Access to Keyboard and Mouse is Lost](docs/Help.HidGuardian.md#how-to-uninstall-hid-guardian-when-access-to-keyboard-and-mouse-is-lost)
- # Troubleshooting
- Some games have control issues when Dead Zone is reduced to 0%.
- You may need to increase the Anti-Dead Zone value if there is gap between the moment when you start to push the axis-related button and the reaction in game.
- **Wheel doesn't work in the game, but it works inside x360ce Application.**
- Some controllers will only operate in game if they are set as "GamePad". Try to:
- 1. Run x360ce.exe
- 2. Select the [Controller #] tab page corresponding to your controller.
- 3. Open [Advanced] tab page.
- 4. Set "Device Type" drop down list value to: GamePad.
- 5. Click [Save] button.
- 6. Close x360ce.exe.
- 7. Run the game.
- Only one controller, mapped to PAD1, may work correctly in some games.
- In v3.x, try to:
- 1. Run x360ce.exe
- 2. Select the [Controller #] tab page corresponding to your controller.
- 3. Open the tab page named after your device (visible when the controller is connected).
- 4. Set "Map To" drop down list value to: 1.
- 5. Set "Map To" drop down list values *(repeat steps 2. to 4.)* for other controllers, if you have them, to: 2, 3 or 4.
- 6. Click [Save] button.
- 7. Close x360ce.exe.
- 8. Run the game.
- In v4.x, "Map To" is gone and the [XInput Devices] page puts controllers in order instead. See
- "Putting controllers in order" above. Configuration files written by v3.x keep their "Map To"
- value untouched.
- To use more than one controller in game, you may need to combine them. Try to:
- 1. Run x360ce.exe
- 2. Select the [Controller #] tab page corresponding to a controller you want to combine.
- 3. Open the [Advanced] tab page.
- 4. Set "Combine Into" drop down list value to: One, and tick "Combine this controller" *(repeat steps 2. to 4. for each controller to combine)*.
- 5. Select [Options] tab page.
- 6. Check "Enable Combining" check-box. *(Note: Uncheck "Enable Combining" check-box when you want to configure the controller.)*
- 7. Click [Save] button.
- 8. Close x360ce.exe.
- 9. Run the game.
- **Do I need to run x360ce Application during the game?**
- The x360ce.exe application can be closed before launching the game; the game doesn't need it and it uses your computer's resources. The x360ce.exe application is just a GUI for editing x360ce.ini and testing your 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 64-bit library, it will only work with the 32-bit version, This is the case regardless of whether your Windows is 32-bit or 64-bit.
- 2. The DInput state of the controller might be incorrect due to an application crashing previously and not unloading the controller 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 controller 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 at least once the 2 sticks, triggers and D-pad are assigned. Sometimes the application needs to be restarted after assigning these for the light to turn green.
- In v4.x the light is drawn in two halves: your own device on the left, the emulated controller on
- the right, so it says which half is missing. Grey means nothing is set up, green means the game is
- receiving what you press, and it reddens as more is wrong at once. Orange means the controller
- works but sits in a different XInput place than its tab number, which the [XInput Devices] page can
- put right. The Help page lists every combination.
- # Screenshots
- Mapping a controller. Each Xbox control on the right names the button or axis on your own
- controller that drives it, and the fx button beside it turns that mapping into a formula.
- 
- Tuning a thumb stick. The curve shows what the game receives for how far you push, so a dead
- zone, an anti-dead zone and a sensitivity change can be seen before the game is started.
- 
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.