Individual Controller Mappings for LaunchBox & Big Box Navigation

Summary:

Add support for per-controller navigation mappings in LaunchBox and Big Box, allowing users to assign buttons independently for each detected input device 🎮.

Problem:

Currently, navigation mappings (e.g., select, back, start) are applied globally across all controllers. However, “Button 1” can mean different things depending on the controller—what’s “A” on an Xbox controller may be “B” on a Switch or DualShock controller. This inconsistency makes it confusing to navigate the interface, especially for users who frequently switch between controllers or use a wide range of input devices (e.g., arcade sticks, light guns, GameCube adapters).

Proposal:

Display a list of all detected controllers and allow individual navigation mappings for each one. This would eliminate guesswork and make the experience consistent, intuitive, and seamless—no matter which controller is picked up.

Benefits:

• Removes friction from switching controllers

• Provides a consistent user experience without needing third-party tools

• Reduces accidental inputs or confusion caused by inconsistent layouts

• Aligns with the needs of emulation-focused users who use multiple controller types regularly

Community Insight:

This is a long-standing request with multiple duplicates on BitBucket and consistent community support. Users emphasize that while external tools like reWASD or X360CE exist, this should be a native quality-of-life feature.