Not every Switch-style controller comes from Nintendo. Version 7 of BetterJoy added an Add Controllers feature aimed at third-party Pro-style pads and Joy-Con alternatives — with the official summary’s own honest caveat that the support “is not perfect.” This guide shows how to add a third-party controller, how to calibrate one whose sticks or gyro behave oddly, and where the real limits are, so you know before you buy or troubleshoot.
First, a reality check on what “support” means
BetterJoy was written against Nintendo’s own hardware. Third-party controllers imitate that hardware to varying degrees: they may use different Bluetooth identifiers, different polling behaviour, and differently scaled sensors. That is why the v7 release notes tell you to check the project’s issues tab for hints, tips, and tricks for specific models, and why the release provides config-file calibration values (covered below) instead of promising one-size-fits-all support. Some models will work beautifully, some will work with quirks, and a few — certain PowerA models are a long-running example in the issue tracker, reported across years as connecting to Windows but not appearing in BetterJoy — may not be recognised at all. That is the honest landscape.
If you have not installed BetterJoy yet, start with the first-run guide; the package is on the download page.
Step 1: Pair the controller with Windows
A third-party pad joins Windows the same way Nintendo’s does: put it into pairing mode (on most Pro-style pads, hold the Sync button until the lights cycle — check the pad’s own manual for its exact button), then add it under Settings → Bluetooth & devices → Add device → Bluetooth. USB also works on pads that offer a wired mode. The controller needs to be visible to Windows before BetterJoy can do anything with it; our Pro Controller connection guide covers the Windows-side flow and the remove-and-repair fix in detail.
Step 2: Use the Add Controllers button
- Run BetterJoyForCemu.exe with the third-party controller connected.
- Click the Add Controllers button in the BetterJoy window — this is the v7 feature built specifically for hardware BetterJoy does not recognise automatically.
- Add your controller through that flow and confirm it appears as an icon in the main window.
- Choose the output you need (XInput is the compatible default, DS4 for tools that expect it) and test buttons and sticks in your game or emulator’s input settings.
Step 3: Calibrate in the config file if the motion feels wrong
The classic third-party symptom is a gyro or stick that is technically working but scaled wrong — aim that flies across the screen, or barely moves. The v7 release notes document the fix: you can change the default calibration for a third-party controller in the config file, via the acc_sensiti… (accelerometer) and gyr_sensiti… (gyroscope) values in BetterJoyForCemu.exe.config.
Work methodically: back the file up, change one sensitivity value by a small step, relaunch, and test in a practice screen. Our config file guide covers safe editing and the other documented keys.
What to check when a third-party pad refuses to appear
- It is awake and really connected. If Windows itself loses the device, BetterJoy never had a chance — fix the Windows connection first.
- Its mode. Many multi-mode pads can present as different device types (XInput, Switch-style, etc.). BetterJoy’s Add Controllers path is for pads presenting as Switch-style controllers; a pad locked into XInput mode is already a PC controller and does not need BetterJoy at all.
- The project’s issues tab. The release notes explicitly point there for per-model hints — search it for your controller’s name before assuming yours is a new problem.
- Expectations. If your exact model has open “not detected” reports spanning years, software settings are unlikely to rescue it; that pad is better used in its native XInput mode or replaced.
Buying advice if you have not purchased yet
If you are shopping for a cheaper Pro-style pad specifically to use with BetterJoy, manage your risk: buy from a seller with easy returns, and test the pad on the day it arrives — pair it, run Add Controllers, and check the gyro in a game, not just the buttons. The failure mode that matters (Windows sees it, BetterJoy does not) shows up immediately, so a returns window is all the insurance you need. Players who mainly want guaranteed gyro behaviour on PC are still best served by Nintendo’s own Pro Controller or Joy-Cons, where support is documented rather than hoped for; third-party pads earn their discount by trading certainty for price.
Also keep receipts of a different kind: if you do get an obscure pad working, note the sensitivity values that fixed it. Clone hardware varies even within one model name, and your working numbers are the first thing another owner of the same pad will search for in the issue tracker.
Frequently asked questions
Will my specific controller work?
Nobody can promise that — not us, and notably not the project itself, which calls the support imperfect. The practical test is cheap: pair it, open Add Controllers, and see whether it appears and responds. The calibration values fix scaling quirks; they cannot fix a pad BetterJoy cannot see at all.
Does this also apply to the maintained fork?
The community fork of BetterJoy states it has only tested official Nintendo Pro Controllers and Joy-Cons — third-party pads are untested there. For clone controllers, the original v7 line with Add Controllers is the documented route.
Can I use a third-party Joy-Con pair as one controller?
If both halves are added and recognised, the same join/split behaviour applies as with Nintendo Joy-Cons — clicking the icons toggles joint mode. Recognition is the hurdle; joining is the easy part.
Where are the other tutorials?
The tutorials index lists all our BetterJoy guides.