Doesn't work properly on some x-box like gamepads and some PS3-like gamepads.

[Lazerbeak12345]

With very thorough testing, I have determined this to be the case, and a plausible way to fix it.

Fixing the PS3-like Gamepads

The reason these don't work (yet) is because of these points:

NOTE: All of these problems in this section are unique to PS3 gamepads - and typically the off-brands. In my experience, it is actually easier for someone looking for a budget gamepad to find a used one of these then any other gamepad.

• The left y axis is swapped
  • FIX: multiply by -1
• The indexes of the right axis should be (2,5), but the library is (currently) not compatible with that. (not even as a re-mapping)
• The dpad is not the last four buttons. In fact it is the last axis. The resting position of this d-pad varies from manufacturer to manufacturer, but it is (in my experience) always outside of the range -1 to 1. The rest of the positions are below, clockwise, starting at up, ending at left-up from -1 increasing by 2/7 till 1. (These are consistent)
  • -1 up
  • -0.7142857313156128 right-up
  • -0.4285714030265808 right
  • -0.1428571343421936 right-down
  • 0.14285719394683838 down
  • 0.4285714626312256 left-down
  • 0.7142857313156128 left
  • 1 left-up

Symptoms

Here are the symptoms of this:

1. The last axis is outside of the range of -1 to 1. (See above)
2. Sometimes, an extra gamepad will appear with vendor of 0000 and product 0000
   • Unreliable

Fixing the x-box like gamepads

The reason these don't work (yet) is because of these points:

NOTE: All of these problems in this section are unique to older x-box gamepads - and typically the off-brands. In my experience, many cheap Nintendo Switch compatibles fit in this category, along with a few other cheap gamepads. These, however, aren't as common as the above.

• The left y axis may be swapped. (I am about 65% sure that it is)
• The indexes of the right axis should be (4,5)
• The dpad is mapped as an axis namely always the last two. (specific numbers not constant across models).
  • You could just trigger the dpad event from the axis handler or something.

Symptoms

Here are the symptoms of this:

1. There are less then 16 buttons.
   • This, unfortunately is also the case for some NES-like gamepads, so we may have a problem there... More testing for other (reliable) symptoms needed.

[Lazerbeak12345]

FYI, I am and have been working on a patch for some time. The problem is it is a patch for the latest commit on master, and might not work with the new commits in the re-write (see the diff). At the very least, my PR, when I submit it should be useful for documentation of how it might be done in the re-write.

[Lazerbeak12345]

Btw, this seems to only happen on windows. I've never been able to recreate this erroneous behavior on linux.