Forums » Windows
Joystick Mapping
So, back after a long time, and now I remember why I got frustrated last visit:
1) The UI is all messed up for my X-56 throttle, as it seems to have too many axes. there's plenty of screen room, but after the first two you can't read the labels and can barely click on the drop-downs.
2) Cant map any JS buttons, as soon as I double click on a command, it drops in JOY0BUTTON14 (disconnected the throttle and restarted, in case one of it's toggles or mode switch was in a constant state, but it seems to be button 14 of the stick which is one of the hats. Seems fine in game controller properties in windows, and I have no issues in other flight-space games.
3) GUI path to clear a binding glitches when clicking on it, and nothing is removed.
Guess I'll need a refresher course on config editing /bind.
1) The UI is all messed up for my X-56 throttle, as it seems to have too many axes. there's plenty of screen room, but after the first two you can't read the labels and can barely click on the drop-downs.
2) Cant map any JS buttons, as soon as I double click on a command, it drops in JOY0BUTTON14 (disconnected the throttle and restarted, in case one of it's toggles or mode switch was in a constant state, but it seems to be button 14 of the stick which is one of the hats. Seems fine in game controller properties in windows, and I have no issues in other flight-space games.
3) GUI path to clear a binding glitches when clicking on it, and nothing is removed.
Guess I'll need a refresher course on config editing /bind.
Turns out the X-56 stick seems to be constantly outputting button 14. Of course the editing software doesn't label it by button #'s, but: the 2 hats and 1 POV each have an assignable center-state, that does not show up in Windows' "USB Game Controllers" properties tab. That's my best guess.
I can get around programming the stick's buttons with it's editor using key-press assignments, but can't do any key or button-mapping (like for the beat-up cyborg v1 I use as a left-stick) while the X-56 is plugged in, and without, the left stick takes over as "JOY0"...
Anyone else fly with an X-56?
I can get around programming the stick's buttons with it's editor using key-press assignments, but can't do any key or button-mapping (like for the beat-up cyborg v1 I use as a left-stick) while the X-56 is plugged in, and without, the left stick takes over as "JOY0"...
Anyone else fly with an X-56?