Dolphin Bar and Windows 10
|
Dolphin Bar and Windows 10
|
|
08-16-2016, 10:03 AM
 (08-16-2016, 09:52 AM)brando56894 Wrote: I see where you screwed up: you're supposed to bark like a chicken, not a cow hahaha I just emailed Mayflash. Hopefully it gets sorted out soon. Talk about sour grapes! 08-16-2016, 01:53 PM
Already received a reply from Mayflash. Their suggestion was to try the Dolphin v3.5 and it worked. I did have to sync the Wiimotes to the bar prior to launching Dolphin, but I made it past a couple levels with no disconnect. In fact, v3.5 seems to work better with my set up.
08-16-2016, 05:38 PM
 (08-16-2016, 09:36 AM)brando56894 Wrote: Yep, they both work fine with the Wii. I'll see if my Arch Linux VMware guest will work properly passing through the DolphinBar, otherwise I'll boot up an Ubuntu Live image and give it a try natively. I just listed the Wii and it's controllers on Ebay since I never use them and would much rather use Dolphin on my PC since it's far less of a PITA then using the hacked Wii. I'll probably end up just buying the official Wii Motion+ controllers to use with it. You can't actually use the DolphinBar under Linux with the official dev builds currently (unless you build this PR which adds DolphinBar support)… so you'll have to use a Bluetooth dongle. Honestly, every time I see a Wiimote work with a Wii but not with Dolphin on Windows, and especially a third-party Wiimote, my first response is always to try on Linux because Windows often simply does not work with them, even with a DolphinBar. 08-16-2016, 05:47 PM
(08-16-2016, 01:53 PM)FVGAZI Wrote: Already received a reply from Mayflash. Their suggestion was to try the Dolphin v3.5 and it worked. I did have to sync the Wiimotes to the bar prior to launching Dolphin, but I made it past a couple levels with no disconnect. In fact, v3.5 seems to work better with my set up. I have a DolphinBar too, and 5.0 works fine. The suggestion to try 3.5 was not a very good one from Mayflash imo, and you're missing out on literally thousands of changes since 3.5 to 5.0, including better accuracy, performance improvements, new features, bug fixes… Also, Dolphin doesn't communicate directly with the DolphinBar, and actually goes through the system's HID driver. And sound shouldn't have be disabled to get it working (disabling it was mostly useful for weak Bluetooth dongles). Though, at least now you know that 3.5 works, so maybe you could bisect (see which version broke Wiimotes for you)? 08-17-2016, 01:50 AM
(08-16-2016, 05:47 PM)leolam Wrote: I have a DolphinBar too, and 5.0 works fine. The suggestion to try 3.5 was not a very good one from Mayflash imo, and you're missing out on literally thousands of changes since 3.5 to 5.0, including better accuracy, performance improvements, new features, bug fixes… That was my thinking at first as well. I've been a Dolphin user for years and literally cringed when I when I opened up the zipped 3.5 and saw the old icon. But you know what, I had some crazy screen tearing with 5.0 and not with 3.5. The only setting I've changed was the resolution. Screen tearing at 3840x2160 doesn't exactly feel like a "performance improvement". And I'm totally aware of how the DB works with Windows HID. What I meant was that something between the DB and Dolphin itself is dropping out. And since 3.5 doesn't have this issue and 5.0 does...? My guess is there's a bug in 5.0. I've read from several other users that 5.0 works just fine with the DB. What I've not heard is whether or not they're using multiple Wiimotes simultaneously. Multiplayer. This is the problem for me. I would very much like to be using 5.0 though. I uninstalled and reinstalled it multiple times trying to get it working. Mayflash must know something we don't if they made such a specific recommendation that worked immediately. 08-17-2016, 02:20 AM
It seems this and the other thread (https://forums.dolphin-emu.org/Thread-dolphinbar-wiimote-does-not-work) are both about the exact same issue.
The user from the other thread run my test program and it does pick up the Wiimote and receives input from it. So this is a bug on Dolphins side. Bisecting what Version/PR broke it would be nice to finding a fix for it. 08-17-2016, 02:23 AM
UPDATE: ARGHHHH!!!
I should've known that 3.5 would have not been the answer. Started doing it again. So maybe it's a bug with the Windows HID driver? Perhaps there is someone here that understands how to fix this issue? I know this is a widespread issue because people with is problem are on many different forums looking for a solution. If the DolphinBar works for you, that's wonderful. If anyone KNOWS how to fix this issue we'd love to know the answer. (08-17-2016, 02:20 AM)JulianLoehr Wrote: It seems this and the other thread (https://forums.dolphin-emu.org/Thread-dolphinbar-wiimote-does-not-work) are both about the exact same issue. The only version I've had on this PC was 5.0 prior to using the Dolphinbar. Sooo.... 5.0 would be a good guess. Or a Win10 HID issue. 08-17-2016, 02:48 AM
So it did work on 3.5 but now it stopped?
I do have an idea as to what may be the bugs root. But that would/could also affect Wiimote connected per Bluetooth Dongle. So that's a missing piece why it only affects DolphinBar. 08-17-2016, 02:59 AM
(08-17-2016, 02:48 AM)JulianLoehr Wrote: So it did work on 3.5 but now it stopped? Correct. Worked last night perfectly. Then the same issue started again this morning. I actually have this same issue with my BT dongle, but I was assuming it was because it was a crappy BT dongle. Would love to know what your idea is. |
|
« Next Oldest | Next Newest »
|
