Skip to content
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

[linux] Hat #0 Button 0 is "True" when untouched #31

Closed
HidingCherry opened this issue Jan 17, 2015 · 3 comments
Closed

[linux] Hat #0 Button 0 is "True" when untouched #31

HidingCherry opened this issue Jan 17, 2015 · 3 comments

Comments

@HidingCherry
Copy link

JoyStick: Microsoft SideWinder Force Feedback 2

As long as the hat is untouched (to no direction pushed), the hat #0 button 0 is always true.
This is an issue because when you set an axis, the button gets into the "combination" and needs to be true so that axis works.

Workaround: give us an option in Controller Configuration to ignore/disable buttons.

@Gaiiden
Copy link

Gaiiden commented Feb 5, 2015

would like to confirm this and also add it is an issue on Win7 x64 as well using a Saitek X55. If it is possible, rather than outright removing the ability to set buttons/axis together I would also suggest an option to ignore buttons on a per device basis. The reason for this is the axis+button assignment is actually useful on my X55 throttle which has a switch for 3 mode settings. So being able to assign the throttle axis when only Mode 1 (button#30) is True is beneficial. But on the joystick I can't use the hat because anything other than its default position will cancel out the axis

@MatthAlex
Copy link

I would also like to confirm that in Win7 x64, KSP x86, v.1.4.6, using a Logitech Extreme 3D Pro, when left untouched AND calibrated several times, during configuration, Hat button left seems always True. When you try to map ANY button, it goes into a combination of the button and Hat#0 Button 0. Also, pushing the button turns True into False.

Thanks in advance, both nlight and ddaf for the great job on this mod!

@badpandabear
Copy link
Contributor

I just submitted a pull request for this. The problem was in the SDLController, so Windows users shouldn't see it if they switch to using Xinput. Unless there's another problem I don't know about because I'm a linux user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants