Wireless Wii Nunchuk Woes

  • Thread starter Thread starter adam_odell
  • Start date Start date
  • Views Views 606
  • Replies Replies 6
I would not bet my life on it it's 10 bucks for a reason dude,
$20 actually, all told.

M. Night Shyamalan came up in here and said WHAT A TWEEST with what I ended up figuring out.
  • I may have accidentally scammed the seller of the Blade FX
  • Thinking on it, I never used my Ali nunchuk with homebrew on Wii hardware- I was playing on Dolphin at the time
  • The Yobo chuck is working just fine in games (awesome) and isn't freezing up the Wii System Menu
  • It makes all homebrew act up horrendously because literally everything is using libogc/wiiuse and apparently this is a common problem, but I only found out about it after a lot of digging
  • 10/10 wish this information was more public (probably going to inform eBay sellers about this!)
  • What's good is when unpaired, the dongle doesn't appear to software (it's like nothing is plugged in)... what's bad is having to physically remove the receiver disconnect the Wii Remote from the Home Menu and wait some seconds to get the nunchuk to unpair, as there doesn't seem to be a way to turn it off outside of a lost connection timeout
So much winning... Wiinning?
 
Last edited by adam_odell,
I figured it out! This is your third-party attachment on libogc
How does it work with official games? Also, would you mind trying it with this version of Visual Controller Test, which is using a completely different backend?
 
  • Like
Reactions: adam_odell
How does it work with official games? Also, would you mind trying it with this version of Visual Controller Test, which is using a completely different backend?
afaik the wireless nunchuks don't work with homebrew in general due "invalid" communication. (This is also apparent with some third-party wiimotes/GameCube controllers.)

https://wiibrew.org/wiki/Wiimote/Extension_Controllers/Nunchuck#Wireless_Nunchuks

EDIT:

Might be interesting to look at.

https://wiibrew.org/wiki/Datel_Retro_Wireless_Classic_Controller
 
Last edited by master801,
  • Like
Reactions: adam_odell
How does it work with official games? Also, would you mind trying it with this version of Visual Controller Test, which is using a completely different backend?
I didn't test it thoroughly*, but it seemed to be working fine. I found an iffy video review from 2009 or so on YouTube where the guy seemed to like it a lot. I need to put it through its paces, but it's not malfunctioning with native Nintendo libs, at least.

It's definitely the invalid signals, as mentioned above. wiiuse's implementation is a pure response to official devices and this wasn't without its flaws. You could say it's similar to third-party controllers in that way- they had to recreate functionality through reverse engineering, and I can't blame manufacturers for coming to incorrect conclusions about how these devices should behave when their implementation (seemingly) works just fine with the official libraries. I'm not a dev, but I imagine wiiuse makes a lot of assumptions that are correct for official hardware and isn't as low-level as it needs to be.

I'll definitely be testing the wpad2 build of VCT today** with both nunchuks***. I have a feeling it won't work, but I'm super curious how it'll differ in behavior. If it does work, I'll be able to test ranges on these devices, so that's cool.

If it doesn't work, is there any way I can log the data streams of these devices to help you determine what's going wrong? I really feel this should be fixed and a new lib is as good a time as any to see what's going on.

*I played a few games with it tonight, and overall, I'm happy with it. Didn't notice any issues outside of the usual for third-party sticks.

**I've tested it- it locks up the GUI immediately upon pairing (in the OG build, it glitched similarly but not identically to the Blade). Restarting the Wii Remote without the Yobo gets around this and it starts working again.

***The Blade FX works in retail software, so I'm going to have to refund the guy's refund. As for VCT wpad2, it actually just glitches like the OG build (accelerometer values are probably 2x higher in both axes, though). Nearly identical to the video starting the thread. No lockups.
 
Last edited by adam_odell,
I can prepare a build of VCT where it logs the bluetooth traffic into a file on the SD card, which we could inspect here later. It should take me a few days to get it ready. If you don't hear from me in a week, please ping me -- I might have forgot :-)
 

Site & Scene News

Popular threads in this forum