Symptoms
Use this checklist when IGTAP ignores a controller, only some actions respond, prompts appear inconsistent, or controller input interferes with keyboard testing. First determine whether the device works outside the game. A controller that is absent from the operating system or Steam cannot be fixed through an IGTAP movement option.
The official Steam feature list reviewed for this guide does not explicitly confirm controller support, supported device families, or default mappings. Steam also displays user-applied tags, including Controller, but a tag is not the same as a developer support specification. Compatibility therefore remains Needs verification.
Likely causes
- The operating system or Steam does not detect the device.
- Multiple connected controllers create an unexpected device order.
- Steam Input and a native or third-party remapper both translate the same input.
- A binding is incomplete, duplicated, or based on a community layout intended for another build.
- The game window is not focused, or an overlay captures input.
- The game may not support the device or action in the way the user tag implies.
Do not interpret a controller-only dash failure as proof that dash progression is broken. Establish whether a keyboard can perform the same unlocked action first.
Fixes in safe order
- Close IGTAP and connect only the controller you want to test. Prefer a direct wired connection for the first comparison if your device supports it.
- Confirm the device responds in the operating system and Steam controller test. If it does not, solve that device-level problem before launching the game.
- Close third-party remappers and controller utilities for one clean test. Do not stack them with Steam Input.
- Launch IGTAP and test basic menu navigation before testing a movement sequence. This separates global detection from an action binding.
- If there is no response, close the game, change Steam Input once, relaunch, and retest. Test enabled and disabled as separate runs rather than switching several options together.
- Review the active layout. Use action names shown by the game or Steam; this guide does not invent button labels.
- Test keyboard alone. If keyboard works, keep progression and movement options unchanged while investigating the controller layer.
For an input that registers but produces unexpected movement, use the directional dash guide. For no dash on any device, use dash not working.
How to verify the fix
Verify in two stages. First, confirm stable navigation or another harmless input in the menu. Second, load a safe area and test one movement action three times. Restart the game with the chosen Steam Input setting and repeat. A fix is credible when the same device and configuration work after that restart.
Record whether the controller is wired or wireless, its model as reported by Steam, the Steam Input state, and any layout name. If only one action fails, note the action name rather than assuming a default button. Avoid rapidly alternating keyboard and controller during the verification run.
When to stop and wait for a patch
Stop after a clean device test, one-controller configuration, both Steam Input states, and a restart if IGTAP still does not respond. Repeatedly installing community layouts or remappers makes the result harder to diagnose and can introduce duplicate inputs.
Report the operating system, controller model, connection type, Steam Input state, whether menus respond, whether keyboard works, and the exact action that fails. Because official native support and default mappings are not confirmed here, wait for a developer statement before treating a specific device as guaranteed compatible.
Sources and verification status
Officially confirmed: the Steam store page lists the game’s official feature set and separately displays user-applied tags. The reviewed official feature list includes Steam achievements and Steam Cloud but does not state a controller-support level.
Needs verification: native controller support, supported device models, glyphs, default mappings, rebinding behavior, and platform-specific compatibility. The steps above test the input chain without presenting those unknowns as facts.