Wii: communication with controller has been interrupted

[guoyunhe]

Compiled the core on Linux, but get this error (Mario Kart):

Standalone Dolphin emulator works fine with the same controller.

[emfox]

confirmed.
using real wiiremote and it's disconnect every 2 or 3 seconds, and reconnect if press any button.

[medievil1]

happening on windows 10 as well..I didn't realize this was the same issue so made my own here #153

[silvarios]

First test:
Dolphin Core version: 2dd20d2 (2020.08.25)
RetroArch Version: 1.9.0
Platform: Linux EndeavourOS (Arch Linux distro
Linux Kernel: 5.8.9-arch2-1
I have the same problem. With the latest buildbot version of Dolphin core and a Dolphin Bar, the Wii Remotes connect, then immediately error out with the same message. If I push a button on the Wii Remote, everything reconnects, only to disconnect immediately again.

Second test:
I compiled the most recent build (based on commit f4f4947) and it seems like some of the terminology in the settings have changed ("Bluetooth Scan" became "Wiimote Continuous Scanning"), but even after enabling the proper settings, I no longer get any messages from the dolphin-core and the Wii Remotes never connect at all. They are definitely still attached to the Dolphin Bar itself, the Core simply is not recognizing them.

Third test:
I built the core with the commits from c7a8067, which are specific to "Support for real Wiimotes and DolphinBar". As with my second test, the core seems not to respond to the Wii Remotes at all.

In general:
Usually I run RetroArch in KMS mode on Linux, but I tested in the GUI, same behavior. Also, stand alone Dolphin seems to work fine with the Dolphin Bar and Wii Remotes. Would be happy to try to generate some logs that may be useful for any developers or provide any additional information that can help solve this bug. Or if the recent changes do in fact fix the problem and I am simply misapplying the settings, I would be happy to check that too.

[medievil1]

I was able to get the latest (built myself) committed version to do old behavior (connect then immediately disconnect, not just dolphin bar, but bluetooth adapter as well) by changing a setting in dolphin.ini (saves/dolphin-emu/user/config as I recall)
I set WiimoteControllerInterface = to true (default is false)

Issue doesn't really seem dolphin related but maybe more RA passthru not passing a signal dolphin needs to know to determine that the wiimote is still connected

but then Ideally realwiimote should bypass RA input all together, since it is a custom to the core internal driver thing...realwiimote would be useless to any other core

[silvarios]

@medievil1
Thank you for the tip, I can try that setting change and report back. I wonder what happened in the core and/or RetroArch to have this setting no longer working? It worked as recently as last year according to forum posts on the RetroArch forums. I wonder if moving my working RetroArch Dolphin.ini or WiimoteNew.ini files over from stand alone Dolphin to RetroArch will allow me to Frankenstein together working settings. Yeah, i agree, seems like the polling is not functioning correctly and is dropping the remote connection too quickly. But I am just a layman here.

[medievil1]

@medievil1
Thank you for the tip, I can try that setting change and report back. I wonder what happened in the core and/or RetroArch to have this setting no longer working? It worked as recently as last year according to forum posts on the RetroArch forums. I wonder if moving my working RetroArch Dolphin.ini or WiimoteNew.ini files over from stand alone Dolphin to RetroArch will allow me to Frankenstein together working settings. Yeah, i agree, seems like the polling is not functioning correctly and is dropping the remote connection too quickly. But I am just a layman here.

I tried that... unfortunately it doesn't work/help.... if the server hadn't gotten hacked/deleted I would have tried to go back to a dolphin core release last year and try it in a new RA build to see if it is a core issue or an interface isse

[silvarios]

medievil1
I compiled with the latest commit, f978693:
Findings:
Even changing that value to True, I am not having any luck. The Wii Remote will vibrate as if it connects, but there is no connection or disconnection text from the Dolphin core, nor is there any functioning input. I tried deleting Dolphin core configs and starting over, same problem. No connection at all.

Real Wii Remotes selected in Quick Menu->Controls. Wiimote Continuous Scanning is enabled and WiimoteControllerInterface also enabled. Maybe newer changes from more recent commits have "broken" something else? The current Dolphin core is pretty solid, I get excellent GameCube support and Wii support for games that do not require the Wii Remote and Nunchuk. Just this pesky Wii Remote issue is keeping me from being 100% configured.

[medievil1]

medievil1
I compiled with the latest commit, f978693:
Findings:
Even changing that value to True, I am not having any luck. The Wii Remote will vibrate as if it connects, but there is no connection or disconnection text from the Dolphin core, nor is there any functioning input. I tried deleting Dolphin core configs and starting over, same problem. No connection at all.

Real Wii Remotes selected in Quick Menu->Controls. Wiimote Continuous Scanning is enabled and WiimoteControllerInterface also enabled. Maybe newer changes from more recent commits have "broken" something else? The current Dolphin core is pretty solid, I get excellent GameCube support and Wii support for games that do not require the Wii Remote and Nunchuk. Just this pesky Wii Remote issue is keeping me from being 100% configured.

hmmm Mine would buzz and in the top left I would get the wiimote connected, wiimote disconnect yellow dolphin message.....if you have the message system disabled in the dolphin ini you might not see them

[silvarios]

Anyone test newer builds in the last 9 months to see if the problem has been solved? I didn't see any code commits that was specifically about Wii remotes but you never know. I've been using a modify dolphin-launcher to kick out from DRM/KMS RetroArch to a mini X11 setup in a different TTY, solely to use upstream Dolphin as a work around, but seems like being able to use Dolphin in KMS (thanks to RetroArch) would be pretty cool.

I did try to use a fork that added KMS support to upstream Dolphin, but I never really had success with it.

[Jonney5]

I still having the same issue with the DolphinBar on the current core.

[silvarios]

Thank you for testing. I have not gotten around to building libretro Dolphin in a while. This one bug is pretty much all that's preventing me from switching over to RetroArch for all emulation on my PC. Fingers crossed it gets fixed one day.

[cscd98]

Fixed in #405 and #404. Do you still have this issue?