You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I was experiencing a 'off-by-one' bug in GIMX config, so to speak, meaning if I assign button_id 0 to cross(which is the corresponding button on DS4 controller) after running GIMX software it would show up as circle, meaning it would get button_id 1 (hence the 'off-by-one' name, it goes +1, for some reason).
With the help of GeekyDeaks on gimx forums I was able to come up with a solution, of sorts?
I'd just move all the buttons by -1 button id, and so changing the official Dualshock4.xml I have come up with this.
I also needed to add button_id 17 part using text editor because GIMX-config only allows auto detect (as far as my knowledge goes at least).
The point of me opening this issue is probably just to help others who experience the same bug? and maybe get a valid fix? though I don't know even why it was happening in the first place.
I'm gonna link a forums thread I've made, maybe there's gonna be enough information for someone who is more familiar with the GIMX backend ,than I am, to fix it. Thank you.
The text was updated successfully, but these errors were encountered:
Hello, I was experiencing a 'off-by-one' bug in GIMX config, so to speak, meaning if I assign button_id 0 to cross(which is the corresponding button on DS4 controller) after running GIMX software it would show up as circle, meaning it would get button_id 1 (hence the 'off-by-one' name, it goes +1, for some reason).
With the help of GeekyDeaks on gimx forums I was able to come up with a solution, of sorts?
I'd just move all the buttons by -1 button id, and so changing the official Dualshock4.xml I have come up with this.
I also needed to add button_id 17 part using text editor because GIMX-config only allows auto detect (as far as my knowledge goes at least).
The point of me opening this issue is probably just to help others who experience the same bug? and maybe get a valid fix? though I don't know even why it was happening in the first place.
I'm gonna link a forums thread I've made, maybe there's gonna be enough information for someone who is more familiar with the GIMX backend ,than I am, to fix it. Thank you.
The text was updated successfully, but these errors were encountered: