Bluetooth was introduced in 153.
The problem only occurs when using USB Loading and HID. SD + HID didn't have the issue.
The problem only occurs when using USB Loading and HID. SD + HID didn't have the issue.
8 less revisions to take into consideration.Bluetooth was introduced in 153.
8 less revisions to take into consideration.
Hope you can understand my point so it could be easy for you to debug the issue.
If you want to be sure, try testing 152 and test HID in that one, then you have a good cut down portion of the total revisions.
Yeah I actually stopped using USB+HID right when the Bluetooth revision came out, so that's also why I'm pointing that out.I'll still test several before that just to make sure it didn't break earlier as the problem is only when loading games from USB + HID. The problem never occurred, at least for me, when loading the game from SD + HID.
Yeah I actually stopped using USB+HID right when the Bluetooth revision came out, so that's also why I'm pointing that out.
But that would be good just to be sure.
What happens when running nintendont and rumble should occure while the grey cable isnt plugged in?
If you feel any rumble discontinue the test asap
Yeah I actually stopped using USB+HID right when the Bluetooth revision came out, so that's also why I'm pointing that out.
But that would be good just to be sure.
After I'm done with my testing on my Wii U, maybe I'll throw in my Wii to see if there is any difference as sometimes there is a difference between how the Wii reacts and how the Wii U reacts.
One thing I did find on a consistent basis, USB 3.0 + HID never worked for me. Always resulted in Checking FS error. Once I switched to USB 2.0 device, no more FS error.
Being USB 3.0 shouldn't matter, as my USB 3.0 HDD works fine, so it could just be the luck of the draw, hard to say for sure.
I totally agree.same time I stopped using HID as well
wireless controllers all the way
but i'm switching back to HID controllers soon because i'm ordering a wavebird for my adapter
I think my HDD is also a 3.0, so I agree with the_randomizer, could be bad luck or maybe an issue with the HDD itself.After I'm done with my testing on my Wii U, maybe I'll throw in my Wii to see if there is any difference as sometimes there is a difference between how the Wii reacts and how the Wii U reacts.
One thing I did find on a consistent basis, USB 3.0 + HID never worked for me. Always resulted in Checking FS error. Once I switched to USB 2.0 device, no more FS error.
I totally agree.
I was doomed with a PS3 controller, heck I can swear I wanted to break that fucking awful controller as soon as I knew bluetooth was compatible. XD
I think my HDD is also a 3.0, so I agree with the_randomizer, could be bad luck or maybe an issue with the HDD itself.
Are you using it with HID on?
Well that sucks, I have my Wii packed right now so I can't test but I hope it gets fixed eventually, thankfully I'm keeping 219 as back up!then try without then forced its a no brainer to always try without extra stuff on before giving up and asking for help here.
yes luigi mansion ntsc broke on 226.
maybe rewriting some code will allow us to use the front ports for controllers when loading from usb?
Considering it's a USB Card reader and the USB 3.0 Card reader + SDXC 64GB + HID gave me FS error and the same SDXC card with a USB 2.0 Reader didn't. The USB 2.0 worked every time with my tests.
I only got the error when using it with HID.
for (chan = HIDPad; (chan < HID_PAD_NONE); chan = (HID_CTRL->MultiIn == 3)? ++chan : HID_PAD_NONE)
for (chan = HIDPad; (chan < HID_PAD_NONE); chan = HID_PAD_NONE)
if (HID_CTRL->MultiIn == 3) //multiple controllers connected to a single usb port all in one message
HID_Packet = (u8*)0x930050F0; //reset back to default offset
memInvalidate = (u32)HID_Packet;
asm volatile("dcbi 0,%0; sync; isync" : : "b"(memInvalidate) : "memory");
if (HID_CTRL->MultiIn == 3){ //multiple controllers connected to a single usb port all in one message
HID_Packet = (u8*)0x930050F0;
} //reset back to default offset
memInvalidate = (u32)HID_Packet;
asm volatile("dcbi 0,%0; sync; isync" : : "b"(memInvalidate) : "memory");