Dolphin, the GameCube and Wii emulator - Forums

They will actually still work, but Bluetooth connectivity will be broken after you restore a state. There may be a way of getting it to work better, but I haven't really had time to look into it.

I recently bought a bluetooth adapter to connect wii remontes to my pc and havent been able to get it working. The model of my usb adapter is [color=#000000]BCM20702A0.[/color]
[color=#000000]I tried following this guide on the forum:
[/color]
[color=#000000]1. Download the Windows PR 4385 build here: [/url]https://dl.dolphin-emu.org/prs/pr-4385-dolphin-latest-x64.7z
[/color]
[color=#000000]2. Extract the archive and launch Dolphin.exe once, then close it out. (This adds a new line your dolphin.ini)[/color]

[color=#000000]3. Download Zadig: [/color][url=http://zadig.akeo.ie/][color=#006abd]http://zadig.akeo.ie/[/color]

[color=#000000]4. Open Zadiq, and in the Options select List All Devices. You should now see a list of USB devices in the dropdown menu. [/color]

[color=#000000]5. Select your Bluetooth adapter (For the broadcom, it's the BCM20702A0 entry) and click Replace Driver.[/color]

[color=#000000]6. Write down the hexadecimal codes you see under USB ID. (For my broadcom, it's 0A5C and 21E8. [/color][color=#006abd]http://i.imgur.com/JqV4BrU.png[/color][color=#000000])[/color]

[color=#000000]7. Convert your codes one at a time to decimal values: [/color][color=#006abd]http://www.binaryhexconverter.com/hex-to-decimal-converter[/color]

[color=#000000] - For example, the first number 0A5C gives us 2652, which is my PID. The second, 21E8 gives us 8680 which is my VID.[/color]

[color=#000000]8. Open your dolphin config folder (usually located at C:\Users\<User>\Documents\Dolphin Emulator\Config) and open dolphin.ini.[/color]

[color=#000000] - Near the bottom of the file, you'll find entries for VID, PID and DisableDescriptorCheck.[/color]

[color=#000000]9. Set the VID to your decimal VID (mine was VID = 2652) and the PID to our decimal PID (mine was PID = 8680).[/color]

[color=#000000]10. Set DisableDescriptorCheck = True.[/color]


[color=#000000][color=#000000]After this, when you launch the PR 4385 build, you should be able to sync your Wiimote (a game has to be launched before you can sync).[/color]
[/color]
I did all of this except for the disabledescriptorcheck which was not in the dolphin.ini. I still get the message No bluetooth usb device found.
Could anyone help me out? 

(01-13-2017, 12:10 PM)SquidCow Wrote: [ -> ]snip

You don't need to use that PR, that was before it was officially added.
Try your current settings with newest dev. If it doesn work manually paste in DisableDescriptorCheck = True.

DisableDescriptorCheck is not used anymore in the latest dev version. Just refer to https://wiki.dolphin-emu.org/index.php?t...assthrough for the instructions.

(12-14-2016, 05:42 AM)dreday78 Wrote: [ -> ]I'm trying to activate Bluetooth Passthrough, but when I start a game with it on, Dolphin crashes.  I'm trying to use my built in Asus adapter, ID: 0B05 179C.

I have the same issue.
After following the instructions with for zadig, device manager shows a new USB device - ASUS Bluetooth with VID 0B05 and PID 179C.
My motherboard is an ASUS P8Z68 Deluxe.

Dolphin will crash on 5.0-1841.  On 5.0-910 I get the "no usable Bluetooth USBdevice was found" error if I specify the VID/PID or if I leave them at -1.  For a brief while, 5.0-910 was not giving me that error and was instead allowing me to open the controller menu and attempt to sync.  It never found the controller though.

This chipset and motherboard do work in 5.0, but the audio through the speaker is atrocious and I suspect the performance isn't as good as it could be either.
I tried using zadig and newer builds to get passthrough working, but now I can't even revert to the previous setup which worked just before using zadig.  I've blown out the USB device and the drivers that came about after doing the zadug stuff and restored my old drivers, but Windows keeps stopping the device now.

This is what I have in the config file.

I went through all 19 pages of this thread and couldn't find any posts related to my issue so here it goes:

My Wiimote is connected and Dolphin remembers the pairing however MotionPlus does not work at all. I've tried several games and MotionPlus is never detected.
Everything else works in Bluetooth Passthrough.

Any suggestions? Thanks.

Dolphin 5.0-1985
Wiimote: 2017, purchased from Nintendo store.
Nunchuk: 2017, purchased from Nintendo store.
Bluetooth: Plugable USB 2.0 Bluetooth Adapter
Performed Zadig driver install, added my adapter in the config/dolphin.ini file, connected to USB3 port as recommended.

Win7x64, Intel 3770K, Nvidia 980Ti, 16GB RAM

This may seem like a silly question, but have you made sure the MotionPlus unit is not broken, and works with a real Wii?

Adapter: Broadcom BCM20702A0 Orico Bta408
Pairing: Yes and remember, I was able to achieve with a Wiimote RVL-CNT-01. I do not have any more drivers to test 2-4 concurrent pairs, though. Force to connect

1: Download the latest Windows build https://br.dolphin-emu.org/download/ 5.0-2008 and the one I tested
2: Download Zadig: http://zadig.akeo.ie/
3: Select the Bluetooth adapter (For broadcom, this is the BCM20702A0 entry) and click Replace Driver
4 note the hexadecimal codes you see in USB ID. (For my broadcom, it's 0A5C and 21EC
5: Convert your codes one at a time into decimal values: http://www.binaryhexconverter.com/hex-to...-converter in my case gave [BluetoothPassthrough]
Enabled = True
VID = 2652
PID = 8684
C: \ Users \ <User> \ Documents \ Dolphin Emulator \ Config) and open the dolphin.ini.
Ready now it works
6: Do not use opengl the ones that gave more right were vulkan and directx12
Wiimote: RVL-CNT-01 (WII SPORTS RESORT)
- Stable: more or less, once again an hour and a half of time like stuttering game "it seems to me that the bluettoth goes into a random economy mode just go to sleep and reconnect the remote wii back to normal."
- Range: Very good, 55+ feet (through two walls, even) before I noticed any lack of responsiveness. I ran out of the room to move further, so I never missed a full connectivity.
- Audio: Perfect

Adapter: CSR Generic Bluetooth Adapter V2.1 Edr Mini Nova E Blue
Pairing: Yes, DO NOT REMEMBER, Wiimote RVL-CNT-01. I do not have any more drivers to test 2-4 concurrent pairs, though.

1: Download the latest Windows build https://br.dolphin-emu.org/download/ 5.0-2008 and the one I tested
2: Download Zadig: http://zadig.akeo.ie/
3: Select the Bluetooth adapter (For my csr is the Generic Bluetooth Adapter 0A12 0001 input) and click Replace Driver
4: Do not use opengl the ones that gave more right were vulkan and directx12
Wiimote: RVL-CNT-01 (WII SPORTS RESORT)
- Stable: YES "works forever " with the game open being necessary press reset on the emulator then sync red on the control then on the emulator tighten synchronize every time a new game is run
- Range: good (through a wall) before I noticed any lack of responsiveness. I ran out of the room to move further, so I never missed a full connectivity.
- Audio: Perfect

I have plugable usb 2.0. One hour of playing Skyward Sword and the pointer goes crazy and buttons dont work. Any way to fix? Some people in this thread say that this adapter works great.