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
Controller Triggers not working correctly #218
Comments
Same here. Tried to calibrate with jscal but that haven't solved the problem. I can do all tests you want to solve the problem if needed. |
Hello, I have exactly the problem that @Marioheld describes, and can't figure out a solution yet, which is very annoying :(. If someone has a solution for this, please share :) |
I have the same issue, using ps3 controller via sixad, abs_deadzone settings in mapping file does not help, only way to have analog triggers with games is set deadzone in game to 50%. I am happy to try any suggestions edit: have tried launching a uplay game direct using -app and not steam. The game was The Crew, it is unplayable with analogue triggers as there is no throttle/brake deadzone settings. This is really starting to drive me nuts (no pun intended) edit 2: SOLUTION, use xboxdrv to emulate ps3 controller as xbox controller, triggers then work as intended |
I used sixad to control moonlight via a PS3 Controller (original Sixaxis) which works perfectly with my custom map file except for the triggers (R2 and L2). When i start a stream the triggers value is set to 0 but when i press the triggers and leave them again the input stays at 127 (in the middle) instead of going back to 0. When pressing again they are correctly working up to 255 but again only goong back to 127. This causes that in racing games for example the break lights stays on and the breaks will not released completely.
The text was updated successfully, but these errors were encountered: