Hello!
I'm having quite the weird issue and I'm not sure how to solve this.
I'm using a Mayflash w010 Wireless Sensor DolphinBar and connect my Wiimote as a real wiimote. It works fine in any other game I've tested but in Mario Galaxy it seems to lose and reconnect 2-3 times a second.
Here's a video of this issue:
https://www.youtube.com/watch?v=0W3jtyW2LCk
It's not even really reconnecting I think, I can walk and jump around just fine. The pointer is incredibly choppy and seems to select and reselect stuff at sudden intervals.
I've tried the usual: disabling AA, enable skip efb, disable scale efb copy, disabling customs textures, deleted the mayflash drivers and reinstalled it after a reboot - nothing works.
Neither updating dolphin to the current version nor downgrading the settings to the minimalest 480p settings.
The connect-reconnect issue persists but only in Mario Galaxy. I don't have any AR/GS codes or anything, but like I said: It works fine in Links Crossbow Training, Umbrella Chronicles and Skyward Sword. Only in Mario Galaxy it seems to be super choppy.
Any idea what else I could do?
What is your "IR Sensitivity" set to? (Dolphin settings, Wii tab) Try adjusting it.
How far are you from your your sensor bar? You should be about 2 meters (6 feet) away.
Oh hey, I have the same issue! It's happening in quite a few games, but not in others... no idea why. Has there been any change to real wiimote code in Dolphin recently?
I'm also using the Dolphin Bar btw (wired, though).
I also have the issue that the wiimote often disconnects, in Prince of Persia it even seems to be pretty much every ten minutes... but in some other games, it even happens after a minute. I don't know if these issues are connected. I only know that I didn't have either of them before (though I haven't played Wii games in a while).
(11-29-2020, 07:03 AM)Billiard26 Wrote: [ -> ]What is your "IR Sensitivity" set to? (Dolphin settings, Wii tab) Try adjusting it.
How far are you from your your sensor bar? You should be about 2 meters (6 feet) away.
IR Sensitivity is set to maximum, I tried reducing it to about half but the issue remained.
Moving further away also didn't help.
Curiously I decided to upgrade from 5.0-13144 to 5.0-13152 to see if it was just a glitch, but the issue was still there.
Then I downgraded back to 5.0-12716 which fixed everything. So I guess somewhere between 5.0-12716 and 5.0-13144 a weird bug must've crept into dolphins code that makes certain interpretations of wiimote signals in certain games difficult?
Hey, you're right. Using 5.0-12716, I also don't get the fickle cursor anymore.
Unfortunately, it didn't help me with my other issue, the wiimote disconnecting every time after a few minutes.
But yeah, there must have been some code after the aforementioned build that produced the cursor issue.
So, at least three people have the same issue now; so I guess it's not just some person's broken system's fault. All three who have reported this issue, though, are using the Dolphin Bar. Not sure if that might be part of the issue. Either way, I hope will not be ignored.
Please see if changing the "Enable Speaker Data" setting has any effect on the fickle cursor.
It secretly does more than speaker data.
(12-03-2020, 10:52 AM)Billiard26 Wrote: [ -> ]Please see if changing the "Enable Speaker Data" setting has any effect on the fickle cursor.
It secretly does more than speaker data.
Couldn't you post this some hours earlier? I was going mad trying to figure out why my WM+ wouldn't calibrate anymore, when you put it face down on the table. Is there a reason why it's even an option to disable it? If so, could the data be filterered, so that the data, that you want to avoid, probably wiimote audio, is filtered, but the rest goes through? Oh, and on that topic, would it be possible to add a toggle to divert wiimote audio to the normal audio device, play on both and wiimote only?
Back on topic:
I was having an issue with a fickle cursor too, with a Dolphinbar and Dolphin 5.0-13163. What fixed it for me, was moving the sensitivity slider from 50% to 75%. I can still reproduce it by getting closer to my sensor bar(PowerA Wii U Ultra Sensor Bar), with 75% i need to get much closer to the sensor bar than with 50% in order to trigger the issue. The Speaker Data setting doesn't seem to have an impact on this.
I do know the issue that a too low sensitivity can bring, but this isn't it. If it was, I guess all games would have the issue. (I did try, though, just to make sure)
Disabling speaker data also doesn't fix the issue (nor does disabling Real Balance Board).
Great thread. I was having the exact same issue - I use a real Wiimote and the Mayflash Dolphin Bar and on Mario Galaxy the IR sensor would constantly disconnect and reconnect. As with other users here downgrading dolphin to 5.0-12716 solved the problem.
Is there a place to file a bug or something?