We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Let say I only have my DualShock 4 plugged, I'll have this:
Perfectly normal, now if I plug my 8bitdo N30 Pro, the new one "replaces" my DS4 and the DS4 moves to port 1:
PLEASE NOTE:
Video of the issue: https://youtu.be/76lMqzjdj6Q
I read about this issue yesterday on Discord and wanted to try, I didn't see any issue about it poping up so here we go.
1st controller stays as player 1 when a new one is plugged.
2nd plugged controller becomes player 1 and previously plugged controller switches to player 2.
Doesnt seem to be a new thing, I went back up to 1.6.7 (the oldest I could get from the buildbot) and it's already acting like that.
The text was updated successfully, but these errors were encountered:
Some information on this comment.
Sorry, something went wrong.
Thanks for the link! I like the idea of having to press a button to add a controller just like on Android.
Ditto, something similar to this would be great I think.
Closing, thanks to #16647 ❤️
No branches or pull requests
Description
Let say I only have my DualShock 4 plugged, I'll have this:
Perfectly normal, now if I plug my 8bitdo N30 Pro, the new one "replaces" my DS4 and the DS4 moves to port 1:
PLEASE NOTE:
Video of the issue: https://youtu.be/76lMqzjdj6Q
I read about this issue yesterday on Discord and wanted to try, I didn't see any issue about it poping up so here we go.
Expected behavior
1st controller stays as player 1 when a new one is plugged.
Actual behavior
2nd plugged controller becomes player 1 and previously plugged controller switches to player 2.
Steps to reproduce the bug
Bisect Results
Doesnt seem to be a new thing, I went back up to 1.6.7 (the oldest I could get from the buildbot) and it's already acting like that.
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: