Quick answer: Set an initial selected element when each menu opens, define explicit navigation between elements, and restore focus when menus change so the controller always has somewhere to go.
Controller navigation that does not work is missing focus and navigation wiring. Setting those up makes menus gamepad-friendly. Here is how.
How to fix it
1. Set an initial selection
When a menu opens, select a default element so the gamepad has a starting point. Without a selected element, directional input has nothing to move from and the controller does nothing.
2. Define navigation links
Ensure each element knows its neighbors (up, down, left, right), either via automatic navigation or explicit links. Gaps or wrong links leave the cursor stranded or jumping unexpectedly.
3. Restore focus on menu changes
When a popup opens or a menu changes, move focus into it, and restore the previous selection when it closes. Losing focus mid-flow strands a gamepad player with no selected element.
Catching the ones you can't reproduce
The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.
Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.
This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.
Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.