x360ce's release tags drop two digits from the version, and it asks you never to disable your antivirus
Primary repository for the x360ce library, front-end and tools.
At a glance
- What is it?
- A controller translation tool that makes a wheel, joystick or gamepad present itself as an Xbox 360 pad, shipped as two major lines from one repository. The trust posture is unusually explicit, the settings folder has an ownership problem the program solves, and the application can register itself as an MCP server.
- Who is it for?
- Fit this if you have a controller the game does not recognise, most often a steering wheel, and you want the game to see a console pad rather than to remap its controls. The tool is a translation layer, not an emulator of anything else, and the v4 line works through a virtual gamepad bus while v3 works through a wrapper library, so the two lines are different approaches rather than versions of one.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- x360ce/x360ce2,949 ★ · +32
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| x360ce/x360ce | 2.9k | 2.9k |
32 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Every release tag drops the last two digits of the version
The tag and the release name disagree in all three of the visible releases, and always in the same direction.
The tag `4.24.0.0` carries the release name `X360CE 4.24.60.0`. The tag `3.5.0.0` carries `X360CE 3.5.10.0`. And the tag `4.23.0.0` carries `X360CE 4.23.59.0`.
So the tag keeps the first two components and zeroes the rest. The application version you read in the interface, and the number in the download instructions, is not the tag. If you pin a build, you have to know which of the two you are pinning.
The other thing the release list shows is that the two major lines ship side by side. Two of the three tags were published on the same day, 2026-10-02, about a minute apart, one from the 4.x line and one from the 3.x line. The day before, a 4.x tag. So the 3.x line is not a frozen branch waiting to be retired; it is still being cut.
The download instructions confirm it, giving a signed 4.x application version alongside a separate signed 3.x application version, and telling you to take the 4 archive for all games while the 3 line needs one archive or the other depending on the bitness of the game.
The repository was last pushed on 2026-10-02, the same day as two of those three releases, and it is not archived.
The project tells you never to exclude it from antivirus
One paragraph near the top of the document is the most unusual instruction in it, and it is worth reading exactly as written.
It asks you to download and run digitally signed files only. Then it says that if somebody asks you to disable antivirus or to exclude the application from it, do not, and to report any suspicion through the issue tracker, with the promise that false positives will be taken to the antivirus developers. Every signed build is published on the releases page.
That is the reverse of the posture most tools that touch input drivers take, where the documentation quietly includes a step about exclusions. Here the exclusion step is the thing being warned against.
The rest of the document is consistent with it. Download instructions name an exact signed application version and, for the current line, an exact driver version. The compatibility section points at a wiki page rather than asserting which games work. And the files section describes the components by role, starting with a wrapper library that translates one input API into another so that old pads which do not speak the newer API at all can be used.
So the trust argument rests on three things a reader can check independently: whether a download is signed, whether it came from the releases page, and whether the antivirus complaint was raised as an issue. None of that requires believing the project.
The two lines are different architectures, and v4 ships a driver
Reading the two download sections side by side explains why both lines exist.
The current line is a single archive named for all games. It needs a signed application, version 4.24.60.0 in the instructions, plus a Virtual Gamepad Emulation Bus, given as one version for Windows 10 and later and a different, older one for earlier Windows. The README also says the current line uses virtual gamepad emulation and points at a wiki page for the instructions.
The previous line is two archives, one for 32-bit games and one for 64-bit games, with a signed application version and a separate libraries version. Its optional DirectInput plugin is described as built from a native source directory and embedded into the executable, and then: it is no longer kept as a committed binary, so there is no separate file to download for it.
That last sentence is the clearest statement of a build practice in the whole document. A file that used to be checked into the repository is now produced by the build, which removes a binary from version control and moves the risk to whoever runs the build.
The driver split by operating system is the other wrinkle. The stated requirement is Windows 10 or newer, yet the driver is given in two versions keyed to that boundary, so the older one covers machines below the documented requirement.
Together with the note that most game executables are 32-bit, the practical advice is that the previous line's 32-bit archive is the one most people need, and the current line removes that choice.
A mapping row can hold a formula, and it replaces the dead zone
The current line lets a mapping be an expression instead of a single control, which is the most interesting thing in the document.
Press the small button beside a row, marked `fx`, and type a formula that starts with an equals sign:
=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 axisThe sources are written the way mappings are stored, so a letter and a number: `a` for axis, `b` for button, `s` for slider. One detail matters for anyone writing one: an axis reads from minus one to one when it drives a stick and from zero to one when it drives a trigger, which is what the row was already doing. There is also a source that reads the milliseconds since the program started, with a note on dividing by a thousand or by sixty thousand.
Three behaviours are documented that you would not guess. The formula takes effect as it is typed, so a number can be adjusted and the difference felt immediately. The button shows whether it works, green while the formula is understood and driving the row, red while it is written down and not, and pointing at a red one reads the error. And a formula replaces the dead zone, the anti dead zone and the sensitivity for its row rather than being applied on top of them, so the three settings and the formula are mutually exclusive for that row.
The limit is where the storage format shows through the interface: a formula is capped at 128 characters, which is the width a mapping is stored in.
Settings live in a folder a second user cannot write to
The current line stores its settings in a location whose ownership rule creates a specific failure mode, and the documentation addresses it directly.
Settings live in a folder under the ProgramData directory. Anyone may create a file there, but only the account that created it may change it afterwards, which means that on a shared computer a second user can find the settings read-only and unable to save.
The alternative is a per-user folder under the local application data directory, in a directory named after the publisher's domain, which belongs to that user alone and cannot be locked by another account. Both locations are visible and selectable from Options, then Settings, which is where the program shows the folder currently in use.
Migration between them is described with the care this deserves. Every file is copied and then checked against the original, and nothing is removed unless all of them match. And if saving ever fails, the program says so and offers to try again or to move to the user folder, rather than failing silently.
This is a small feature and it is the kind of thing that only gets written down after somebody has hit it, because the default location is the shared one and the ownership rule is enforced by the operating system rather than by the program.
The application can register itself as an MCP server
One block in the document is written specifically for automated assistants, and it describes two ways to drive the program from outside.
The first point is documentation: both programs describe themselves, so instead of guessing, read the generated interface tree files for each line, which list every control with its purpose and are written by each program, and the help files, which are the help each program shows. Those files can be regenerated by the executable with a switch that takes an output directory. A separate document holds the rules for working on the code.
The second point is control. To operate a running copy, you register the executable as an MCP server, or you call one tool at a time through a different switch that takes a tool name. Both require an assistant access option to be switched on in the program's Options, where it is off by default.
The tree is consistent with that framing. There are two application directories, one per major line, and four entries at the top level whose purpose is to be read by an assistant rather than by a person: two directories, an agents file and a Claude file.
Also present is a directory named after a well known Windows hooking library with an update script beside it, which is the pattern for keeping a vendored native dependency current, plus the newer XML solution format alongside a spell dictionary for it, and two PowerShell scripts, one enforcing the git attributes file and one cleaning the solution.
The issue tracker is explicitly not a help desk
The reporting section is short and uses capital letters, which tells you what has happened there before.
It asks for crashes and other bugs only, states that the issue tracker is not a help desk, and then states in capitals that help requests about installation or configuration are not wanted there either, directing those to a forum instead.
For a tool whose entire user surface is configuration, that is a deliberate division rather than unfriendliness. Configuration questions are the ones with unbounded variation and no code to fix; crashes are the ones with a stack trace attached. The forum link is named as the destination for the first kind.
There is also a scope boundary stated in capitals a few lines earlier: Denuvo protected games are not supported, with a link to a published list of them. That is a licensing position rather than a technical one, and putting it in capitals alongside the crash policy means the boundary is meant to be read before anyone files an issue.
Compatibility is handled the same way. The document does not claim which games work; it points at a compatibility page on the project wiki and a second page for reporting results.
The files section at the end describes three components and then stops partway through the third, in the middle of a list of what the configuration file holds.
Editorial conclusion
Fit this if you have a controller the game does not recognise, most often a steering wheel, and you want the game to see a console pad rather than to remap its controls. The tool is a translation layer, not an emulator of anything else, and the v4 line works through a virtual gamepad bus while v3 works through a wrapper library, so the two lines are different approaches rather than versions of one. Four things to check before you install. Which line you want, since both are published in parallel and they differ in architecture rather than in features. Where your settings will live, because the default location can end up owned by a different account than the one you are logged in as. Which archive to download, since v4 ships one file for all games while v3 needs the 32-bit or the 64-bit one and most games are 32-bit. And whether you can get your content through the driver's rumble path at all, because force feedback only reaches a real controller through a pass-through setting and a test slider rather than automatically.
Frequently asked questions
Is x360ce safe to use?
The project asks you to download and run digitally signed files only, says every signed build is published on its releases page, and tells you not to disable antivirus or exclude the application if anyone asks you to. It asks that any suspicion be reported as an issue so false positives can be raised with antivirus developers.
Is x360ce still being updated?
Yes. Three recent releases are visible, two of them published on the same day in October 2026, one from the 4.x line and one from the 3.x line, and the repository's last push is dated 2026-10-02. The releases page is where the signed builds are published.
What games are compatible with x360ce?
The repository does not host a list. It points at a compatibility page on the project wiki and a second page for reporting results, and it does state that Denuvo protected games are not supported, linking to a published list of them.
What does x360ce v4 require that v3 does not?
Version 4 uses virtual gamepad emulation and needs a Virtual Gamepad Emulation Bus, given as version 1.21.442.0 on Windows 10 and later or 1.16.112.0 on older Windows, and it downloads as one archive for all games. Version 3 ships a separate 32-bit or 64-bit archive and no longer keeps its DirectInput plugin as a committed binary, because it is built from source and embedded in the executable.
Where does x360ce store its settings and who can change them?
In a folder under the ProgramData directory, where anyone may create a file but only the creating account may change it afterwards, so a second user on a shared computer can find it read-only. A per-user folder under the local application data directory cannot be locked by another account, and moving settings there copies every file and checks it before removing anything.
Can an AI assistant drive x360ce?
The application can register itself as an MCP server, or expose a single tool through a command line switch, and both require the assistant access option to be switched on in the program's Options, where it is off by default. The repository also ships generated files listing every control with its purpose, which the program writes itself.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/x360ce-x360ce)Star history chart for your README
[](https://hysenlabs.com/projects/x360ce-x360ce)Was this useful?