New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Defining which range of values will be reported to the HID interface #104
Comments
Well, just wanted to let you know that eventually I made it work with FreeriderFPV I was able to fix my problem by changing the -_MINIMUM values within the joystick.cpp file like this:
Considering this I guess it would be pretty easy to construct a procedure call to adjust the max/min values |
Turns out this applies to all Unity-based games. I was having the same problems here in my project and it was driving me nuts. Thanks for posting the solution! Cheers |
I was also having this problem, and the suggested settings above worked! |
Actually this hack is decreasing the resolution to half on the axes and hat switches. Working nice with Unity, but idk how it plays with other games. |
After a few weeks of experimenting with this unsigned mod, it seems like maybe not the best solution. Worked like a charm under Windows 10 (1803) and OSX, but had serious issues on Ubuntu (16.04). |
Version 2.1.0 of the library should address the issues seen in Unity (and other applications). |
Hi, great library, seems to work pretty consistently on Windows 7 and 10, great job!!
The flight simulator (FPV Freerider) that I am using is unable to recognize joystick positions in the negative region, that is having the center point at zero.
Here is their developers explanation: "On Windows, you need to setup so that the joystick channels go from 0 at minimum to 100 at maximum
(instead of -100 to +100)."
I have been fiddling with setting the AxisRange() but that does not seem to help a lot.
What I would really like is a procedure to set what max- and minimum values will be reported to the HID interface.
Is there any way that I could change this behavior within Arduino myself?
(or did I somehow misunderstand the meaning of the AxisRange() procedures?)
Below is a screenshot showing my range settings and the values that Windows 10 seemingly reports during calibration.
The text was updated successfully, but these errors were encountered: