Let’s be precise from the first line, because this page exists to prevent a misunderstanding: the software described here is d3xMachina/BetterJoy, a community fork of Davidobot’s BetterJoy. It is not an official release, Davidobot did not publish it, and its v8.x version numbers do not continue the official line, which ended at v7.1 in 2021. What it is: the only BetterJoy descendant with verifiable, current releases — a maintained fork that modernises the runtime and replaces the most outdated bundled components. This guide states what we verified, who it suits, and where the conservative choice still wins.
What we verified (October 2026)
| Item | Verified fact |
|---|---|
| Project | Community fork by GitHub user d3xMachina of Davidobot/BetterJoy — not the original author’s release |
| Latest release | v8.5.0a, 29 June 2026 (following v8.5.0, 24 June 2026) |
| Download asset | BetterJoy.zip, 10,801,657 bytes |
| SHA-256 (published by GitHub for the asset) | c54c44d930e0756aee3630daac57fc4278f9e7c144772f3b170fe89fa2a925bc |
| Runtime generation | .NET 10 (the original v7.1 is a .NET Framework-era build) |
| Device hiding | Ships HidHide 1.5.230 instead of the legacy, discontinued HIDGuardian |
| Virtual gamepad driver | Bundles ViGEmBus 1.22.0 (the final ViGEmBus release) |
| Extra hardware | Adds NES and N64 controller support alongside Pro Controller, Joy-Cons and the Switch SNES pad |
Two of these rows matter more than the rest. The original v7.1 ZIP bundles a 1.16.x-era ViGEmBus MSI and HIDGuardian, a hiding layer its own author discontinued years ago; the fork brings both components to their final, modern forms. And unlike Davidobot’s older releases, GitHub publishes a SHA-256 digest for the fork’s asset, so the file is checkable against the value above — the same verification habit we recommend in Is BetterJoy Safe?
What the fork actually changed
Beyond swapping the bundled drivers, the fork’s own changelog describes a maintenance pass over the original code: a long list of crash and disconnect fixes, stick calibration controls, and deadzone/range adjustments that can be set per stick — things v7.1 users otherwise handle inside each emulator. The runtime move matters for longevity as much as features: v7.1 is a .NET Framework-era binary from 2021, while the fork builds on .NET 10, which is the generation Microsoft currently services. None of this makes the fork “BetterJoy 2” — it is the same mapper idea, carried forward by a different maintainer with a modern toolchain — but it explains why the fork exists at all: the original’s components (HIDGuardian discontinued, ViGEmBus retired at 1.22.0, .NET Framework frozen) each reached end-of-life while the controllers people use did not.
One boundary is worth repeating in this section because fork coverage elsewhere blurs it: the fork’s controller support is the original Switch family plus the retro pads. Its README’s testing notes centre on official Pro Controllers and Joy-Cons. It does not add Switch 2 support, and it does not promise broader third-party pad support than the original — by the maintainer’s own account, less testing has happened there, not more.
Download the fork
Download the community fork on GitHub (d3xMachina, v8.5.0a)
The button goes to the fork’s own GitHub release asset — no mirror, no wrapper. Prefer the known quantity instead? The conservative choice remains the official v7.1 download, Davidobot’s own release, and nothing on this page should be read as talking you out of it.
Who should try the fork
- You hit the original’s age. If v7.1’s legacy driver stack gives you trouble — especially anything involving HIDGuardian, which also conflicts with HidHide if both end up installed — the fork starts from the modern components (our double-input guide explains the HidHide approach).
- You want the extra controllers. NES and N64 pad support exists only in the fork line.
- You value current maintenance. The fork shipped releases in mid-2026; the original’s last push was July 2024. If a Windows update breaks something tomorrow, the fork is the line that can plausibly answer.
- You’re willing to test newer builds. The “a” in v8.5.0a is a fix-up release four days after v8.5.0 — normal for an active project, and a reminder that this line moves.
Who should stay on v7.1
- Your setup already works. v7.1 has been the stable reference for five years and about 1.75 million downloads of its ZIP. Don’t migrate a working rig on curiosity alone.
- You follow guides literally. Most tutorials, forum answers and our own tutorials hub describe v7.1’s menus and config file; the fork’s newer build may differ in details.
- You use third-party controllers. The fork’s maintainer notes testing focused on official Pro Controllers and Joy-Cons; third-party pads are the original line’s documented feature (v7’s Add Controllers), and even there, results vary by model.
- You don’t want a moving target. A dormant program never surprises you; an LTS fork occasionally will.
Before you switch
Don’t run both lines into the same driver stack. If you move to the fork, first remove the original cleanly — our uninstall guide covers the ViGEmBus MSI and the HIDGuardian remnants — then install the fork’s bundled components. Above all, never leave HIDGuardian and HidHide on the same system: Nefarius’ own guidance says the two must not coexist, and the fork shipping HidHide is a reason to make sure the old layer is really gone. And keep the fork’s identity straight when you read about it elsewhere: v8.x = d3xMachina’s community fork; v7.1 and below = Davidobot. The version history keeps the two lines visually separate for exactly this reason.
Frequently asked questions
Is the fork official?
No. It is an independent community fork by d3xMachina, built from Davidobot’s MIT-licensed source. It is legitimate to use and link — MIT allows forking — but it is not endorsed by, or a release of, the original author.
Does the fork support Switch 2 controllers?
No. Its controller list is the original Switch family plus NES/N64 pads. Switch 2 controllers use a different protocol entirely — see the Switch 2 answer.
Can I keep v7.1 and the fork side by side?
The programs themselves are just folders, but their driver and hiding layers overlap (ViGEmBus, HIDGuardian vs HidHide). Treat it as one installation or the other, and uninstall cleanly when switching.
More context in the Versions & Trust hub.