Guides
Alabaster Dawn Controller Not Working: Fix Order
Quick Answer
If Alabaster Dawn controller input is not working, use the checklist and saved test log: restart with one controller connected, check Steam Input, test wired and Bluetooth, confirm device order, reload the game, and check prompts before changing a main save.
Controller Fix Log
Test One Change At A Time
Save the device, connection, Steam Input state, and result so you can undo bad fixes quickly.Alabaster Dawn controller issues are best fixed in a clean order. Do not change five settings at once inside a main save. Start with one controller, check Steam Input, test wired and Bluetooth, restart the game, then confirm prompts and movement before continuing.
Last checked: May 29, 2026. Controller behavior can change with Early Access patches, Steam Input updates, OS updates, and device firmware.
Quick Answer
| Step | What to do |
|---|---|
| 1 | Close the game |
| 2 | Connect only one controller |
| 3 | Check Steam Input settings |
| 4 | Test wired if Bluetooth fails |
| 5 | Restart Steam and the game |
| 6 | Check prompts and movement on a test save |
Fix Order
- Disconnect extra controllers, wheels, virtual devices, or handheld docks.
- Restart Steam.
- Open the game’s controller settings from Steam.
- Try the default Steam Input profile.
- If that fails, toggle Steam Input off or to a different profile.
- Test the controller wired.
- Test Bluetooth only after wired works.
- Launch the game and check the title menu.
- Start a test save, move, attack, dodge, open menus, and save.
Controller Fix Log
Use the tool above to save the controller, connection type, and result. This is useful because controller fixes are easy to confuse after several restarts.
| Save this | Example |
|---|---|
| Controller | Xbox pad, DualSense, 8BitDo, Steam Deck controls |
| Connection | Wired, Bluetooth, docked, handheld |
| Result | No input, wrong prompts, fixed after restart, works in menu only |
If a test fails, save it before changing another setting. A short log can reveal that wired works, Bluetooth fails, or prompts refresh only after restarting Steam.
Common Causes
| Symptom | Likely cause | Try |
|---|---|---|
| No input at all | Device not detected or wrong Steam Input state | Reconnect one controller and restart Steam |
| Buttons work but prompts are wrong | Prompt layer or profile mismatch | Change profile and reload |
| Movement works but actions do not | Partial mapping | Check layout and bindings |
| Bluetooth drops | Pairing or battery issue | Test wired |
| Works in menu, fails in game | Stale input state | Restart game and test save |
When To Wait For A Patch
Wait or report the issue if the same controller works in other Steam games, wired and Bluetooth both fail, Steam Input profiles do not change behavior, and the issue appears after a specific update. Early Access input bugs can be real, and forcing a long save with broken controls is a bad trade.
What To Test Before A Main Save
| Action | Pass condition |
|---|---|
| Movement | Stick or D-pad moves cleanly |
| Attack | Button responds without delay |
| Dodge or defensive action | Timing is reliable |
| Menu navigation | You can change items, skills, or settings |
| Prompt display | Buttons match your controller well enough |
| Save reload | Quit and resume without losing control state |
Do not ignore partial input. A controller that works in menus but fails in combat is still not ready for a main route.
Next Pages To Open
- Alabaster Dawn Steam Deck
- Alabaster Dawn Beginner Guide
- Alabaster Dawn Early Access
- Alabaster Dawn Hub
Sources
FAQ
Why is my controller not working in Alabaster Dawn?
It may be Steam Input, device order, Bluetooth pairing, a stale prompt state, or an Early Access input bug.
Should I use Steam Input?
Test both the default profile and Steam Input options. Some setups work better with Steam Input enabled, while others need it disabled or reset.
Should I troubleshoot in my main save?
No. Use the title screen or a test save before risking a main route.
Can this page save controller tests?
Yes. The controller fix log saves your device, connection, and result in your browser.