Symptoms
Use this checklist when pressing your intended dash input produces no movement, the dash travels differently from earlier runs, or a movement sequence stops working after an upgrade or hotfix. First separate “no dash at all” from “dash behaves differently.” They are not the same failure. A changed direction or jump count may point to the Omni-dash movement state, while no response on every input may point to an unlock, binding, focus, or device problem.
Write down the course or room, the movement options visible in the game, and whether keyboard input works. That short record prevents several changes from being mixed together.
Likely causes
- Officially confirmed: IGTAP progression unlocks movement abilities, so two saves can legitimately have different movement access.
- Officially confirmed: Hotfix 2 changed the Omni-dash upgrade box into a toggle. One state trades one jump for Omni-dash; the other preserves the previous move set.
- Needs verification: the current default key, rebinding behavior, and every room-specific dash restriction have not been confirmed from an official control reference.
- Common diagnostic possibility: another controller, remapping layer, overlay, or unfocused game window may capture the intended input.
Do not diagnose save corruption from a movement symptom alone. The official hotfix history shows that movement behavior can change through patches, and a save operation is not a safe first response.
Fixes in safe order
- Pause in a safe area. Avoid testing beside a hazard, transition, or checkpoint that could create a new state while you troubleshoot.
- Confirm the ability is unlocked on this save. Use only information displayed in the current game. Do not compare against a video recorded on a more advanced save.
- Read the movement option before changing it. If an Omni-dash toggle is available, note its current state. Change it once, then test the same movement from the same standing position.
- Restart IGTAP once. Fully exit the game, allow Steam to finish any normal synchronization, relaunch, and retest before changing bindings.
- Test one input device. Disconnect unused controllers and close third-party remappers. Test the keyboard first, then a controller separately if you use one.
- Inspect the in-game binding. Confirm that the dash action is assigned and not duplicated in a way that the interface marks as a conflict. This guide deliberately does not name an unverified default key.
- Keep the save untouched. Do not delete, rename, import, or restore save files to fix dash input.
If you use a controller and keyboard behavior is normal, continue with the controller input checklist. If dash direction or jump count changed, use the directional dash and double jump guide.
How to verify the fix
Choose a flat, repeatable area. Start from rest, use the same direction, and try the action three times without changing any other setting. A useful verification answers three questions: did the input register, did the movement match the selected state, and did the result survive a full restart?
Do not treat a single successful attempt during rapid mixed input as proof. If changing only the Omni-dash state consistently changes the observed behavior in the way the option describes, the input is working and the original symptom was probably a movement-state mismatch. If keyboard works but a controller does not, keep the movement setting fixed and isolate the device layer.
When to stop and wait for a patch
Stop making changes if the dash fails with multiple clean inputs, an unlocked ability, and both movement states after a restart. Also stop if entering a particular room repeatedly creates a softlock or if the game cannot return to a stable menu. Preserve the current save and logs before further play.
Report the game version, course or room, selected movement state, input device, exact reproduction steps, and whether the problem began after an upgrade. Avoid claiming a cause you did not test. That evidence is more useful than repeatedly changing the save or reinstalling without a controlled comparison.
Sources and verification status
The Steam store officially confirms the movement-upgrade progression loop. The developer’s Hotfix 2 notes officially confirm the Omni-dash toggle and its jump tradeoff. The June development notes also describe dash responsiveness changes, but those notes predate the full release and are context rather than a guaranteed current specification.
Needs verification: current default bindings, every interaction between dash and individual rooms, and device-specific controller mappings. This page uses safe diagnostic steps around those gaps and does not present them as confirmed mechanics.