Learning Proposal: HyperSpin build may still need Keyboard Mode remap, not X-Input

Reusable support point

When a Tank VR or Arcade2TV-style controller works as a mouse/joystick on PC but the main buttons will not assign inside a HyperSpin or similar preconfigured front-end build, do not assume the fix must be switching to X-Input mode.

One confirmed outcome showed the setup working in Keyboard Mode after the customer deleted the existing key entries and remapped them to the input layout expected by the third-party HyperSpin build.

Evidence from ticket 30761

• Customer follow-up 12386201714 said the trackball and joystick worked, but the main buttons would not assign in HyperSpin / MAME on a One Arcade PC build.
• Automation draft 12386207459 suggested a safe direct-PC / keyboard-tester isolation path.
• Manual public reply 12386270534 pivoted to an X-Input explanation and suggested switching to green X-Input mode for HyperSpin.
• Customer confirmation 12386312517 later said the setup ended up working in Keyboard Mode after deleting the current key entries and remapping them to the Carlos/One Arcade input layout.

Draft-quality feedback

• automation_draft_weakness: The draft stayed at the general isolation stage and did not mention that some third-party HyperSpin builds may simply need the stale key entries cleared and remapped to the build's expected keyboard layout.
• manual_reply_improvement: The manual reply made the HyperSpin-specific mapping dependency more explicit and pushed toward a concrete front-end configuration path instead of only general hardware isolation.
• new_drafting_rule: When a third-party front-end build already sees some X-Arcade inputs, draft the next step around the build's expected mapping first. Mention clearing old entries and remapping to the expected keyboard layout before assuming the customer must switch to X-Input mode.
• confidence_effect: The customer-confirmed outcome upgrades the keyboard-mode remap path to a reusable support pattern for similar HyperSpin / One Arcade builds. The earlier X-Input assumption should be treated as unconfirmed for this case.
• storage_decision: reviewable learning proposal plus case-file update.

Safe future wording

If the joystick/trackball already respond on PC but HyperSpin or a third-party front-end will not assign the main buttons, first check whether the build expects a specific keyboard map. Ask the customer to clear the old key assignments and remap them to the layout that build expects before concluding that X-Input mode is required.