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?
Hi all!
In the last few months I've been writing
a new Bluetooth stack from scratch, with the goal of supporting more devices than just Wiimotes, and be suitable for running in the ARM Starlet processor too (for things like Nintendont and Fakemote, since I plan to support more BT controllers). It's nearly complete, and I do have an example program which transfers a file from the Wii to another device (phone or PC), just to prove that the bluetooth controller of the Wii is capable of supporting standard bluetooth scenarios.
I've now reimplemented the WPAD API from the wiiuse...
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.