Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retroarch still cant differentiate between Xbox Controllers #17483

Open
2 tasks done
Yasaka7 opened this issue Jan 28, 2025 · 3 comments
Open
2 tasks done

Retroarch still cant differentiate between Xbox Controllers #17483

Yasaka7 opened this issue Jan 28, 2025 · 3 comments

Comments

@Yasaka7
Copy link

Yasaka7 commented Jan 28, 2025

Is there an existing issue for this?

  • This is a bug in RetroArch frontend
  • I have searched the existing issues

Description

So i have an 8bitdo controller which uses xinput and works fine without changing anything in the button layout. But i also have a gamecube controller and i use delfinovin to emulate an xbox controller so i can use my gamecube controller in retroarch, games etc.
However the layout is a different one so i need to map every button manually. when i save the config, it saves the config for an xbox 360 controller. however the 8bitdo is also detected as an xbox 360 controller.

The problem: when retroarch saves the config it always saves it for ANY xbox360 controller since the configs name is xbox 360. so i have to remap my controller everytime i change the controller.
This is a problem for years now and my workaround is that i just use 2 completely different retroarch instances so i can save my button layout.

Please implement that you can actually name the cfg file yourself and that you can choose which cfg file to load for which controller or change the way Controllers are detected.

Expected behavior

Retroarch should detect Controller differently so even if both are detected as XBOX 360 controller Retroarch can still differentiate between those.

Steps to reproduce the bug

  1. Have to different controllers with different internal button mapping that your computer detects as XBOX 360 controller.
  2. Try saving the correct button layout for each one.
  3. Since for Retroarch they are the same it will overwrite the same cfg file for both controllers and you have to remap the other controller again in order to use it.

Version/Commit

1.20.0

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

Windows 10

Affected Cores

No response

Environment information

No response

Relevant log output

@hizzlekizzle
Copy link
Contributor

How are we supposed to tell them apart if they're both giving us exactly the same (false) information?

@Yasaka7
Copy link
Author

Yasaka7 commented Jan 28, 2025

How are we supposed to tell them apart if they're both giving us exactly the same (false) information?

Like mentioned, if this isnt possible it would be really useful if one could name the cfg file when its saved, and actually be able to load a certain cfg file. because right now you cant even load a cfg. you only can save one and its loaded automatically.

@cmitu
Copy link
Contributor

cmitu commented Jan 29, 2025

It's possible if you change the joypad profiles' path (option: joypad_autoconfig_dir), which you can set in a separate .cfg with --appendconfig.

Another option would be to configure (if possible) the remapping software (delfinovin ?) to use a different name or Vendor/Product IDs for the emulated Xbox controller. RetroArch can use also the Vendor/Product IDs to differentiate between 2 controllers that have the same name and load their corresponding profiles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants