Hacking Nintendont

[teogeo]

I have observed a very weird behavior with my wiiu pro controller and Nintendont.

I've done a minimal installation of the Homebrew Channel on a vWii (no extras apart from taking nand and key backups) and then I only run Nintendont. My wiimote+nunchuck worked flawlessly: synced immediately with Nintendont and all emulated buttons work in several games.

Then I tried to use my OEM wiiu pro controller, which appears to work perfectly when in Wii U mode. I did manage to sync it with Nintendont, since I see the player1 light on both in the Nintendon't menu and while in games. BUT the controls are either completely unresponsive or most of the time it appears like the up (or Z) button is constantly pressed which results in an infinite loop between the YES and NO options in the progressive scan mode option at the beginning of most GC games. Even if I skip this part by waiting, in the game menu the controller still appears to be completely unresponsive no matter which button I press (I suspect it's again stuck on some button but can't prove it). And again, the controller works perfectly in the Wii U mode. And of course, I checked if any button appears to be stuck/pressed but all of them seem to be in good shape.

What I have tried:
- Reading a lot of posts in this thread and searching online for similar cases -> no luck, most people have their pro controllers work perfectly once they manage to sync them (which is no problem for me)
- Going through the troobleshooting sections in the first post and the unofficial Nintendont site -> Nothing reported about such problems
- Tried several older versions of Nintendont: 2.153 (fist revision with BT support), 2.370 (the latest), and several others in-between (by checking when the devs made changes to the BT.c file, trying to make sure it's not a bug) --> got the exact same fanky behavior in all of them

The verdict is that something is either wrong with my controller or that there is something missing in my (quite vanilla) softmod.
My question is: Has anyone observed something similar? Is it possible that I would first need to install other stuff like IOS236 or d2x cIOS to have BT work better? Fun thing is that my wiimote+nunchuck do work...

Of course I can installing more stuff (cIOS and IOS236), but I was holding off till and if I need to play wii games to reduce the general risk of bricking.

Any help appreciated!!

 

[Howard]

I have observed a very weird behavior with my wiiu pro controller and Nintendont.

I've done a minimal installation of the Homebrew Channel on a vWii (no extras apart from taking nand and key backups) and then I only run Nintendont. My wiimote+nunchuck worked flawlessly: synced immediately with Nintendont and all emulated buttons work in several games.

Then I tried to use my OEM wiiu pro controller, which appears to work perfectly when in Wii U mode. I did manage to sync it with Nintendont, since I see the player1 light on both in the Nintendon't menu and while in games. BUT the controls are either completely unresponsive or most of the time it appears like the up (or Z) button is constantly pressed which results in an infinite loop between the YES and NO options in the progressive scan mode option at the beginning of most GC games. Even if I skip this part by waiting, in the game menu the controller still appears to be completely unresponsive no matter which button I press (I suspect it's again stuck on some button but can't prove it). And again, the controller works perfectly in the Wii U mode. And of course, I checked if any button appears to be stuck/pressed but all of them seem to be in good shape.

What I have tried:
- Reading a lot of posts in this thread and searching online for similar cases -> no luck, most people have their pro controllers work perfectly once they manage to sync them (which is no problem for me)
- Going through the troobleshooting sections in the first post and the unofficial Nintendont site -> Nothing reported about such problems
- Tried several older versions of Nintendont: 2.153 (fist revision with BT support), 2.370 (the latest), and several others in-between (by checking when the devs made changes to the BT.c file, trying to make sure it's not a bug) --> got the exact same fanky behavior in all of them

The verdict is that something is either wrong with my controller or that there is something missing in my (quite vanilla) softmod.
My question is: Has anyone observed something similar? Is it possible that I would first need to install other stuff like IOS236 or d2x cIOS to have BT work better? Fun thing is that my wiimote+nunchuck do work...

Of course I can installing more stuff (cIOS and IOS236), but I was holding off till and if I need to play wii games to reduce the general risk of bricking.

Any help appreciated!!

Did you turn off any wiimotes and disconnect any other controllers?

 

[sonictopfan]

So anyone got F-Zero AX working with 270? I wanna know what I'm doing wrong, I tried everything, deleting the save file, changing settings and values, the game runs fine in 266 though!

 

[Nemesis90]

So anyone got F-Zero AX working with 270? I wanna know what I'm doing wrong, I tried everything, deleting the save file, changing settings and values, the game runs fine in 266 though!

There are different revisions of the image online so you may have an incompatible copy of the game, it happened with me when i first tried Mario Kart Arcade GP.

 

[teogeo]

Did you turn off any wiimotes and disconnect any other controllers?

I did yes. I forced the wiimote to turn off after selecting a game in Nintendont (since I need it till that point) and the same thing I described above keeps happening. (Also, all controllers seem to disconnect when a game loads so even if I don't turn off the wiimote it disconnects by itself.)

But thanks anyway for the suggestion!

 

[AbdallahTerro]

USB only, to pair a ps3 controller you'd need to change the mac address to that of the bluetooth device / console you want to access, that's how it works with Android and Windows

www.dancingpixelstudios.com/sixaxiscontroller/tool.html
http://forums.pcsx2.net/Thread-XInput-Wrapper-for-DS3-and-Play-com-USB-Dual-DS2-Controller

the bluetooth mac address is normally -1 or +1 of your normal lan / wifi mac address

??:??:??: ??:??:01 - Bluetooth mac address.
??:??:??: ??:??:02 - LAN / Wifi mac address.

so it might only need a tiny code tweak to implement this for nintendont!

 

[CronoSage]

Does anyone know if Rumble support is broken on the Wii U (vWii mode)? I have both a Wii and a Wii U. When I tested a PS3 controller as well as a Logitech Cordless Rumblepad 2 (F710). I have proper rumble support when playing on the Wii, but on the Wii U I get nothing. And yes, I used same SD card (with Nintendont) and USB stick (with games and controllers profiles), just switched between Wii and the Wii U.

 

[Sheimi]

You dont mention what instructions you followed. based on the error the cheat path isnt being set by your loader. what loader and version version of the loader are you using? Try turning cheat path off.

Oh, sorry about that. Launching through the HBC. I am using the current nintendont loader. I did put the .gct with the game, cheats set to on and the cheats do not work.

 

[sj33]

That's actually a good idea, correct me if I'm wrong, games that support native widescreen have the option to switch it in game, it could be easy detect what games are actually using true widescreen. From the games I've tested so far, if they doesn't have in-game option for widescreen they only will strecht the image to cover black borders.

Not sure what are the parameters to submit a game as widescreen compatible in the list, but it "should" be as you say.

It's a little bit more complicated because there are games that don't natively support widescreen but do support widescreen when forced by Nintendont (albeit with a tolerable level of artifacts). The Sonic Adventure and Zelda games, for example.

Games that merely stretch the image should never be listed as widescreen compatible though, in my opinion. By definition they are not.

 

[Howard]

Oh, sorry about that. Launching through the HBC. I am using the current nintendont loader. I did put the .gct with the game, cheats set to on and the cheats do not work.

What is the full path and name of your .gct?

 

[pedro702]

I have observed a very weird behavior with my wiiu pro controller and Nintendont.

I've done a minimal installation of the Homebrew Channel on a vWii (no extras apart from taking nand and key backups) and then I only run Nintendont. My wiimote+nunchuck worked flawlessly: synced immediately with Nintendont and all emulated buttons work in several games.

Then I tried to use my OEM wiiu pro controller, which appears to work perfectly when in Wii U mode. I did manage to sync it with Nintendont, since I see the player1 light on both in the Nintendon't menu and while in games. BUT the controls are either completely unresponsive or most of the time it appears like the up (or Z) button is constantly pressed which results in an infinite loop between the YES and NO options in the progressive scan mode option at the beginning of most GC games. Even if I skip this part by waiting, in the game menu the controller still appears to be completely unresponsive no matter which button I press (I suspect it's again stuck on some button but can't prove it). And again, the controller works perfectly in the Wii U mode. And of course, I checked if any button appears to be stuck/pressed but all of them seem to be in good shape.

What I have tried:
- Reading a lot of posts in this thread and searching online for similar cases -> no luck, most people have their pro controllers work perfectly once they manage to sync them (which is no problem for me)
- Going through the troobleshooting sections in the first post and the unofficial Nintendont site -> Nothing reported about such problems
- Tried several older versions of Nintendont: 2.153 (fist revision with BT support), 2.370 (the latest), and several others in-between (by checking when the devs made changes to the BT.c file, trying to make sure it's not a bug) --> got the exact same fanky behavior in all of them

The verdict is that something is either wrong with my controller or that there is something missing in my (quite vanilla) softmod.
My question is: Has anyone observed something similar? Is it possible that I would first need to install other stuff like IOS236 or d2x cIOS to have BT work better? Fun thing is that my wiimote+nunchuck do work...

Of course I can installing more stuff (cIOS and IOS236), but I was holding off till and if I need to play wii games to reduce the general risk of bricking.

Any help appreciated!!

that happens on my fake wiiu pro controller are you sure the controller is official and not a knock off bought online? my fake one has some of these issues while my official one works flawlessly.

 

[Howard]

Does anyone know if Rumble support is broken on the Wii U (vWii mode)? I have both a Wii and a Wii U. When I tested a PS3 controller as well as a Logitech Cordless Rumblepad 2 (F710). I have proper rumble support when playing on the Wii, but on the Wii U I get nothing. And yes, I used same SD card (with Nintendont) and USB stick (with games and controllers profiles), just switched between Wii and the Wii U.

Can you share the rumble commands for the "Logitech Cordless Rumblepad 2 (F710)" with the rest of us. The conrtoller.ini on the google code page dosent include them.

 

[cashonly]

hei, eternal darkness [pal] shuts down my wii, i've tried 3 diferent iso's. im running latest nintendont and usb loader gx...

can anyone help me? what should i test, the usb stick is ok, i'm running other games from it... it is the only game that does not work? shoul i try some setting, etc? it's not the .iso

 

[pedro702]

can anyone help me? what should i test, the usb stick is ok, i'm running other games from it... it is the only game that does not work? shoul i try some setting, etc? it's not the .iso

try disabling all the settings except mcemu nad hid(incase you use hid) if you have forced progressive or widescreen or video modes or whatver taht can happen too.

 

[cashonly]

can anyone help me? what should i test, the usb stick is ok, i'm running other games from it... it is the only game that does not work? shoul i try some setting, etc? it's not the .iso

after i launch the game from usb loader, the nintendont loading screen apears, it does not return errors, but at the end of the verbose it shuts down the console.

 

[pedro702]

after i launch the game from usb loader, the nintendont loading screen apears, it does not return errors, but at the end of the verbose it shuts down the console.

like i said put everything off except mc emu and levue video in auto and try it.

 

[cashonly]

try disabling all the settings except mcemu nad hid(incase you use hid) if you have forced progressive or widescreen or video modes or whatver taht can happen too.

ok, only setting that i activated is global widescreen, i will disable that when i will arive at home.

 

[pedro702]

ok, only setting that i activated is global widescreen, i will disable that when i will arive at home.

some games dont like extra settins and eternal darkness pal might not like widescreen for all we know.

 

[zonatar]

There's a way to configure virtua striker 4?

It's start with no problem, but i want to add more time in the match

 

[Shawshank]

That does indeed fix it!

FIX94

Two games need to be added to arstartdma list

SRS: Street Racing Syndicate
Interactive Multi-Game Demo Disc Version 18

Hi Adeka,

It looks like Fix94 miss your message because it's always not working in r270 with SRS !

Do you have a special way to contact him ?