-
Notifications
You must be signed in to change notification settings - Fork 7
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
Analog Sticks Classic Controller #10
Comments
Probably those value are slightly off: https://github.com/xerpi/viimote/blob/master/main.c#L24 |
I can confirm this issue and it happens for the nunchuck too. Tested both an original wiimote with/without motion plus attached and a wiimote plus. If I connect my wired fight pad in the wiimote the range values are fine, so, the problem lies only on the nunchuck and both wii classic controllers. |
I don't have those accessories myself so I can't test it. |
I have a Classic Controller, but don't have a Nunchuck. I know nothing about VitaSDK or how to use git and compile software, but I am willing to learn. So far I think I understand how to install VitaSDK via msys2, but I have no idea on what to do next. Can you point me to some instructions, please? Also, how hard would it be to make the plugin read the mapping and deadzone/sensitivity values from a file, instead of hardcoding them? That would actually make testing and finding the right values much easier, and will allow for remapping. I, for one, would very like to remap the O to A and X to B, because they are being the other way around currently. |
@BFG1992 to compile:
This will generate the skprx. |
@xerpi So, I have learned how to recompile it and fiddled with values around the lines you have linked. P.S.: I actually have the Wii Classic Controller Pro, not the regular, older one with analog triggers. Sorry for misinformation there. |
Hi and sorry if this is already resolved. Whats the progress so far with the stick values? |
@zerofalcon I did no further testing of the plugin since writing that comment. As I stated: I don't really understand how to program such stuff and am bad at math, so fiddling with the stick values in the code is all I can do, sadly. I never found values that would make the Wii Classic Controller Pro analog sticks to report ranges of 0-255 on the Vita, as the Vita's sticks do. I (wildly) guessed that maybe it isn't as simple as just putting in some right values, so I have posted my findings in hope that xerpi finds them useful and makes according changes to the code, but it seems that either my testing wasn't useful or xerpi is not interested in further development of this plugin :( Coincidentally, I have bought myself a (used) Nunchuk yesterday, so I might have a try at tweaking the values once again, after it arrives tomorrow. The code for the Classic Controller analogs and for the Nunchuk analog is different, so maybe I can compare the reported values of both attachments and figure something out... Don't count on that though. |
Just tested it with a Nunchuk and it works fine. |
Thank you for the update xerpi. I made a test and as you said nunchuks now work fine. |
Just committed the fix with to the inverted left Y axis.
|
I am able to connect the Wiimote just fine and use any extension, but when I use the Classic Controller (also tried it on a Pro) the sticks seem like they have a limited range of motion. I confirmed this when I launched Minecraft and when I tried to move my character forward, it does so very slowly but when using the Vita's sticks, it moves just fine.
The text was updated successfully, but these errors were encountered: