Talk:Wii Remote Plus (RVL-CNT-01-TR) Connection Guide

Driver signature

The drivers provided by Toshiba Stack are signed and install just fine, however, manually adding a device ID to the .inf file makes the driver become unsigned, and in 64 bit editions of Windows (including WinVista/Win7) the installation fails. Shouldn't we add steps telling how to disable driver signature check in windows 7 and older? Jhonn (talk)

You do not need to disable driver sigchecks, you merely need to install the driver(s) as an administrator. incassum (talk) 00:03, 3 February 2014 (CET)

Collapsible Section

Eh, I meant to remove the Collapsible bit and screwed up, but eh, this is ok for the short term. I'll still look into better methods later. If anyone has any ideas feel free to try them. - MaJoR (talk) 11:02, 27 October 2013 (CET)

Wiimote sounds/speaker

I've found that the wiimote speaker, using a normal, nintendo original wiimote, does not function properly when using the toshiba stack under windows 7 x64. I do admittedly not know if this is unique to the toshiba stack, but it's the only one I've used (for it's technical/functional superiority over the windows built-in stack), and ever since at the very least revision 4.0-717 (I had not tried real wiimotes prior to that revision, however, it seems that the problem is with the actual toshiba stack as opposed to Dolphin) it only gives of weird white-noises (between which can sometimes be heard the actual sound that is supposed to be heard), and in addition it also makes the rumble lag behind significantly in some games (e.g. Soul Calibur Legends). Since it has happened with every game I've tried, and to a certain extent with some wiimote testing software I've used (and several different wiimotes), I think it might be related to my choice of stack as opposed to dolphin in itself, however, I would like someone to confirm this. Anyone up for it? incassum (talk) 00:03, 3 February 2014 (CET)

This happens regardless of the bluetooth stack. In fact, the Toshiba stack greatly improves the wiimote speaker with dolphin. With the MS stack everything is even more laggy and sounds even worse. So yea, known issue. The Toshiba Stack is the best wiimote support dolphin can get on windows. - MaJoR (talk) 03:14, 3 February 2014 (CET)

Aha, ok... Isn't that something that should be on here then, as well on the page about wiimotes in general? (i.e. the problem with wiimote sounds, that they're.. Well, basically entirely broken) So as to avoid further confusion?
Also, seeing as you say "on windows", allow me to ask, as a person sticking with a couple of windows client basically just because they're easier for gaming if you play a lot of obscure and imported games (as opposed to mainly indie or triple-A releases, which are getting more and more common on at the very least Linux), is Linux/*nix in general confirmed as not having this problem? (Might be time to migrate a dedicated gaming/emulation machine to Linux if that's the case...). incassum (talk) 21:21, 3 February 2014 (CET)

Well, the problem is desktop bluetooth. No one is entirely sure the exact reasons, either latency, bandwidth, or both, but it has never really worked quite right. The toshiba stack cuts down on latency, so button presses and the wiimote pointer behave as well as they do on the wii (better even, no HDTV lag means it feels faster). But the speaker has never worked right. As for linux, from what I understand it behaves the same as the Toshiba Stack. The issue with the MS bluetooth stack is that it doesn't support all bluetooth functions: many of which the Wiimote needs. Hence it is incapable with the -TR wiimote, laggier, and much more problematic. The Toshiba Stack and the Linux bluetooth stack both support all those functions, so they behave more or less the same. So there really isn't any solution to the wiimote speaker issue. Oh, and just FYI, better to ask questions like these on the forum :P - MaJoR (talk) 00:07, 4 February 2014 (CET)