Bluetooth pass through never ending troubles

[elementalwindx]

Does anyone have bluetooth pass through working 100%? I've never been able to fully get it to work. I used to be able to sync remotes, but they would randomly stop working, especially if I quit the game and start it up another day later.

Now I'm at the point where I've reset my entire dolphin install, deleting the folder under my docs, and gotten the newest version posted an hour ago. I've selected "Passthrough a bluetooth adapter" and hit the sync button, and the message that usually appears in the top left, no longer appears.



Any advice on what to do? I'm using the sedna ud100 adapter that the compatibility list shows as all green. Are there any updated lists of better bluetooth adapters out since then?

Thanks all.

[RemagOrter]

I use the same adapter. And i have no more issues since i added the (decimal) VID/PID numbers to the Dolphin.ini like this:
[BluetoothPassthrough]
Enabled = True
VID = 2578
PID = 1
More detailed step by step:
1. Plug in the BT Stick and use Zadig to install the libusbk drivers.
2. Install the latest USBDK Runtime Librarys
3. Use Zadig to find your VID/PID and use a converter like this https://www.binaryhexconverter.com/hex-t...-converter
to get the decimal numbers.
4. Open the Dolphin.ini, scroll to the bottom and change the VID and PID to your decimal numbers.

That's all. I forgot to do step 4, that's why i had problems at first.

[elementalwindx]

I use the same adapter. And i have no more issues since i added the (decimal) VID/PID numbers to the Dolphin.ini like this:
[BluetoothPassthrough]
Enabled = True
VID = 2578
PID = 1
More detailed step by step:
1. Plug in the BT Stick and use Zadig to install the libusbk drivers.
2. Install the latest USBDK Runtime Librarys
3. Use Zadig to find your VID/PID and use a converter like this https://www.binaryhexconverter.com/hex-t...-converter
   to get the decimal numbers.
4. Open the Dolphin.ini, scroll to the bottom and change the VID and PID to your decimal numbers.

That's all. I forgot to do step 4, that's why i had problems at first.

[elementalwindx]

Any idea where the latest USBDK runtime librarys are? I'll give that a try right now.

[elementalwindx]

Unless you mean these which haven't updated since 2017? https://github.com/daynix/UsbDk/releases

[RemagOrter]

Ehm, did you read this? https://wiki.dolphin-emu.org/index.php?t...assthrough
You find the link under "Setting Up -> Windows -> last sentence (hard to see)
Here's the link https://github.com/daynix/UsbDk/releases
Yeah them. If you get LIBUSB Errors from the Panic Handler, you'll have to install them.

[elementalwindx]

Yeah I've done all this that you've said and it will let them sync. I'll close out of everything and then go back to open dolphin, run a rom, and press 1+2 on the controller to get it to connect. At first one will connect but the 2nd controller won't. Then if I repeat the process, no controllers will connect.


I've also moved this entire setup to a completely different computer and I get the same end results.


Every time I open and close a emulator, it makes a noise like hardware has been added or removed from the pc too..


*edit* Ok after multiple tries. It seems to allow the same wiimote to connect but only one of the two I have. If I resync the one that doesn't connect, then it will let that one connect from then on and not the original one that worked fine. :/


This is my dolphin.ini:

[BluetoothPassthrough]
Enabled = True
VID = 2578
PID = 1
LinkKeys = 00:17:ab:39:42:95=131d20b134e0b52f4f3348c18a17339f,d8:6b:f7:38:69:f9=74a0c862e591d767d04bf20d2fba4cff


*edit again*

On the 15th try it allowed both controllers to connect.

Sometimes I'll get an warning "A "IPCEvent" event was scheduled from the wrong thread (non-CPU) Ignore and continue?


There is literally no pattern I can nail down and say with confidence "We finally got wiimotes to work"

Try 18+ it's not working on both wiimotes again..... -_-

[RemagOrter]

I get the IPCEvent Warning also sometime. No Clue where it comes from. Just click OK the Emulation should run.

Regarding Synchronizing:
DO you have Original Wiimotes or 3rd Party Wiimotes? Maybe the Sena UD100 has issues with some 3rd Party Wiimotes? I have only original Wiimotes, so i can't test it. Oh and btw, i can only register 2 Wiimotes without problems, if i register a third Wiimote, it messes up the pairings.
[EDIT] For a single game session with friends i can pair all 4 Wiimotes. But after that i have to do the pairing for my 2 main Wiimotes again. I think the SENA UD100 can save only 2 Wiimotes, but can handle more in 1 session.[EDIT]

And are you using the Sync button to pair the Wiimotes? And after they are paired, you have to press any button to connect the Wiimote, not 1+2 (that's forcing a new pairing scann and therefore messing up the pairing).
[EDIT] I totally forgot about this: Did you try to delete you SYSCONF file in Wii/shared2/sys/ ? Worth a try.

If this dosn't help, i'm out of ideas

[EDIT] Regarding the Hardware unplug sound, that noise is normal. Since the adapter is passed through to Dolphin this plug in plug out sounds happen whenever Dolphin handles the adapter. If you install the WinUSB drivers with Zadig, you get that small USB Hardware icon beside your windows clock. Whenever you start Dolphin this icon will disapear and the sound is played. Closing dolphin and the icon appears again. I think cause Dolphin takes control over the adapter and gives it back to Windows when closed again.

One more question: Where did you plug in the SENA UD100? If possible try to use another USB port. If possible one that's direcly on your Motherboard. And then check the VID/PID again.[EDIT]

Good luck.

[elementalwindx]

If I sync a wiimote, and exit dolphin and re-enter it , pressing anything other than 1+2 doesn't let the wiimote connect I have 2 original wiimotes and a clear blue walmart wiimote. I've tried deleting the entire dolphin folder out of mydocs. Would that be equal to deleting the sysconf?

I've tried plugging my sedna into multiple usb 2/3/3.1 ports.

[themanuel]

Before you go with UsbDk, you should give plain old WinUSB a try (installed through ZaDig). I switched to that from libusbk (also through Zadig) recently and it resolved some of my problems. UsbDk has been known to cause issues for some people so I would try WinUSB first.