I found this 2 year old site. It's way above my head what they are talking about, but i think you guys would be surprised.
Can someone qualified please read this, it's not too much text and i really think this could be of some kind of help. Thanks in advance
https://github.com/daynix/UsbDk/issues/35
I think it might be important what kind of driver you install for your bluetooth adapter, when you use usbdk. Well, that's the only way i can explain why it works well for me. If you install a bluetooth driver with a standard bluetooth stack, it might try to connect to your wiimote through that. And if you install a bluetooth passthrough compatible driver, it might try to use passthorugh through that. Or it works well for me because of Windows 7...
Long story short:
I use the bluetooth driver from the ScpToolkit to use my ps3 controllers wirelessly as xinput controllers. And for Dolphin bluetooth passthrough, i have usbdk 1.0.19 installed on my system. When i launch a wii game with bluetooth passthrough enabled, it then disables the ps3 controller driver and reenables it when shutting down the game.
(02-19-2019, 12:23 AM)themanuel Wrote: [ -> ]I was hoping that would help but usbk is quite a pain in the ass. I'm not sure where to go from there.
One more thing to try would be the instructions in the Dolphin Wiki BT Passthrough page for forcing a specific BT adapter.
I have to apologize. Cause i'm a Dumbest Assumable User, i made a big small misstake.
The Dolphin BT Passthrough Wiki says this:
[color=#000000]
Forcing a specific adapter[/color]
[color=#222222]
If you need to use a specific adapter, instead of using the first Bluetooth adapter that is found, you can force Dolphin to use it by editing Dolphin's configuration file (Config/Dolphin.ini). In the BluetoothPassthrough section, set "VID" and "PID" to your adapter's vendor ID and product ID. [color=#663366]These values should be converted from hex to decimal[/color], for example a VID of "057E" should be inputted as "1406".[/color]
[color=#222222]
The Dolphin.ini has preset numbers in it. VID: -1 and PID: -1. Now my misstake was to assume the " - " have to stay. And my VID was "-2578" instead of "2578"", same for PID "-1" instead of "1".[/color]
[color=#222222]
Once i deleted the - symbols infront of the VID/PID numbers in Dolphin.ini, i get no more LIBUSB_ERROR and the BT Adapter works flawless every time.[/color]
[color=#222222]
I have now installed the WinUSB Drivers with Zadig and have installed the latest USBDK Runtime Library.[/color]
[color=#222222]
So i would say for me this is solved. I think my internal Bluetooth device was causing the problem, even that i deactivated it in devicemanager. I think that wasn't enough and it interfered somehow.[/color]
[color=#222222]
Thanks anyway. Without your hints and tips i would be lost.[/color]
Awesome. I'm glad you have it working now. There was nothing dumb about that, as it wasn't clear just from looking at the ini file.