Cannot remap gamepads with inertial sensors

[xarvh]

Because the library can't distinguish between a number changing because the user deliberately activated a control, or just moved the gamepad.

[xarvh]

Possible solution:

Base input recognition rather than on the absolute value, on the difference between the max value and the min value?

Needs to be tested.

[xarvh]

A (solid?) solution could be to allow the user to see all the raw outputs, not unlike http://html5gamepad.com/ does, and then for any input select which action it should be bound to.

For any axis and button in the raw input, this manual mode would show to the user:

• The raw input id (ex: "Axis 4")
• The current analog value as a slider
• The current digital value as a switch?
• The mapped function (ex: "Move Left"; "unused" if none)
• The mapped inverted function (ex: "Move Right"; "unused" if none)

Pros

• Should solve the issue
• Should solve Firefox produces -1 when analog triggers are in rest position #25
• Giving the user full control of the mapping could work around future and unforeseen issues?

Cons

• It's a lot of work and I don't know if I have the time
• Requires a way for the UI to switch from the automatic "easy" mode to the new manual mode
• It is a complex UI that will require a lot more screen space.

[Malax]

This is probably a way to go, even though it's not very convenient for the user. It's a shame that the gamepad API is in such a bad shape. :(

What do you think about collecting those inputs and sending them to a central server where they can be analyzed? Maybe there is some common data in there that is yet to be seen that might make more game pads compatible out of the box.

[xarvh]

That would be way beyond the time I can dedicate to the project.
I am not sure that studying the data in aggregate would yield anything reliably useful.
There would be also issues about trusting user-produced input and keeping your apps up to date with the latest changes in the database.