Just posting this out to just so if anyone else encounters a similar issue, there might be hope for them.
Since the release of Dolphin 5.0, I've been trying to get some Non-TR WiiMotes working using the Dolphinbar. While the WiiMotes paired flawlessly to the Dolphinbar, the Dolphin emulator failed to utilize it at all.
After trying just about everything, I noticed some strange things happening to the Griffin PowerMate on my desk when I attempt to power on a WiiMote while the Dolphin emulator is running: the PowerMate's blue LED cuts out and the WiiMote doesn't become connected to Dolphin. I then go into the Controllers menu and hit the Refresh button...but this causes Dolphin to hard lock (would have to force close the app through Windows Task Manager).
It was at this point, just for kicks, I unplugged the PowerMate from USB and wouldn't you know, Dolphin became immediately responsive and found the WiiMote and connected (the WiiMote buzzed to signify it was paired, etc).
I can connect the PowerMate back to USB after Dolphin is connected to the WiiMote, but that is it. If I power cycle the WiiMote or close Dolphin, I have to first disconnect the PowerMate first before I can connect the WiiMote.
There is the following path that sometimes works: Dolphin is closed down, WiiMote power off, Dolphinbar connected over USB, PowerMate connected over USB. Start Dolphin, idle at game selection. Power on WiiMote (already paired to Dolphinbar) and Dolphin *might* find and connect it. This method probably boils down to the enumerated index in which the Dolphinbar/WiiMote USB appears...if the PowerMate appears earlier, it might cause it to not pair at all.
Here is the link to the PowerMate: https://support.griffintechnology.com/product/powermate/
While I have found a work around, its hardly ideal to constantly do the steps mentioned above to just connect the WiiMote. Maybe something about the USB characteristics of the PowerMate just don't fit right with Dolphin 5.0...or the code in Dolphin needs to accommodate for malformed USB responses? Not sure...
If anyone else might have insight on this, please provide any information here. Hopefully one of the devs finds it and can work in a fix?
Since the release of Dolphin 5.0, I've been trying to get some Non-TR WiiMotes working using the Dolphinbar. While the WiiMotes paired flawlessly to the Dolphinbar, the Dolphin emulator failed to utilize it at all.
After trying just about everything, I noticed some strange things happening to the Griffin PowerMate on my desk when I attempt to power on a WiiMote while the Dolphin emulator is running: the PowerMate's blue LED cuts out and the WiiMote doesn't become connected to Dolphin. I then go into the Controllers menu and hit the Refresh button...but this causes Dolphin to hard lock (would have to force close the app through Windows Task Manager).
It was at this point, just for kicks, I unplugged the PowerMate from USB and wouldn't you know, Dolphin became immediately responsive and found the WiiMote and connected (the WiiMote buzzed to signify it was paired, etc).
I can connect the PowerMate back to USB after Dolphin is connected to the WiiMote, but that is it. If I power cycle the WiiMote or close Dolphin, I have to first disconnect the PowerMate first before I can connect the WiiMote.
There is the following path that sometimes works: Dolphin is closed down, WiiMote power off, Dolphinbar connected over USB, PowerMate connected over USB. Start Dolphin, idle at game selection. Power on WiiMote (already paired to Dolphinbar) and Dolphin *might* find and connect it. This method probably boils down to the enumerated index in which the Dolphinbar/WiiMote USB appears...if the PowerMate appears earlier, it might cause it to not pair at all.
Here is the link to the PowerMate: https://support.griffintechnology.com/product/powermate/
While I have found a work around, its hardly ideal to constantly do the steps mentioned above to just connect the WiiMote. Maybe something about the USB characteristics of the PowerMate just don't fit right with Dolphin 5.0...or the code in Dolphin needs to accommodate for malformed USB responses? Not sure...
If anyone else might have insight on this, please provide any information here. Hopefully one of the devs finds it and can work in a fix?