Skip to content

Gamepad indices do not match Windows / indicator LEDs #4286

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

Open
shambles1980 opened this issue Apr 8, 2025 · 2 comments
Open

Gamepad indices do not match Windows / indicator LEDs #4286

shambles1980 opened this issue Apr 8, 2025 · 2 comments
Labels
App: EmuHawk Relating to EmuHawk frontend Request: Feature/Enhancement For feature requests or possible improvements

Comments

@shambles1980
Copy link

Running windows 10 with two 8bitdo sn30 pro usb, and two generic xbox 360 pads. These indicate which one is player 1 - 4 with the led lights.
P.c games on the system adhere to this (the game pad with player one indicated via LED are indeed player 1 or player 2-4 respectively)
the Mame plus command line version also adheres to this In fact all systems i have setup adhere to this. Apart from emuhawk.

Every emulator i set up using emuhawk detects the player 1 controller as x4 ,player 2 is x3, player 3 is x2, and player 4 is x1.

this is 100% backwards and is making the use of emuhawk impossible for me.
If i chose to use the emulators nativity (example) if i use snes9x.exe and configure that, it detects the controllers correctly.
i would prefer to use emuhawk as i prefer to edit an ini file via scripting as and when needed. and not all emulators support this. But currently i am having to use all the individual emulators rather than emuhawk because of this issue.

i cannot find any way to fix this behaviour in emuhawk.

@YoshiRulz YoshiRulz added Request: Feature/Enhancement For feature requests or possible improvements App: EmuHawk Relating to EmuHawk frontend labels Apr 9, 2025
@YoshiRulz YoshiRulz changed the title Xinput devices are the incorrect number. Gamepad indices do not match Windows / indicator LEDs Apr 9, 2025
@Morilli
Copy link
Collaborator

Morilli commented Apr 9, 2025

Could you check the controller info emuhawk reports on startup? Open a cmd window in the bizhawk folder and run .\EmuHawk.exe > log.txt, then upload that log here.

Maybe @CasualPokePlayer has an idea if anything is wrong with the controller code. I have briefly checked the code and it seems fine. I also don't have multiple controllers to effectively test this.

@CasualPokePlayer
Copy link
Member

Does say mGBA or melonDS also have the same issue? They also have SDL used for input backends.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App: EmuHawk Relating to EmuHawk frontend Request: Feature/Enhancement For feature requests or possible improvements
Projects
None yet
Development

No branches or pull requests

4 participants