The only other thing I can think of is for you to try to connect it with vsync off. There is currently an issue documented elsewhere in the forum where vsync seems to have some interaction with bluetooth passthrough connectivity.
(01-30-2019, 12:41 PM)themanuel Wrote: [ -> ]The only other thing I can think of is for you to try to connect it with vsync off. There is currently an issue documented elsewhere in the forum where vsync seems to have some interaction with bluetooth passthrough connectivity.
and that was exactly what fixed it. thank you for your help. turning vsync of was the problem
Awesome. Perhaps you an still revert back to vsync after you've synced your wiimotes and they will work fine. If not, to avoid screen tear, either enable vsync through your GPU's control panel, or try a different gfx back-end. I was having all sorts of trouble with NSMBW BT passthrough connectivity and was only able to fix it by switching over to Vulkan, which I do now for that particular game..
I´m wondering if both NSMB and Z:SS tie the number of commands sent with their framerate/some sort of routine/anything.
I just noted this small piece of info in BT Passthrough wiki page:
"(Have issues with) games which send a lot of commands, including New Super Mario Bros. Wii and The Legend of Zelda: Skyward Sword before you get in game."
Obviously I don´t really know about the inside of all this. But could lead to why V-Sync fixes the sync issue.
(01-30-2019, 01:49 PM)themanuel Wrote: [ -> ]Awesome. Perhaps you an still revert back to vsync after you've synced your wiimotes and they will work fine. If not, to avoid screen tear, either enable vsync through your GPU's control panel, or try a different gfx back-end. I was having all sorts of trouble with NSMBW BT passthrough connectivity and was only able to fix it by switching over to Vulkan, which I do now for that particular game..
funny enough even though vsync is disabled it still does not screen tear. testing Zelda skyward sword it runs fine. im using dx11 backend and im also using reshade. only issue now is custom texture packs. as I cant seem to get them to work on latest builds of dolphin . but thanks a lot for helping me solve this problem.
Problem is that wii bt module is having problems with nsmb and zelda skyword. Not just other Brands dongles.
Wii bt module shouldnt have this kind of problems.
I'm not having these problems. AFAIK JMC nor leo has these problems either.
So unless somebody who is actually able to both reproduce and actually investigate the issue to find out what's going on in code (Which is probably some obnoxious timing issue, given vsync), you're going to be waiting a bit.
(01-30-2019, 12:24 PM)domjam Wrote: [ -> ] yea under device manager is libusbk USB device and under that is [color=#000000]Qualcomm Atheros QCA61x4A Bluetooth 4.1 .there must be a way for me to get it working because its listed under the main wiki as limited functionality with dolphin..and that states [color=#222222][b]Partially compatible.[/color][/b][color=#222222] Works well in most cases, but there may be some issues. [/color][/color]
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
(01-30-2019, 02:54 PM)Helios Wrote: [ -> ]I'm not having these problems. AFAIK JMC nor leo has these problems either.
So unless somebody who is actually able to both reproduce and actually investigate the issue to find out what's going on in code (Which is probably some obnoxious timing issue, given vsync), you're going to be waiting a bit.
I don't think it is that much of an obscure problem, given that the warning about NSMBW and Skyward Sword connectivity issues has been on the BT passthrough wiki page for a long time, so several people must have been exposed to that aspect of the problem. It's just that it hasn't bothered anyone enough to investigate further.
It bothered me enough when I realized I would frequently lose wiimote connection for 5-6s at a time while playing NSMBW. Eventually, trihy found that disabling vsync fixed the problem, and I realized that switching back-ends also fixed it, without having to disable vsync.
Likely, if a solution is found for the small connection issue identified in the BT passthrough wiki, it will work for all the other problems trihy and I have reported.
(01-30-2019, 11:38 PM)themanuel Wrote: [ -> ]I don't think it is that much of an obscure problem, given that the warning about NSMBW and Skyward Sword connectivity issues has been on the BT passthrough wiki page for a long time, so several people must have been exposed to that aspect of the problem. It's just that it hasn't bothered anyone enough to investigate further.
[...]
Likely, if a solution is found for the small connection issue identified in the BT passthrough wiki, it will work for all the other problems trihy and I have reported.
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.