Dusk controller not working
This page is for Dusk and Dusklight input problems: an 8BitDo controller is detected but does not map correctly, L2 and R2 behave like the wrong buttons, Steam Deck input fights native input, Android Bluetooth layout changes after an update, or gyro and mouse aim feel doubled.
What changed in Dusklight v1.2.0
Dusklight v1.2.0 adds an option to remove button binds with only a controller and fixes shoulder analog values. That is important for Steam Deck, Android handhelds, living room PCs, and users who are not near a keyboard when a bad bind needs to be cleared. If L, R, L2, R2, or menu buttons feel wrong after an update, do not immediately reinstall the app. Check bindings first, remove duplicates, then test one connection mode at a time.
For users who just need a normal setup path, use the new Dusk Twilight Princess controls guide. Stay on this page when the controller is detected incorrectly, labels are shifted, trigger bindings do not persist, or Steam Input and native Dusklight input are fighting each other.
Input bugs are especially confusing because the same physical controller can present itself differently depending on Bluetooth mode, USB mode, firmware, operating system, Steam Input, Android, or a third-party remapper. The correct fix for one device can be wrong for another. That is why this page separates clean testing from device-specific advice.
Clean controller reset
- Update to the latest official Dusklight release.
- Disconnect extra controllers so only one device is active.
- Disable third-party remappers for the first test.
- On Steam Deck, decide whether Steam Input or native Dusklight input owns the mapping.
- Open Controller Configuration and clear duplicate trigger or shoulder bindings.
- Bind movement, camera, attack, item use, menu, and first-person camera in a simple order.
- Test in a safe area before loading a complicated save or adding gyro changes.
This reset prevents one common mistake: stacking fixes. If Steam Input, DS4Windows, an Android controller profile, and Dusklight native binding all change the same button, the final result can look random even when each layer is working as designed.
8BitDo Bluetooth controller issues
The official tracker includes an open report around an 8BitDo Ultimate Bluetooth Controller being detected incorrectly or not receiving input correctly. That does not mean every 8BitDo controller is broken. It does mean 8BitDo users should report exact model, firmware, connection mode, platform, and whether the controller appears as a Switch Pro Controller, Xbox controller, or another device.
| Question | Why it matters |
|---|---|
| Bluetooth or USB? | The same controller can expose a different layout over each connection type. |
| Switch mode, XInput, or DInput? | Dusklight may see a different device depending on the mode. |
| Firmware version? | Controller firmware can change gyro, trigger, and profile behavior. |
| Steam Input enabled? | Steam can remap controls before Dusklight sees them. |
| Android or Windows? | Platform input APIs can label buttons differently. |
If an 8BitDo controller is your main device, test USB first if possible, then Bluetooth. If one mode works and the other does not, that is useful evidence. If both fail, test the same controller in another game and write down whether only Dusklight has the issue.
Android controller layout changed
Android controller mapping can vary by phone, Android version, controller mode, and firmware. Current reports around joystick, trigger, and saved controller configuration behavior make Android worth testing separately from Windows or Steam Deck. The practical fix is to treat Android as its own input path, not as a copy of a desktop profile.
On Android, start with a clean profile. Pair the controller fresh, launch Dusklight, open Controller Configuration, and bind the main controls manually. If L2 or R2 opens a menu, acts like Start, or maps to the wrong shoulder, clear the conflicting digital trigger entry and bind again. If the layout still changes after a reconnect, record the Android version, device model, controller model, and connection mode before reporting.
Steam Deck input
Steam Deck users have two powerful input systems available: Steam Input and Dusklight's own controller configuration. Both are useful, but using both aggressively at the same time can create double mappings. For the first test, use a plain gamepad template in Steam and let Dusklight handle in-game bindings. After that works, add gyro, back buttons, radial menus, or custom shortcuts.
If the Deck controls do nothing, confirm Dusklight was added as a non-Steam game correctly, launched through Steam when you expect Steam Input, and focused as the active window. If you launch from Desktop Mode outside Steam, Steam Input may not be the input layer you think it is.
Gyro and mouse aim
Dusk supports modern input ideas such as gyro and mouse aim, but they are easy to double up. If aiming feels too fast, jittery, or doubled, choose one owner. Either configure gyro through Dusklight or configure it through Steam Input, not both at once. Then test first-person camera and normal movement separately.
Older releases also fixed issues where invert first-person settings affected gyro in a way users did not expect. If you changed inversion settings in an older build, retest those settings after updating before assuming your controller profile is permanently wrong.
When to report a controller bug
Report only after a clean input test. A useful issue includes: Dusklight version, operating system, controller model, connection type, firmware version if known, whether Steam Input or a remapper is active, what Dusklight detects the device as, and the exact wrong button behavior. Link to the official tracker only when the problem is reproducible without mods or unusual overlays.
Joystick and trigger report
Current report around joysticks and triggers becoming unbound.
Config not saving
Current report around controller configuration not saving correctly in v1.2.0.
Controller FAQ
Should I use Steam Input or native Dusklight binding?
Use whichever gives you a stable baseline, but do not troubleshoot with both doing heavy remapping at the same time. Start simple, then layer advanced mapping later.
Why do L2 and R2 act like the wrong buttons?
Duplicate trigger binds or analog/digital trigger confusion can cause this. In v1.2.0, use the controller-only bind removal option if needed, then bind again.
Does controller troubleshooting require a new download?
Only if you are not on the official latest build or you used an unofficial mirror. Most controller problems are profile, mode, firmware, or platform mapping issues.
Where should I go next?
Use controls setup for a clean first profile, Steam Deck setup for Deck-specific launch flow, Android setup for phone and handheld notes, and known issues for current official reports.