Re: [w3c/gamepad] Terminology of inputs. (#131)

I think NES, SNES, and GC are adequately covered by "Standard Gamepad". For a gamepad to use the Standard mapping it doesn't need to have every button or axis defined by the spec, it's fine if some buttons or axes are missing. NES and SNES style gamepads should have no axes, only buttons.

N64 doesn't match the Standard Gamepad layout but I think it's still better to consider it a Gamepad rather than something new (Standard N64?). If we treat it as something other than a Gamepad then it won't function correctly in apps that expect a Standard Gamepad. Instead I think we should do our best to shoehorn it into Standard Gamepad. Currently Chrome doesn't support any N64 adapters but if it did I'd probably map it like this:

buttons[0] = A button
buttons[1] = C-down
buttons[2] = B button
buttons[3] = C-left
buttons[4] = L button (left shoulder)
buttons[5] = R button (right shoulder)
buttons[6] = Z trigger
buttons[7] = unmapped (would be right trigger)
buttons[8] = unmapped (would be Back/Select)
buttons[9] = Start
buttons[10] = unmapped (would be left stick click)
buttons[11] = unmapped (would be right stick click)
buttons[12] = D-pad up
buttons[13] = D-pad down
buttons[14] = D-pad left
buttons[15] = D-pad right
buttons[16] = unmapped (would be Meta)
buttons[17] = C-right (extra button 1)
buttons[18] = C-up (extra button 2)

axes[0] = analog stick X
axes[1] = analog stick Y
axes[2] = unmapped
axes[3] = unmapped

I think a new "Standard Wheel" addition to the spec makes a lot of sense, possibly we would add "handle" and "spring" inputs to the spec to represent the wheel and pedals. However, these would still be represented by values in the axes and buttons array, we'd just give special meaning to the values in particular indices like we do for Standard Gamepad.

A "Standard Flight Stick" would probably make sense as well, but I don't know as much about the variety of inputs on flight sticks. It would be helpful to do a survey on modern flight sticks to see which inputs are common enough to be included in the standard.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/131#issuecomment-646344000