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

Two identical controllers seem to both connect to same channel #69

Closed
vaderag opened this issue Sep 19, 2021 · 9 comments
Closed

Two identical controllers seem to both connect to same channel #69

vaderag opened this issue Sep 19, 2021 · 9 comments

Comments

@vaderag
Copy link

vaderag commented Sep 19, 2021

I'm not 100% certain why this is happening but I have two identical 8bitdo controllers and initially thought one must be connecting to something else, but I've been round and turned off all Bluetooth I can find and now can only assume that they are both connecting on the same channel

Any ideas why this might be?

@vaderag vaderag closed this as completed Sep 19, 2021
@vaderag vaderag reopened this Sep 19, 2021
@darthcloud
Copy link
Owner

Do they work properly with BlueRetro one at a time?

Can you get the debug logs: https://github.com/darthcloud/BlueRetro/wiki/Getting-BlueRetro-debug-logs-via-Serial-port-Windows-10

@vaderag
Copy link
Author

vaderag commented Sep 19, 2021

Yep, one at a time is good. Will check the logs when I have a moment

Worth noting the when the second connects only the first will do any kind of control.

I'm still not 100% certain it's not connecting to something random somewhere, but I'm 99% sure

@vaderag
Copy link
Author

vaderag commented Sep 19, 2021

Okay, so I've worked out what it is, and there is an issue but not the same as I thought

The controllers in the pic are all connected
Notice how there are two ones and one 3. Turns out that 8bitdo #2 is connected but not receiving(?) the correct status assignment. So it always shows as P1
I've tried connecting in all positions and irrespective what player it's assigned to it shows #1
Also connection mode doesn't make a difference (except to the button layout), still shows as P1 in Switch or Xinput modes

IMG_20210919_103432.jpg

@darthcloud
Copy link
Owner

This is likely just a cosmetic LED issue, you should have one being P1 and the other being P2

@vaderag
Copy link
Author

vaderag commented Sep 25, 2021

This is likely just a cosmetic LED issue, you should have one being P1 and the other being P2

Oh it is just cosmetic - but it's quite confusing given other controllers seem to connect with the correct # designation and if you put them down it's not obvious what is what.

@GizmoTheGreen
Copy link

it would be really cool if blueretro showed on supported controllers which player port it's being assigned to, and for player 4+ (if applicable) it would show a led pattern like (o= on, x=off)
player 5 [ooxx]
player 6 [oxox]
player 7 [oxxo]
player 8 [xoox]

just to give an idea.

@darthcloud
Copy link
Owner

This allready the case for 4 LED ctrl like ps3 and wii & switch
1-4 is one led like usual
5 is 1100
6 is 0110
7 is 0011

PS4 and 5 got different color for all seven.

Xbox does not have player id LED.

@vaderag
Copy link
Author

vaderag commented Oct 25, 2021

This allready the case for 4 LED ctrl like ps3 and wii & switch 1-4 is one led like usual 5 is 1100 6 is 0110 7 is 0011

PS4 and 5 got different color for all seven.

Xbox does not have player id LED.

Just to note, it still doesn't work on the 4 LEDs on the 8BitDo controllers (PowerA seems fine oddly)

@darthcloud
Copy link
Owner

Closing this, 8bitdo ctrl need to be used in Xinput mode which provides no player LED indicator.

If official SW ctrl where also concerned by this issue it's likely a manifestation of issue #146

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