Most Wii Remote problems in Dolphin are not controller problems. They are translation problems: your operating system’s Bluetooth stack pairs the remote, Dolphin interprets what the stack hands it, and somewhere in that chain the speaker audio, fine motion data and sync behavior of a real Wii get lost. Bluetooth passthrough removes the translator: Dolphin gives the emulated Wii direct control of a USB Bluetooth adapter, and the remote talks to what it believes is a console.
As an Amazon Associate, we earn from qualifying purchases.
That makes passthrough the most accurate way to use real Wii Remotes on a PC, and the fussiest. It demands a compatible adapter, a replacement driver on Windows, and an adapter your computer cannot use for anything else while you play. This guide covers what it does, what it costs, and how to set it up following Dolphin’s own documentation, using only games from your own discs.
Some links in this article are affiliate links, and we may earn a commission when you buy through them at no extra cost to you.
Quick Answer
Dolphin Bluetooth passthrough hands a USB Bluetooth adapter directly to the emulated Wii, so real Wii Remotes pair, sync and behave as they do on console hardware, speaker audio included. It needs a wiki-documented adapter, a libusbK driver swap on Windows, and that adapter becomes Dolphin-only while in use. For accuracy-obsessed Wii play, nothing else matches it.
What Passthrough Actually Does
Since Dolphin 5.0-910, the emulator has been able to pass a Bluetooth adapter straight through to the emulated software instead of emulating one itself. In standard mode, Dolphin pretends to be the Wii’s Bluetooth hardware and translates between the remote and your PC’s own stack. In passthrough mode, the emulated Wii runs its own Bluetooth stack against your real adapter, exactly as it would against the module inside a console.
Because the Wii software is doing the talking, behaviors that depend on the console’s stack simply work. Pairings are stored as a Wii stores them, so a synced remote reconnects as it does on hardware. The remote’s speaker gets its audio properly, and fine motion data arrives unfiltered. The wiki is blunt about the ceiling: perfect compatibility is only guaranteed with Bluetooth modules from Wii consoles themselves.
What It Buys Over Emulated Bluetooth and the DolphinBar
Three gains matter. First, accuracy: the wiki notes passthrough communicates fine motions more accurately than standard Bluetooth emulation, which shows up in tilt-heavy games. Second, audio and pairing: Wii Remote audio is supported, third-party remotes can pair, and sync survives as it does on a console instead of depending on your PC stack’s mood. Third, Wii Remote Plus handling: remotes with MotionPlus built in, the awkward case for several PC stacks, are handled by the Wii’s own software, not workarounds.
The Mayflash DolphinBar is a fine device for the emulated route, but the wiki lists it as not supported for passthrough, because it does not expose its internal Bluetooth adapter to the PC at all. If you own one, it stays useful as a sensor bar and for standard mode, nothing more.
The Costs, Stated Plainly
Passthrough takes your adapter away from your operating system. While the specialized driver is installed, the OS cannot access the adapter, so your Bluetooth mouse, headphones and gamepads lose their receiver until you revert the driver. Most passthrough users dedicate a cheap second adapter to Dolphin permanently.
Compatibility is specific, not general. The wiki warns that stability depends heavily on the adapter, and its test table gives individual models individual verdicts: lag after long sessions, trouble with multiple remotes, pairings that do not survive. A modern adapter is not automatically a good one; some current Realtek designs on the newer EPATCH v2 firmware format are listed as not working at all.
Other features shrink too. Netplay and input recordings are limited, save states made in passthrough cannot load in emulated mode or the reverse, and a remote can disconnect if emulation runs too fast or slow. Unplug the adapter mid-game and Dolphin may crash.
Setting It Up on Windows
- Plug in the adapter you are dedicating to Dolphin, ideally from the wiki’s tested list; note its model and revision.
- Download Zadig and run it as Administrator. In Options, enable List All Devices, then find your Bluetooth radio.
- In the right-hand column select libusbK and click Replace Driver. This hands the adapter to Dolphin and takes it away from Windows Bluetooth; it is reversible later through Device Manager.
- In Dolphin, open Controller Configuration and select Passthrough a Bluetooth adapter in the Wii Remotes section.
- Start a game, then sync a remote with the Sync button in that dialog, or the Press Sync Button hotkey, which behaves like the Wii’s red sync button: pressing triggers a sync, holding clears pairings.
- If Dolphin reports no usable adapter, force it. Newer builds offer an Adapter dropdown in controller settings; on any build, set VID and PID in the BluetoothPassthrough section of Dolphin.ini, with a 0x prefix.
Linux and macOS Notes
Linux needs no driver replacement, but it does need permission. The wiki’s route is a udev rule in /etc/udev/rules.d/52-dolphin.rules granting user access to your adapter’s VID and PID, then reloading the rules and reinserting the adapter. Dolphin can usually unload the btusb kernel module itself if your user is in the plugdev group; otherwise unload it manually.
macOS has the strangest history. Passthrough stopped working after macOS 10.9, because Apple removed the ability to unload the Bluetooth kernel module, then returned on macOS 11 and 12 with no custom drivers needed; on macOS 12 and newer you simply connect a compatible adapter. Android does not support passthrough.
Troubleshooting the Usual Failures
LIBUSB_ERROR_NOT_SUPPORTED on Windows means the libusb or WinUSB driver was never installed for that adapter; redo the Zadig step. LIBUSB_ERROR_ACCESS on Linux points back to the udev rule. A black screen over ten seconds at boot usually means the adapter is stuck after the reset command; unplug and retry. Remotes that will not stay paired after closing a game point, per the wiki, to an adapter that does not remember link keys properly; the honest fix is a different adapter.
Hardware That Serves a Passthrough Setup
TP-Link UB500 Bluetooth Nano USB Adapter
The wiki’s table lists the UB500 line, built on the Realtek RTL8761B, as working with firmware loading and stable in its original version, making it the easiest current adapter to justify. Check the hardware version on the box; later revisions share the name.
Specs:
– Chipset: Realtek RTL8761B, per Dolphin’s adapter test table
– Bluetooth version: 5.0 on the original version; varies by revision
– Interface: USB, nano form factor
– Dolphin wiki status: works with firmware loading
– Model: UB500
ASUS USB-BT400 Bluetooth 4.0 USB Adapter
The BT400 appears in the wiki’s table on its Broadcom BCM20702 chipset with working audio, marked as an adapter to specify manually by VID and PID. Its known limit is stability over long sessions with demanding games, so treat it as a single-remote option, not a party adapter.
Specs:
– Chipset: Broadcom BCM20702
– Bluetooth version: 4.0
– Interface: USB 2.0
– VID and PID: 0B05 and 17CB or 17CF, depending on revision
– Dolphin wiki status: works when specified manually; audio supported
ASUS USB-BT500 Bluetooth 5.0 USB Adapter
ASUS’s newer adapter is also an RTL8761B design in the wiki’s table, listed as working once Dolphin loads its firmware, with the same multi-remote limitations as its chipset siblings. Pick it for the modern firmware route over the older Broadcom path.
Specs:
– Chipset: Realtek RTL8761B
– Bluetooth version: 5.0 with EDR
– Interface: USB, ultra-small design
– VID and PID: 0B05 and 190E or 1BF6, depending on revision
– Dolphin wiki status: works with firmware loading
Nintendo Wii Remote Plus, Black
The genuine Wii Remote Plus is the remote the Wii’s own stack was written for, with MotionPlus built in rather than clipped on. Its speaker, sync behavior and motion output follow the console pattern exactly, because nothing translates.
Specs:
– Motion sensing: built-in Wii MotionPlus
– Audio: built-in speaker
– Sync: red sync button pairing, stored by the emulated Wii
– Power: AA batteries, count not stated
– Color: black
Aokin Sensor Bar for Wii
Passthrough solves the Bluetooth half of pointing, not the infrared half. The pointer still needs an IR source above or below your screen, and this wired replacement bar provides it, stand included.
Specs:
– Type: wired infrared sensor bar for Wii and Wii U
– Placement: above or below the screen
– Included: clear stand
– Cable length: not stated
– Power note: console-plug design; a PC-only desk needs a USB-powered variant
How to Choose
Start with the wiki’s adapter table, not storefront specs. Find your candidate’s exact model and revision, read its stability notes, and prefer a verdict of works or works with firmware over a newer Bluetooth version number. For several remotes, avoid entries flagged for multi-remote issues; for solo play, a limited-stability Broadcom adapter is a reasonable route.
Then decide how permanent this is. A dedicated adapter in one USB port, driver already replaced, turns passthrough into a two-click habit. Sharing one adapter means repeating the Zadig swap and Device Manager revert until you stop bothering. Keep a sensor bar in the budget for pointer-heavy games; passthrough does nothing for aiming alone.
Who Should Skip
Skip passthrough if you mainly play GameCube games, use an emulated remote with a gamepad, or rely on netplay and input recordings, which passthrough limits. Skip it if your PC’s only adapter also runs your mouse, keyboard and headphones and you cannot add a second one. Skip it on Android, where it is unsupported. Skip it for a casual library: standard mode with Continuous Scanning covers that well, with no driver surgery.
FAQ
Does the Mayflash DolphinBar work with passthrough?
No. The wiki lists the DolphinBar as not supported for passthrough because it does not expose its internal Bluetooth adapter. It remains a good sensor bar and standard-mode receiver, but passthrough needs a separate documented adapter.
Will my remotes stay synced between sessions?
That is the design. Pairings are stored by the emulated Wii as a console stores them, so synced remotes reconnect on later launches. If pairings keep vanishing, the wiki blames adapters that fail to remember link keys, and recommends a different adapter.
Can I get my adapter back for normal Bluetooth use?
Yes. On Windows, uninstall the libusbK device in Device Manager and Windows reinstalls its default driver next time the adapter is plugged in. The wiki documents the same revert for WinUSB installs, listed under Universal Serial Bus Devices.
Does passthrough work on a Mac?
On current macOS, yes. The wiki records that passthrough returned with macOS 11 and 12 and needs no custom drivers on macOS 12 or newer; connect a compatible adapter and Dolphin can use it.
Final Verdict
Bluetooth passthrough is Dolphin at its most faithful: the emulated Wii runs its own stack against real hardware, and real remotes answer exactly as they do on a console. The price is a dedicated adapter and a driver swap your operating system will not love. If Wii games are the heart of your library and motion accuracy matters, follow the wiki’s table, buy one documented adapter, and set it up once.











