TROUBLESHOOTING
Controller connected, but input or rumble is wrong
Separate controller detection, button mapping and rumble. Check model-specific reports without applying one controller's workaround to all devices.
On this page
A Bluetooth “connected” status does not prove that game input recognizes the controller. Working input, correct buttons and rumble need separate checks.
No input at all
Check the system connection, then whether S2Arm lists the controller. If the OS does not expose it as a game controller, check the manufacturer's supported connection modes and your device OS before rebuilding games.
For a multi-mode third-party controller, consult the manufacturer's mode instructions. In #456, a Beitong BTP-KP20 paired in Switch mode without input; the reporter confirmed input after switching to Xbox mode. This is one model's report, not a universal mode recommendation.
If S2Arm detects the controller but a game stays at its “press A on the controller” prompt, v0.2.3 includes a fix for a game rejecting the controller type. On a newer version, record the specific game and scene if the issue persists.
Success check: The controller appears and can operate the affected game. Otherwise report its exact model and mode.
Input works, but confirm and back are reversed
v0.2.5 changed DualSense / DualShock defaults to × confirm and ○ back. To restore the old ○ confirm behavior, the maintainer points to the gear menu's controller / motion settings and the option that maps buttons by position. iPhone users need to install to the phone again after updating the computer launcher to apply the change. Maintainer reply and confirmation
Success check: Test confirm, back and directions in a menu before replaying a long scene.
Input works, but there is no rumble
Check that the controller and connection mode support rumble and that the game action should trigger it. Check S2Arm's rumble setting and try its available levels.
In #466, the PS button mapping fix had shipped, while iOS external-controller rumble remained under investigation. The two are not both resolved just because they share a thread.
v0.2.5 also lists a rumble-routing fix for a specific wired MFi GameSir G8+ variant, explicitly without testing on that hardware. Do not generalize it to all GameSir controllers.
Success check: Rumble works during an action that should trigger it. If not, report the exact model, cable / Bluetooth mode, settings and scene.
Joy-Con 2 on Mac needs SYNC every time
#521 distinguishes a Mac remembering a device from completed controller host bonding. The reporter used a long press on SYNC to pair again. An any-button reconnection improvement remained discussion / development work in the reviewed sources, with no confirmed release here.
Use the currently supported pairing process. Do not write proposed bonding information to the controller or look for a setting that has not been confirmed as shipped.
Report the part that fails
Check detection, input, mapping and rumble separately. Include exact controller model, wired / Bluetooth connection, selected mode, OS, S2Arm version and game. A connected status does not answer all four questions.
Sources are user reports and maintainer statements. This site has not tested the controllers. Use the problem report outline if needed.