Wii BT module in passthrough not working with NSMBW - need confirmation

[themanuel]

[color=#000000]In late 2017, I connected a Wii replacement module (J27H002.00 LF) to my computer using the DIY USB hack documented elsewhere in the forums.  I had assumed this was the "ultimate solution" and would not have to worry again about Wii remote connection and operation anymore.  However, I've come to realize that I can't get it to work well with New Super Mario Bros. Wii, specifically.  It is hard to get the Wii remotes to connect when the game starts and when they do, they will frequently disconnect for about 5-6 seconds while playing the game, rendering it unplayable.[/color]


[color=#000000]I'm planning to attempt the hack again, but this time with an original WLM-C43 module.  However, before I do that, I would appreciate it is somebody can confirm if they have these types of issues with NSMBW.  [color=#000000]I had previously noted that with Skyward Sword, if you press a button on the Wii remote too soon after the game loads, you will not be able to connect and will have disable/enable the module before trying again.  [/color]I think the information in the Wii Bluetooth Passthrough wiki page should be updated to reflect that even the Wii's BT module is not an unqualified green "Yes" solution, and should have the "2" superscript appended to it, at least for J27H0002.  
[/color]

[color=#000000]If you are using a Wii BT module in passthrough mode, would you mind checking if you have the problems described above with New Super Mario Bros. Wii?[/color]

[Polaco]

Did you find a solution? I am having the same problem in my new computer, in my case the only solution looks like if I play in the original resolution, if I upscale to 2x or above the NSMBW start disconnect the wii remote, it doesn't matter which api (vulkan, d3d11,12, etc). But my previous computer was i5 3570 with gtx 960, now it is a intel hd 630, maybe I think the intel hd graphics is not powerful enough (even 2x resolution still running on 60fps) so may cause a kind of delay. Anyway, I am curious if you found a solution or figured out what could be, thanks.

[Polaco]

Good news, I fixed my problem, short answer:
my monitor is 75hz but I use in 60hz (59.9x actually), so I changed to 75hz on the windows display, and no disconnection problems anymore!

Long answer:

I tried so many options, I kind feel the problem could be a delay because in native internal resolution runs better, anyway I finally figured out what is the problem in my case!
First I made a list and tried all the steps below, nothing worked (may can work for you):

1 - tried only one monitor (I use 2, so could make the hardware slower and disconnect the wii remote)
2 - tried close all apps first to run (like bank security apps, etc, it could some how interfere in the communication?!)
3 - tried single core
4 - tried another dolphin version (5.9202)
5 - tried to install another driver (Winusb)
6 - tried another api like vulkan etc (tried all them)
7 - tried play windowed mode (for me even not full screen still disconnecting)
Nothing worked...

So I still wondered why vsync off run well but turned on runs bad... so I went to monitor settings, I see the hz was in 59.9xhz (so I thought maybe the game run in 60fps but the hardware runs slower making a delay...) so I put in 60hz the game runs better but still disconnecting, and then I see my monitor is 75hz, so I changed to 75hz also and.. BINGO! No disconection, wii remote runs flawless on full screen, vsync on and 2x Internal Resolution with rumble and audio on! Playing with 2 wii remotes!

So I hope it could help you guys also!
Thanks.