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

Controller mapping #90

Closed
jotego opened this issue Apr 20, 2022 · 2 comments
Closed

Controller mapping #90

jotego opened this issue Apr 20, 2022 · 2 comments

Comments

@jotego
Copy link

jotego commented Apr 20, 2022

Since a few weeks ago, MiST sometimes maps the only USB joystick I have connected to the second player. I have to unplug and re-connect, then it gets mapped to the first player.

There is also this issue I got, where they found that the controller order for joysticks 3 and 4 is somehow messed up in my cores.

I checked my code and I swap joysticks 1 and 2 (0 and 1 in user_io) when I instantiate user_io. But that works to be the right assignment -at least most of the time.

I don't understand why I have to swap them. I saw that the PC engine core has an option to swap the two joysticks too.

What's going on? Is the joystick order influenced by something else? Should I swap joysticks 3 and 4 too? Do you have some insight on this topic, please?

@gyurco
Copy link
Contributor

gyurco commented Apr 20, 2022

Swapping 0 and 1 is historical. More details here:
#37
I'm not aware that 2 and 3 must be swapped. Maybe it's a hardware issue during enumerating the controllers. 4 controllers can take a lot of power, and one of them might glitch. Or there might be other USB errors. Hard to tell without a debug log output.

@jotego
Copy link
Author

jotego commented Apr 20, 2022

Thank you for your explanation :-)

@jotego jotego closed this as completed Apr 20, 2022
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

2 participants