Different Launchbox APP controller settings?

[CuzzinChizzy]

I use a ton of different controllers in launchbox, I have each one set up in it's appropriate emulator and they're all working fine within those. 

My question is, is there a way to set different mappings to controller buttons within Launchbox for navigating it's menus?
  Like the Pause menu for example.  

Every time I use a different controller like XBOX, DS, or Switch Pro, the buttons don't necessarily match up for navigating the pause menu or within the library window. 
XBOX pads usually work fine, but if I use my Switch Pro controller, it will show up as Pro Controller in the Options > Controller Mappings, but none of the buttons do what they're supposed to. 
Then if I mess around with it enough I can get it to work. But it would be nice if it was more streamlined. 

[AstroBob]

Hi @CuzzinChizzy, thanks for the question here. This question was actually brought up in our recent AMA, so I'll defer to the official response we gave there.

I'm also attaching the stream where we discussed this in a lot more detail (it's linked at the bottom at the correct timestamp for you) 

The question was:  Are there any plans to allow LaunchBox to store mapping for each of my different controllers for navigation (A on Xbox controller vs. B on switch controller) 

We recognize the challenges posed by different controller layouts, particularly when transitioning between devices like an Xbox controller (where the “A” button is in one position) and a Switch controller (where the “B” button may occupy a similar position). These inconsistencies can make it difficult to navigate LaunchBox or Big Box fluidly, which can indeed impact the overall user experience.

That said, creating a framework to manage multiple controller profiles and remap all of their inputs in a unified way is not something on our short-term plans. The main reason is that there are already external tools that do this very well, such as reWASD and X360CE, that provide robust solutions for controller remapping at a system-wide level. These programs allow users to create consistent controller profiles that are applied not only within LaunchBox or Big Box, but also across all applications and emulators on their system. By setting up these profiles at the controller level, users can ensure that each controller behaves the same way across all programs, making the need for specific in-app navigation mappings less critical.

From our perspective, where we do feel we can make an improvement with controller mappings is within the emulators themselves, i.e configuring a controller mapping in LaunchBox, and having that be automatically applied to the emulator's configuration, negating the need for users to have to configure controllers separately via emulators.

 

Hopefully this helps clarify our stance on this, but let me know if you have any further questions on the subject 😊

 

 

[CuzzinChizzy]

Thanks for the reply AstroBob !

 

ill check this out 😊

Edited October 21 by CuzzinChizzy

[thec0r3]

On 10/18/2024 at 4:32 AM, AstroBob said:

Hi @CuzzinChizzy, thanks for the question here. This question was actually brought up in our recent AMA, so I'll defer to the official response we gave there.

I'm also attaching the stream where we discussed this in a lot more detail (it's linked at the bottom at the correct timestamp for you) 

The question was:  Are there any plans to allow LaunchBox to store mapping for each of my different controllers for navigation (A on Xbox controller vs. B on switch controller) 

We recognize the challenges posed by different controller layouts, particularly when transitioning between devices like an Xbox controller (where the “A” button is in one position) and a Switch controller (where the “B” button may occupy a similar position). These inconsistencies can make it difficult to navigate LaunchBox or Big Box fluidly, which can indeed impact the overall user experience.

That said, creating a framework to manage multiple controller profiles and remap all of their inputs in a unified way is not something on our short-term plans. The main reason is that there are already external tools that do this very well, such as reWASD and X360CE, that provide robust solutions for controller remapping at a system-wide level. These programs allow users to create consistent controller profiles that are applied not only within LaunchBox or Big Box, but also across all applications and emulators on their system. By setting up these profiles at the controller level, users can ensure that each controller behaves the same way across all programs, making the need for specific in-app navigation mappings less critical.

From our perspective, where we do feel we can make an improvement with controller mappings is within the emulators themselves, i.e configuring a controller mapping in LaunchBox, and having that be automatically applied to the emulator's configuration, negating the need for users to have to configure controllers separately via emulators.

 

Hopefully this helps clarify our stance on this, but let me know if you have any further questions on the subject 😊

 

 

Telling users to create their own controller profiles using external programs is a cop-out imo.  This is a feature that should be a priority as far as I'm concerned. I've been using the Launchbox premium since 2018 and have paid for a new license several times. The fact that I can use this feature on Kodi or Steam Big Picture mode, and it costs nothing is really irritating. I thought the idea of using this front-end was to create less work for the user not more.