Apr 29, 2012 at 11:51 AM
Edited Apr 29, 2012 at 2:49 PM
Thanks for the confirmation, that's what I suspected, I did look at the sources but as I have only basic knowledge of C and I'm not familiar with the project's internals I didn't know if I was looking in the right place.
The problem may also be caused by the cheapish controller I have, using jstest (from the linux console project ) I can see that with very little input I have some output but in games like ape escape and wipeout 3 using the analog controller it feels like
I have to give a lot of input before I get some output, and from there it very quickly reaches maximum output.
I'll try to see if there is a way to somehow alter the (non)linearity of the analog axis by some other means and post back if I find anything, so it might serve as reference for other people.
I've been able to make the response a little better by using the jscal utility, linearity is not equal to the real thing (read dualshock connected to a playstation) but a bit more usable. The pad I bought has a digital and an analog mode and both work
reasonably well out of the box with kernel 3.3, however the analog mode can be improved by doing a recalibration. In my case it affects the output values when in digital mode, since digital and analog can report values on the same axis (not at the same time
Just leaving some pointers here for anyone else using linux, the utilities you want to try before starting to use pcsxr are jstest, jscal and fftest to ensure you have everything setup as well as possible.