Gamecube/Wii support & news forums
http://www.gc-forever.com/forums/
what contradiction??BenoitRen wrote:In other words, you're saying that the data that the Balance Board transmits is more than a Wiimote + Nunchuk, right? Because otherwise it doesn't follow. I asked why it's counted as an expansion device and you answer that it's simulating a Wiimote with an expansion device. See the contradiction?
http://tinyurl.com/o96gkenmegalomaniac wrote:what contradiction??BenoitRen wrote:See the contradiction?
Expansion device != Wiimote + expansion devicemegalomaniac wrote:what contradiction??
What relevance does the additional port on the motion plus have? If you want to access the motion plus data, it must be done via the expansion port regardless of whether the motion plus is built in or externally attached. So it's always an expansion device even when it's part of the wiimote.BenoitRen wrote:I don't see the correlation. The Wii MotionPlus is a different thing as it has an expansion port of its own.
You said yourself that the Balance Board simulates a Wiimote with an expansion device. Hence it's not an expansion device, as it's stand-alone.
If there is a HBC update then the new version will be "wiiu pro enabled" but no idea when that will happen. Making it work globally is too difficult as I explained earlier.I have tested Devolution with the Wii U Pro Controller and it's actually amazing. First I was confused when I realized the buttons were not mapped to match the names of the gc controller buttons (Y is B and B is A etc), but I got used to it very quickly. The only thing that I dislike is that if I exit to the HBC to select another game I can't use it anymore. It would be really cool to have drivers that enable the Wii U Pro Controller globally. I don't think Nintendo will ever update the Wii again so I think those drivers would be save. Please make this happen, tueidj! I don't think anyone else other than you can make this happen
I see what you mean now. In my eyes, though, it's only really an expansion device if it's connected to an actual Wiimote.tueidj wrote:What relevance does the additional port on the motion plus have? If you want to access the motion plus data, it must be done via the expansion port regardless of whether the motion plus is built in or externally attached. So it's always an expansion device even when it's part of the wiimote.
The balance board is like a giant wiimote with no accelerometers or camera, one single button and four weight sensors connected to the expansion port. If a device uses the wiimote's expansion port for communication, surely it is an expansion device?
Whats the maximum number of steps a GCN game actually uses during gameplay?tueidj wrote:The classic controller pro functions the same as the original classic controller except it doesn't have analog L and R triggers.
Both of them have the same terrible stick sensitivity - the L stick ranges from 0 to 63 and the R stick ranges from 0 to 31 (and they are never calibrated properly). In contrast, the gamecube sticks and PS1/2/3 controllers all range from 0 to 255 and the wiiu pro sticks range from 0 to 4095.
I personally think sensitivity is the wrong term to use for this, that would imply that you aren't getting the full "distance" of the analog stick. What is being described is much more like "resolution".inspectah_deck wrote:And is the difference in stick sensitivity (between GCN and CC controller) even noticable during gameplay?
Thats a bummer, making these GCN to CC adapter not the perfect solution for original controls either.tueidj wrote:Try zooming in with the sniper rifle in TimeSplitters 2, the controller isn't sensitive enough to target accurately.
So would you be interested in adding such support in Devolution tueidj?Q: Does the current revision (of GCN to CC adapter) support the full range of the Gamecube sticks (0-255) or only the limited one of the CC (0-63 and 0-31)?
A: Only the limited one. Doing better would require implementing a special mode
in my adapter and having the Devolution developer support it. This special
mode would also be useful to some homebrew apps.. For now I'll add this
on my list for future features.
Oh I missed that. That explains the higher sensitivity of the Wii U Pro Analog sticks I experienced with F-Zero then. Can the sensitivity of the Wii U Pro analog sticks be changed via software to 0-255?inspectah_deck wrote:Look here:
viewtopic.php?p=19233#p19233
I don't think he has to implement a special mode. The classic controller uses 6 bytes for reporting data which the wiimote reads from offset 8 of the extension memory, but depending on the reporting mode the wiimote can return up to 8, 19, 16, 9, or 21 bytes. So all he has to do is make his adapter put the real stick/trigger values after the normal 6 bytes of CC data and I can read them using the 19 byte reporting mode (which I always use anyway because it's needed for the WiiU Pro). Also put a couple of signature bytes on the end to distinguish it from a real classic controller.inspectah_deck wrote:I also asked him about the different ranges of the CC and GCN controller, here is what he answered:So would you be interested in adding such support in Devolution tueidj?Q: Does the current revision (of GCN to CC adapter) support the full range of the Gamecube sticks (0-255) or only the limited one of the CC (0-63 and 0-31)?
A: Only the limited one. Doing better would require implementing a special mode
in my adapter and having the Devolution developer support it. This special
mode would also be useful to some homebrew apps.. For now I'll add this
on my list for future features.
Heh, then it was my imagination afterall. Thanks for clearing this uptueidj wrote:The values from the WiiU Pro are already converted to the 0-255 range, they have to be in order to emulate a GC controller.
Hello tueidj,tueidj wrote:I don't think he has to implement a special mode. The classic controller uses 6 bytes for reporting data which the wiimote reads from offset 8 of the extension memory, but depending on the reporting mode the wiimote can return up to 8, 19, 16, 9, or 21 bytes. So all he has to do is make his adapter put the real stick/trigger values after the normal 6 bytes of CC data and I can read them using the 19 byte reporting mode (which I always use anyway because it's needed for the WiiU Pro). Also put a couple of signature bytes on the end to distinguish it from a real classic controller.inspectah_deck wrote:I also asked him about the different ranges of the CC and GCN controller, here is what he answered:So would you be interested in adding such support in Devolution tueidj?Q: Does the current revision (of GCN to CC adapter) support the full range of the Gamecube sticks (0-255) or only the limited one of the CC (0-63 and 0-31)?
A: Only the limited one. Doing better would require implementing a special mode
in my adapter and having the Devolution developer support it. This special
mode would also be useful to some homebrew apps.. For now I'll add this
on my list for future features.
Code: Select all
/* | Bit |
* Byte | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
* ------+---------------+-------+----------------------------+
* 0 | RX<4:3> | LX<5:0> |
* 1 | RX<2:1> | LY<5:0> |
* 2 | RX<0> | LT<4:3> | RY<4:0> |
* 3 | LT<2:0> | RT<4:0> |
* 4 | BDR | BDD | BLT | B- | BH | B+ | BRT | 1 |
* 5 | BZL | BB | BY | BA | BX | BZR | BDL | BDU |
* 6 | GC Left stick/N64 stick raw X value |
* 7 | GC Left stick/N64 stick raw Y value |
* 8 | GC C-stick raw X value |
* 9 | GC C-stick raw Y value |
* 10 | GC Left shoulder raw X value |
* 11 | GC Right shoulder raw Y value |
* 12 | 0x52 ('R') |
* 13 | 0x4E ('N') |
* 14 | 0x54 ('T')
*/
