-
-
Notifications
You must be signed in to change notification settings - Fork 141
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 Request]: Black Shark (黑鲨双翼手柄) #882
Comments
English only, please. |
That's ok, I just want to have some idea of what this controller is. Do you have a link to a user manual or something? (Chinese is fine, I can translate it) Does the controller connect to the system at all? Many newer controllers are using Bluetooth LE, which isn't supported in the release versions of Mission Control. I have builds supporting BLE available on my discord server that you could try to connect it with. |
|
Haha, images might be a little harder to run through a translator :p. But I see 4.2 and 4.4 listed in there, which are likely what I was looking to see (bluetooth version numbers). 4.0+ usually indicates that it's a BLE controller, so yeah, give the discord build a try (see #testing-ble channel). Note that there is currently something wrong with the patches on firmware 19.0.x, so you will need to use it on a firmware < 19.0.0 for now until I have time to fix it |
17.0.1 AMS1.6.2 Which version am I using? I tried 0.10.0 but still got an error. |
Yes, the 0.10.0 version should be the one you want for fw 17.x.x. Though i couldn't really tell you what stability improvements were made since then. You would be best running an 0.11.0+ version on 18.x.x. What's the error you're getting? |
That can happen from time to time, it's not entirely stable. If it happened while pairing the controller, there is possibly useful in formation in the log (sdmc:/mc-mitm.log). If it happened randomly you might just need to try again. |
This appears when opening the atmospheric virtual system |
Try clearing the pairing database, and make sure you're not connecting any other wireless controllers as they might be increasing the likelihood of the error |
It worked,thanks. But still unable to search for the controller.It may be an issue with the controller itself |
Share the log it created, it will show what's happening. |
Perhaps because this controller alone cannot RF out the L+R button signal, pressing L+R separately from left and right will not be considered as a paired Joycon. |
Not sure what you mean. Did you get it connected? |
It seems like something has been detected, but the switch is now stuck on this interface.... |
|
I forced it to shut down directly. Where can I find the logs |
I told you here #882 (comment) sdmc:/mc-mitm.log |
I'm not seeing any BLE events in there, just a bunch of regular inquiry packets from what looks to be a phone. Are you sure you're entering pairing mode correctly on the controller, and that it does indeed support bluetooth? |
The device BTHLE \ Dev_04338505fc0a \ 8&DB2a817&0&04338505fc0a has been configured. |
That certainly looks like an LE device from that description. This is paired to your PC? |
Yes, and the computer can only connect to one controller at a time |
Bizzarre. How are you supposed to use these controllers in practice then? I still don't really understand why they're not showing up in the log either. If they're BLE there should at least be some activity, even if the connection is ultimately unsuccessful |
Android phones can be linked normally and mapped for use through some software. The mobile phones under the controller production company also have specialized adaptation software |
Controller Name
黑鲨双翼手柄
Current Controller Behaviour
Controller is not successful in pairing with the console
Controller vendor and product ID
No response
Supported Features
Input Report Format
No response
Additional Details
No response
The text was updated successfully, but these errors were encountered: