Help with Bluetooth passthrough

[domjam]

(01-30-2019, 03:41 PM)mbc07 Wrote: I see you got it working, but for further reference, make sure your HW ID exactly matches the ones in the wiki when comparing test results. It seems very common with Qualcomm/Atheros BT adapters to use the same "friendly" name for completely different HW IDs (right now AR9462 comes to mind) and that seems to happen more often on WiFi+BT cards (which seems the case with your motherboard) where the results greatly varies between them...

I should probably put this on the wiki page as well

Im not sure what els to look for but looking under device manger under the device name libusbK USB devices there is [color=#111111]Qualcomm Atheros QCA1X4A Bluetooth 4.1 showing and thats the same name for the device on the wiki list showing as limited. If there is more to it then this just tell me were i need to look and i can post the info for you.[/color]

[themanuel]

(01-31-2019, 02:00 AM)mbc07 Wrote: TL;DR none of that matters if the people with the coding/debugging skills can't replicate the connection issue, and as it stands now, none of the currently active devs and testers did.

Then please do this simple test for me, if you have bluetooth passthrough:
1. Ensure you have vsync enabled in gfx config
2. Start NSMBW and, as soon as the first white wiimote warning screen appears, press any button on the wii remote
3. Repeat the exercise with the remaining two graphics back-ends

If you do not experience any difficulty connecting the wii remote with any of the back-ends, with vsync enabled, then this might indeed be a fringe case affecting me, and a few other users.

[mbc07]

(01-31-2019, 02:42 AM)themanuel Wrote: [...]
If you do not experience any difficulty connecting the wii remote with any of the back-ends, with vsync enabled, then this might indeed be a fringe case affecting me, and a few other users.

I don't own NSMBW but I own Skyward Sword, which according to reports from you and others is also problematic. Regardless of the backend (I can only test DX11 and OGL, though) or VSync setting the connection just works fine every time on my end. However, JMC47 does own NSMBW and AFAICT he couldn't replicate the issue either...

(01-31-2019, 02:22 AM)domjam Wrote: Im not sure what els to look for but looking under device manger under the device name libusbK USB devices there is Qualcomm Atheros QCA1X4A Bluetooth 4.1 showing and thats the same name for the device on the wiki list showing as limited. If there is more to it then this just tell me were i need to look and i can post the info for you.

Double click your BT Adapter in device manager, then go to the Details tab, on the Property drop-down menu, choose Hardware IDs, then look the output on the Value text box, you'll have something similar to USB\VID_xxxx&PID_xxxx&REV_xxxx. Do the VID, PID and REV values exactly matches any of the one listed on the wiki? If no, you have an adapter we didn't test and thus it may explain your connection issues...

[themanuel]

(01-31-2019, 03:47 AM)mbc07 Wrote: I don't own NSMBW but I own Skyward Sword, which according to reports from you and others is also problematic. Regardless of the backend (I can only test DX11 and OGL, though) or VSync setting the connection just works fine every time on my end. However, JMC47 does own NSMBW and AFAICT he couldn't replicate the issue either...

OK.  Thanks for checking.  I'm fine with my current setup as I can simply use Vulkan for those games and the problem goes away.  I was just trying to keep the issue alive but it seems very setup-specific.

[Helios]

I don't doubt there is an issue, timing issues like this are often random on who can actually reproduce as it depends on 40 million different variables and whether the planets align correctly.

But given that this is a timing issue, unless a programmer can reproduce it and find out how the timing issue is happening to fix it, it won't be fixed for awhile, as I said earlier.

This is why most of the devs are ignoring their issues.

[trihy]

Im not sure about this, cause testing bt passthrough is a pain on Windows. Its easy to hang the adapter when doing a lot of testing.

But tried some really old builds and the issue is there. Im pretty sure they worked fine when used those builds years ago.

So Windows or gpu drivers could be interfering with Dolphin vsync.

[domjam]

(01-31-2019, 03:47 AM)mbc07 Wrote: I don't own NSMBW but I own Skyward Sword, which according to reports from you and others is also problematic. Regardless of the backend (I can only test DX11 and OGL, though) or VSync setting the connection just works fine every time on my end. However, JMC47 does own NSMBW and AFAICT he couldn't replicate the issue either...

Double click your BT Adapter in device manager, then go to the Details tab, on the Property drop-down menu, choose Hardware IDs, then look the output on the Value text box, you'll have something similar to USB\VID_xxxx&PID_xxxx&REV_xxxx. Do the VID, PID and REV values exactly matches any of the one listed on the wiki? If no, you have an adapter we didn't test and thus it may explain your connection issues...

I have two in the properties window. Both correspond to the one listed as limited on the wiki.  but one of them does not have the revision. 

USB\VID_0B05&PID_1825&REV_0001
USB\VID_0B05&PID_1825

[asdf]

(01-26-2019, 12:28 AM)themanuel Wrote: To add to mbc07's solid advice, before trying to sync the game, make sure you go to dolphin's settings screen and uncheck "Pause on Focus Lost".  If the game is paused, it won't sync.  While running a game (and not paused), alt+tab to the main dolphin screen, open the controller settings screen and press "Sync", then press the red button in side the battery compartment of your wii remote.

Do this with a game other than NSMBW or Skyward Sword as those two can be problematic with certain setups.  Post back here if can't get it working.

Thank you thank you thank you!!! I soldered an original Wii BT module to a usb cable using the guide in this forum, but then spent hours trying to figure out why the wiimotes wouldn't connect. After reading your advice I unchecked the "Pause on Focus Lost" option and then they connected! Just wanted to note that it may be worth putting the info about that checkbox in the Bluetooth Passthrough wiki page. Not sure who has the power to do that or if anyone will even see this post, but figured it was worth mentioning. Again, thank you for preventing my further insanity!