You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Connect Wiimote (or in my case, Wii U pro controller).
2. Open any application that uses the controller (in my case, ZSNES).
3. Start playing a game, and notice that there is some stuttering. To test
this, rock the d-pad back and forth in Super Mario World, and notice that Mario
sometimes moves further in one direction than expected. In the SNES Test
program, sometimes left or right on the d-pad might get stuck for a split
second, which could explain this phenomena. It appears that someone else has
had this issue, but the solution provided is not for the average user, and
requires code to be entered, but I cannot figure out where.
https://code.google.com/p/wjoy/issues/detail?id=71
What is the expected output? What do you see instead?
The game should control with no issues, but instead, there is a stutter which
sabotages any gaming experience.
What version of the product are you using? On what operating system?
I am using wjoy 0.7.1 on Mac OS X 10.10.2 Yosemite.
Please provide any additional information below.
I need a solution that works for the average user, not a coding expert. I tried
removing the device from my bluetooth devices list multiple times, to no avail.
The problem is not bluetooth related, since Openemu's built-in bluetooth works
perfectly, so this issue is most certainly related to wjoy. Please get back as
soon as possible.
Original issue reported on code.google.com by [email protected] on 10 Feb 2015 at 8:28
The text was updated successfully, but these errors were encountered:
Hello :)
It's known problem. I'll fix it in next release. And it's really bluetooth
chip/driver bug, i think - it's happens only on some mac models.
And OpenEmu doesn't do something, what do WJoy, like low battery notifications.
Original comment by alexandr.serkov on 11 Feb 2015 at 9:52
Original issue reported on code.google.com by
[email protected]
on 10 Feb 2015 at 8:28The text was updated successfully, but these errors were encountered: