@Concat I've tried the trinary flag, but didn't have any effect either.
For the buttons, just load dosbox without a game. Map something like "T" to your A button, and see if you can type a T with the button. No idea why a button mapping wont work. Thats the easiest thing to do in this tool...
I'll try that later.
Here's another thing I was thinking about trying out though.
• min – The reported minimum value on the axis. Used for determining
trigger levels.
• max – The reported maximum value on the axis. Used for determining
trigger levels
Except I'm not 100% sure how to implement it, but I was thinking something likes this...
Assuming my thumbsticks have 'idle' axis values ranging between 0-2000 and either -32767 or 32767 when hold to the max in a direction, then defining a min/max value close to the max value should work? (in theory)
# so for movement to the left
axis vendor=0x045e product=0x028e src=2 target=mouse axis=0 min=-30000 max=-32767
# movement to the right
axis vendor=0x045e product=0x028e src=2 target=mouse axis=0 min=30000 max=32767
# up movement
axis vendor=0x045e product=0x028e src=3 target=mouse axis=1 min=-30000 max=-32767
# down movement
axis vendor=0x045e product=0x028e src=3 target=mouse axis=1 min=30000 max=32767
EDIT: Well that seemed to have fixed the deadzone issues, but besides that nothing is working like it should.
Currently the mouse cursor is fixed top left and won't move except for when I push the thumbstick all the way to the left, then it moves to the bottom left in a flash and when I release the thumb it moves back to top left.
It seems to me like something is messed up when it comes to button/axes values, and it's not registering the values as presented by jstest
Really weird because DOSBOX's internal mapper works perfectly fine, if only it had the possibility of mapping the mousekeys.
I've also tested running just dosbox with the Y button mapped to the letter y but it's not responding.
