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
Pro Controller Grip Colors saving but not showing correctly on switch. #28
Comments
It appears that by default the pro controller will have different Grips and Body colors. However, once a color has been applied to the body, it will be applied to the grips as well. |
That's because the algorithm that decides what colors it will use in Switch, changed. For now I don't have time to update the toolkit :/ |
@TJBaurle I had the same issue and I solved it by flashing the original (stock) fw from backup, changing the grip colors only and flash, then change body color and flash. |
I just got bit by this as well. Joy Con Toolkit: v5.2 All of the controllers I have are stock pro controllers, and normally have a black shell (#323232) with white buttons (#ffffff) in software. I can't change the grip colors if the shell body is default (#323232). While I think Toolkit v5.2 is trying to guard against changing the grip colors in this case, it feels more like a hap-hazard bug because changing the body color to a non default value allows me to continue, but as you'll see... if I try, it simply doesn't work. I set the body color to #2D2D2D which allows me to set grip colors... and the controller appears to accept the new values. After writing the colors, the switch software seems to ignore everything except the body + buttons color, with the grip colors inheriting the body's color I'm unsure if it's simply not possible anymore, or if the tool needs an update. I'd love to hear more on this, even if it's just a #wontfix. |
I have the same issue with the pro controller. And may I ask when you plan to update the Joycon Toolkit? Just checking, no rush. :) |
Hi, I have the same problem. I set the body color to white and the grip to black but when I connect the controller to the Switch it shows all white except for the buttons. Glad to know I'm not the only one! Is there going to be a fix for this anytime? |
I managed to switch my grip colors on a smash controller to FFFFFFF on the right and 464646 on the left. When I try this with a normal Pro Con, it fails. So maybe its a switch firmware thing? |
Hello I have an issue with a pro controller bought used. it has connectivity issues, it doesn't stay connect more than like 2 minutes. |
See files in link. These are original spi files for my pro controllers. |
Same issue now. Cannot display correct color on switch. |
Hi everyone, I believe I have found the solution for stock colors. |
Good to hear that. Thank you very much, will check this evening~ |
I can confirm this works, just make sure to set the button color to FFFFFF. |
So I was messing with the HID stuff today and managed to get custom grip colors to show up on an actual Switch. The SPI data at x601B needs to be set to 2 if there are grip colors defined. So 0 = no custom colors, 1 = custom body/button colors, and 2 = custom everything. Once you set the byte to 2, everything appears as it should on the console. Can someone tell me what the stock values are for a Smash Bros Pro Controller? Is it similar to Splatoon and Xenoblade where there is a magic body color that tells Switch what grip colors to show? |
That is so awesome. I'll try it out tonight and report back. Good job!
…On Thu, Jan 9, 2020, 7:50 AM jmickelonis ***@***.***> wrote:
So I was messing with the HID stuff today and managed to get custom grip
colors to show up on an actual Switch.
The SPI data at x601B needs to be set to 2 if there are grip colors
defined. So 0 = no custom colors, 1 = custom body/button colors, and 2 =
custom everything. Once you set the byte to 2, everything appears as it
should on the console.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28?email_source=notifications&email_token=AAYLEIPNMFOLY4OF6MGHJY3Q44TQPA5CNFSM4GKC2USKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIQLQ4I#issuecomment-572569713>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYLEIOHMD7KCTARSQR3FN3Q44TQPANCNFSM4GKC2USA>
.
|
Can anyone make a simple tutorial for this? Im kind of a noob and I´m afraid to mess stuff up |
Oh sorry, I should've explained how to do it through the Toolkit. First, set your colors like you normally would. Then, go to the section where it says "Debug: Custom Command". Set the following: Hit "Send" and you should be good to go. You should get a Subcmd Reply starting with 80 11. |
It wont let me set Subcmd to 11 for some reason, when i hit send I get "No reply." |
Odd... that info should be correct. I'll try it later when I hop back on Windows 10. |
Odd. You're definitely connected? It looks like it should be working... I see your firmware version/MAC isn't showing up properly. That could be a clue to what's going on. |
In the "debug_scripts" folder there are two .bat files. Make a copy of one of them, open it up in notepad, change the last line to "jctool_v5.2.0 -e". That's what I did and it worked for me. EDIT: Turns out I assumed something unrelated worked. What I really did that worked was typing "11" into the subcommand, opening up the HD Rumble Player, then going back to the debug menu and it doesn't block you from sending anymore, even though the error still shows. |
Thanks a lot!! this totally helped!! |
Thank you, @jmickelonis and @MarkAdmani! |
I hope this gets picked back up soon. This is a cool tool that many would love. |
@nusco @gavinhsmith I've forked the repository here. Feel free to check it out. The whole tool has not been ported over yet, but I've got the IR sensor, HD Rumble player, and the controller colors to work (and be recognizable on the switch.) As of right now, the issue mentioned in the thread should still persist as I've yet to work on fixing it since I've been busy working on doing some major refactoring of the code (hopping back and forth between different portions.) Here is a screenshot: The colors loaded on the SPI are recognized when you click "Try Connection Attempt." As for the original project, I've submitted a pull request, but I haven't received feedback on it yet. For now I'll just assume the project is dead as there has not been a single commit to the master for almost 2 years now. Since there is no decent API out there in the wild that I've come across, the fork won't be dead as I have some cool concepts on what the joycon itself could be used for. |
https://switchbrew.org/wiki/Joy-Con The evee joycon colors are from there |
Did you find it yet?I can not find the Smash color number 😭 |
can confirm this still works on switch 12.1.0 |
Try 2D2D2D |
Any fixes gonna eventually come for this? I'm just curious. Would love to see it happen. |
if anyone finds the new colors for the Splatoon 3 Cons and Pro controller that'd be nice |
Please Please Please Please tell me Splatoon3 Pro controller code such as Splatoon2 313232 |
For Splatoon 3 pro controller, try For Splatoon 3 joy-cons, try Joy-con (R) I copied the codes from the real Splatoon 3 pro controller and joy-cons. |
After reading through and testing, here are all the steps in order for this error to be fixed guaranteed.
|
The colors of the grips on my pro controllers are saving properly, but when displayed on the switch they are the same color as the body. Is this specific to the FW version of the controller? The switch is on the latest release 6.2.0. Also the S/N is showing as "Not Supported".
The text was updated successfully, but these errors were encountered: