One Joy-Con feels instant and the other trails behind; inputs arrive late, in bursts, or with jitter that makes aiming impossible. With BetterJoy, Bluetooth lag is rarely the program’s fault — the project’s own wiki sets the tone: “you need a decent Bluetooth adapter that is comfortable with handling 3/4 connections at a time.” Two Joy-Cons plus a Pro Controller is three simultaneous connections before anything else joins. This page works from the most specific documented cause (an Intel driver version) outward to the adapter question, so you change one variable at a time.
Check 1: Your Intel Bluetooth driver version
This is the rare lag fix with an exact number attached. In issue #731, a lagging secondary Joy-Con on Dolphin was fixed by updating the Intel Bluetooth driver from Intel’s website — the threshold in that report was a driver older than 22.180.0. Windows Update routinely serves older Bluetooth drivers than Intel’s own download center, so “my drivers are up to date” inside Windows often isn’t. If your PC uses Intel wireless (most laptops and many motherboard modules do), download the current Bluetooth driver package from Intel directly, install, reboot, and retest before buying anything.
Check 2: Which controller lags — and the author’s blunt diagnosis
Issue #571 describes the classic shape of this problem: with two Bluetooth controllers, the one that synced first carried almost a second of delay. The author’s reply was blunt — “joycons natively don’t like Intel drivers/BT adapters” — and in the same discussion, a user solved their setup with an Asus USB-BT400 USB adapter. Two lessons: the chipset and driver stack matter more than the Bluetooth version number printed on the box, and “the first-paired controller lags” is a known pattern, not something you imagined. A quick diagnostic: disconnect both controllers, pair only the lagging one, and play. If it is fine alone, your adapter or driver is struggling with multiple connections — exactly the wiki’s 3–4 connection warning — and no BetterJoy setting will change that.
Check 3: Rumble load on the same link
Rumble data travels over the same Bluetooth connection as your inputs and motion samples, and heavy rumble makes everything else queue behind it. The pattern is documented: in issue #616 the console errors began after about 20 minutes with rumble enabled, while rumble-off sessions ran for hours (see our duplicate timestamp guide). The practical fix costs nothing: reduce rumble intensity in your emulator — the long-standing guidance for Cemu is around 70–80% — and see whether the lag follows the rumble setting. Older BetterJoy versions also carried a genuine rumble-lag bug fixed in v6.1, so if you are on an ancient build, updating comes first.
Check 4: Adapter placement and interference (community practice)
These steps are standard Bluetooth troubleshooting rather than BetterJoy-specific documentation, and they fix a surprising share of cases:
- Move the adapter (or your PC) so the controller has line-of-sight within a couple of metres; a rear motherboard antenna behind a metal case is the worst common setup.
- If you use a USB Bluetooth dongle, put it on a front port or a short USB extension cable — away from USB 3.0 hubs and external drives, which are known to radiate interference in the 2.4 GHz band.
- Disconnect other Bluetooth devices (headphones, phones, a second pair of Joy-Cons) for one test session to see if the lag is contention.
- For a Joy-Con pair, make sure both were paired separately and appear individually in BetterJoy before joining them, per the Joy-Con connection guide.
When a dedicated USB Bluetooth adapter is the real fix
If the Intel driver is current, rumble is tamed, placement is good, and a pair of Joy-Cons still lags while a single controller is fine, you have hit the adapter’s connection ceiling. That is a hardware limit, and the honest fix is a decent dedicated USB Bluetooth adapter — the BT400 is simply the model named in the project’s own issue thread; treat it as an example of the class, not a magic part number. Buy for a reputable chipset and current drivers, keep your motherboard Bluetooth disabled while testing so Windows uses one stack, and buy from somewhere with returns: Bluetooth behaviour varies enough by PC that no adapter is a guaranteed cure. (Our buying guides cover adapter picks separately — this page deliberately keeps the diagnosis tool-agnostic.)
If lag survives a known-good adapter too, the problem has moved — re-check the detection guide and the troubleshooting hub, and grab a clean copy of the program from the download page if your install predates v6.1’s rumble fixes.
FAQ
Is a Bluetooth 5.0 or 5.3 adapter automatically better than 4.0?
Not automatically. The documented failures are about chipset and driver quality and how the stack handles several simultaneous game controllers — which is why a well-supported 4.0 dongle appears in the project’s issue thread as the fix. Judge by chipset reputation and driver currency, not the version badge.
My Pro Controller lags too, on USB it doesn’t. Same fix?
Yes — USB removes the radio from the equation, so lag that exists only on Bluetooth lives in the adapter/driver/placement layer. Work through Checks 1, 3 and 4 in that order.
Does BetterJoy add input delay itself?
BetterJoy’s translation layer is not the documented cause in any of the reports behind this page; the identified causes are the Intel driver threshold, multi-connection load, and rumble traffic. Keep the program updated so you are not fighting the pre-v6.1 rumble bug, and measure after each single change.
Related buying guides: if your lag survives every fix on this page, the radio itself is the remaining suspect — our Bluetooth adapters for Switch controllers on PC guide covers what to replace it with, and when no adapter is needed at all.