Homebrew Starting Nintendont from Wii U menu breaks controllers

[lightwo]

I started by installing Nintendont itself and the accompanying vWii channel.

Then I installed the forwarder found under Full Guide to Play GameCube Games on Wii U.

This forwarder worked okay, and PDP Afterglow Wii U Pro Controller worked fine, however Wii U Gamepad didn't work.

Then I proceeded to install the forwarder found under Nintendont Channel on Wii U Menu 2023.

Upon using it, while Wii U Gamepad indeed worked as a controller, it broke controls of PDP Afterglow launched through all forwarders! (Nintendont still works as expected if launched through vWii directly, but that requires using the Wiimote every time.)

The broken controls manifest through wrong button assignment, some buttons not being assigned at all, and some buttons being permanently held. It is unusable.

Can you please help? I wiped everything I could think of that could be related to this, and nothing's changed.

Post automatically merged: Nov 15, 2024

I also tried the Nintendont forwarder from "Forwarder for WiiU (Aroma)" attached in Boot2vWii Channel Tutorial.

Same effect. PDP Afterglow's controls freak out when Nintendont is entered. Sadly I can't use a Wiimote as I currently don't have access to one.

 

[lightwo]

I tried to use vWii Decaffeinator light mode, and nothing has changed. This really makes it feel like vWii isn't the culprit.

 

[Gopnikh]

hey, hou did u manage to make work the WIIU gamapad? mine its only working as a screen no commands allowed

Post automatically merged: Nov 17, 2024

hey, hou did u manage to make work the WIIU gamapad? mine its only working as a screen no commands allowed

 

[lightwo]

hey, hou did u manage to make work the WIIU gamapad? mine its only working as a screen no commands allowed

Post automatically merged: Nov 17, 2024

hey, hou did u manage to make work the WIIU gamapad? mine its only working as a screen no commands allowed

I used the homebrew linked in the second video, but while I am still not completely sure if it was the culprit, I'm warning you that it might make your Pro Controller be broken in Nintendont the way it is for me.

Also, Wii VC Launch plugin may be necessary to skip the Wiimote prompts, and you probably need to install CIOSes for your vWii, as today I reset it with Decaffeinator and this no longer works for me.

 

[Gopnikh]

HEY I solved, i downloaded the version from the video like that i have 2 of them right now, possibly to solve your problem u need to dowload another version of nintendond, because i nothiced that they have different controller settings, let me know, if need let me u discord name

 

[lightwo]

HEY I solved, i downloaded the version from the video like that i have 2 of them right now, possibly to solve your problem u need to dowload another version of nintendond, because i nothiced that they have different controller settings, let me know, if need let me u discord name

Mind telling me which version of Nintendont I need to download, here in the thread? I wouldn't mind a chat, but specifying version number or linking it directly sounds like it should be just fine.

Edit: I do realise you haven't got posting privileges necessary to post URLs, but you could go to my GBATemp profile and send a PM to work around that. I don't know how strict the mods are about avoiding the URL filter, but whichever way works for you.

 

[lightwo]

Update: this also occurs with WiiFlow! The controller is all sorts of wack in the same way. Something's really broken about forwarding to vWii that doesn't seem to do anything with Nintendont itself...

 

[Gopnikh]

V6.502 (WII U) BUILT 28.7.2024 14:12:52NO WIIU CONTROLLER WITH SCREEN
V6.502 (WII VC) BUILT 28.7.2024 14:12:52 YES WIIU CONTROLLER WITH SCREEN, from the link of the video that you linked

 

[lightwo]

Well, I realised that third-party Pro Controllers don't seem to follow Nintendo's spec completely, if they've been approved at all.

So it probably makes a significant difference that the controller I'm using is PDP Afterglow Wii U Pro Controller. Still, I don't think that I had this issue the first time I set up a forwarder.

 

[lightwo]

Another update: I'm surprised I haven't verified this before, but it seems like Nintendont menu controls only work correctly if launched through HBL and not through a Wii channel forwarder (as in, from the Wii menu).

 

[leerz]

this is a known issue, the bt init isn't being loaded, this is another reason why autobooting to cfg or any loader will fUP bt functions.

 

[lightwo]

this is a known issue, the bt init isn't being loaded, this is another reason why autobooting to cfg or any loader will fUP bt functions.

That would explain it if the controller couldn't connect at all, but the controller does connect, and the controls are mapped incorrectly in the menu. Do you know where I can find more information about this?

 

[samu24love]

Sorry for my English, I'm using translator. I created this account because the same thing happened to me with a Nintendo shortcut on my Wii U gamepad. First the button assignments changed and then "Y" button kept pressed, I had to send it to be repaired because I didn't know about the subject, I thought it had been damaged by itself, because it had been less than a month since I bought it, but reading your story I have realized that what happened to me was not a coincidence. If you have more information or would like to find a solution so that it does not happen to me again, and not waste money fixing it, thank you.

 

[lightwo]

Sorry for my English, I'm using translator. I created this account because the same thing happened to me with a Nintendo shortcut on my Wii U gamepad. First the button assignments changed and then "Y" button kept pressed, I had to send it to be repaired because I didn't know about the subject, I thought it had been damaged by itself, because it had been less than a month since I bought it, but reading your story I have realized that what happened to me was not a coincidence. If you have more information or would like to find a solution so that it does not happen to me again, and not waste money fixing it, thank you.

Only solution I have so far is to have a Wii Remote ready in order to start Nintendont (or other homebrew) from within Homebrew Channel instead of using forwarders. Or, if you do use a forwarder, navigate it with a Wii Remote.

Aside from that, you can probably get away with generating WiiVC injects using UWUVCI, but I had no luck with that approach myself.

As for your hardware, it is not broken.

 

[samu24love]

Hay Is there a way to fix the control failure?

 

[Hanky97]

I’ve been troubleshooting why the Wii U Pro Controller (spesifically Afterglow Pro) fails in VC injects when synced through Wii U mode. (I'm using Aroma).

Sync Pro Controller in Wii U mode -
Launch a Nintendont VC inject =
Controller fails / inject crashes.

Sync Pro Controller in vWii mode -
Launch Nintendont from vWii or WiI U (inlcuding Injects) =
Controller works perfectly.


If I resync the Pro Controller to the Wii U at any time, it stops working in my injects and Wii U forwarders.
I also tested with several different .dol files, multiple forwarders for Wii U and vWii (including Nintrix), and every possible setting inside Nintendont, controllers folders, etc. The issue persists across all configurations.


Conclusion:

This proves the conflict probably comes from the Wii U Bluetooth stack claiming the controller during the Wii U → vWii handoff in injects. Disabling plugins didn't fix it — the issue is baked into the Wii U stack itself.

Request fix:

An Aroma plugin that blacklists Pro Controllers from Wii U Bluetooth pairing during injects, leaving vWii HID ownership intact. Or is there any other fix available?

Thanks!