What’s the code to turn home LED on indefinitely with this program or is it an option in the latest release
Epilepsy!
Btw, the milliseconds in the documentation were approximately measured through my smartphone's camera. 120fps video. It did me a great favor.
Try my command also
You need to send it as a command via the debug menu. If you get it turned on, you can re-pair it with the Switch and it'll stay on until you put the console in sleep mode.What’s the code to turn home LED on indefinitely with this program or is it an option in the latest release
I have it blinking, that’s unfortunate I would love it on every time I wake it up on the switchYou need to send it as a command via the debug menu. If you get it turned on, you can re-pair it with the Switch and it'll stay on until you put the console in sleep mode.
That would mean third party controllers wouldn’t work if they did thatColor me paranoid, but surely the system could be updated to respond negatively in some way (use your imagination) if you're using values that don't match any of the officially released ones, right? I mean, this is Nintendo we're talking about.
The same one that keeps trying to fix all the problems with the 3ds for years?Color me paranoid, but surely the system could be updated to respond negatively in some way (use your imagination) if you're using values that don't match any of the officially released ones, right? I mean, this is Nintendo we're talking about.
I admit I'm not really sure what info you're going by to draw that conclusion. How exactly do third party controllers identify themselves to the Switch? The one I have, an 8Bitdo SNES pad, appears to the system as a Switch Pro Controller.That would mean third party controllers wouldn’t work if they did that
That's a straw man argument. The kind of update I'm describing should be child's play to implement.The same one that keeps trying to fix all the problems with the 3ds for years?
But it would be a pain for nintendo, because if they limit the colors in the firmware, then they would need to make a new update for each new joy con color they makeI admit I'm not really sure what info you're going by to draw that conclusion. How exactly do third party controllers identify themselves to the Switch? The one I have, an 8Bitdo SNES pad, appears to the system as a Switch Pro Controller.
That's a straw man argument. The kind of update I'm describing should be child's play to implement.
They're already generating that every time. It would be a simple matter to automatically add new values to a whitelist and require that you update the Switch any time it sees a color scheme not found on said list—effectively rendering any custom color sets useless.But it would be a pain for nintendo, because if they limit the colors in the firmware, then they would need to make a new update for each new joy con color they make
That's the problem, they would have to keep pushing out updates for each new joy con they make. What about the people who don't update? What happens if they put one of the new colored joy cons in their switch?They're already generating that every time. It would be a simple matter to automatically add new values to a whitelist and require that you update the Switch any time it sees a color scheme not found on said list—effectively rendering any custom color sets useless.
I'm guessing the same thing that happens if you want to use the updated DualShock 4 controllers or Move controllers with a PS4 that's still running the original system version. {shrug}That's the problem, they would have to keep pushing out updates for each new joy con they make. What about the people who don't update? What happens if they put one of the new colored joy cons in their switch?
It won't detect my left joycon. At all.
Here's how everything goes:
The right joycon pairs fine, and the bar that shows pairing progress in Windows goes all the way to the end before saying it's connected. I then open Joycon Toolkit and it detects it fine. Everything goes smoothly.
Then I connect the left joycon, and the bar that shows pairing progress just stays at the very beginning for like 2 seconds before saying it's connected. I then open Joycon Toolkit and it doesn't detect it.
I've been trying to change my left joycon's colours for like, half an hour now. What is this fucking bullshit.
I think the 3rd party controllers dont have chips in them to write a colour to, and so the switch would probably read the colour as NULL, in theory this would not be on the colour list therefore making it not work, whereas right now that just sets it to standard coloursI admit I'm not really sure what info you're going by to draw that conclusion. How exactly do third party controllers identify themselves to the Switch? The one I have, an 8Bitdo SNES pad, appears to the system as a Switch Pro Controller.
That's a straw man argument. The kind of update I'm describing should be child's play to implement.
I found the Easter egg by the way, fucking glorious HahahahaWhat's the point of that?
You can only capture the normal HID communication, which can already be done pretty easily and it's useless.
On PC, either you use USBCap on your USB BT adapter or make an up with infinite loop on hid_read and write the packets to a logfile.
Instead of USBCap, there are bt sniffers for Android or you can use hidapi.
The only useful sniffing is between Switch and the controller. For this you need ubertooth and then you need to decrypt the BT LE packets.
But it's easier to find a USB sniffer and put it between the dock and a Pro controller.