Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,174,290
  • Replies Replies 42,894
  • Likes Likes 194
Well, there are very few actual Wii/WiiU/WiiWare/VC games that use analog buttons in any way. Also, a pure on/off button should arguably provide faster, more reliable control than a mushy analog button--hence "pro". If they actually meant for the controller to be used with GC games, then it would be a poor decision. As it is, it seems to do fine. [/devilsadvocate]
I agree with a digital on/off button but I meant more along the lines of shoulder buttons like every other console has, including GC & the original classic controller which I own. Thank God for that cuz again the "Pro" line of controllers are simply not adequate for even next gen gaming, many games require analog input for precision control.
 
I agree with a digital on/off button but I meant more along the lines of shoulder buttons like every other console has, including GC & the original classic controller which I own. Thank God for that cuz again the "Pro" line of controllers are simply not adequate for even next gen gaming, many games require analog input for precision control.
I meant that the digital shoulder buttons are either off, or they're on. I really can't think of many next/current generation games that require analog shoulder buttons, and the pro controller wasn't meant to be used with GameCube games. They would make it easier to port GC games to Wii U for sure, but in that case it should also have six face buttons to support N64/Xbox/Saturn games, etc.
 
Guys does it matter which file must be renamed to controller.ini? I'm connecting an USB gamepad similiar to ps2's gamepad that seems isn't recognized, because the analog button won't turn on the red light. Of course the .ini file can't be "controller_ps2.ini" ... But the other possible choice is F510.. Is "controller_F510.ini" the file which i have to rename to controller.ini?

Anyway, i suppose kernel errors are caused by files mismatch! I'm going to delete all files in SD root, except controller.ini (=controller_F510.ini, which should better fit my HID device) , and try to load Wind Waker again and let you know!
 
Guys does it matter which file must be renamed to controller.ini? I'm connecting an USB gamepad similiar to ps2's gamepad that seems isn't recognized, because the analog button won't turn on the red light. Of course the .ini file can't be "controller_ps2.ini" ... But the other possible choice is F510.. Is "controller_F510.ini" the file which i have to rename to controller.ini?

Anyway, i suppose kernel errors are caused by files mismatch! I'm going to delete all files in SD root, except controller.ini (=controller_F510.ini, which should better fit my HID device) , and try to load Wind Waker again and let you know!

chances are that the F510 config will not work as your controller is not a F510 pad
you need to look here and make a config file for your type of pad
 
I have an adapter PS2-to-USB, i think i'm going use that with controller_ps2.ini. But first i have to solve kernel -1 error =/
 
For those with the -1 error, make sure your HBC and your IOS58 are up to date and that you're running it through HBC with the meta.xml file in the same folder
same here..
I can't pass -1kernel error... wii 4.3e boot2 as ios,
maxternal u know holliwood line on syscheck is about wii and wiiu?
i remember crediar say; nintendon't need two diff version 1 for wii and other for wiiU ...
 
i remember crediar say; nintendon't need two diff version 1 for wii and other for wiiU ...
Crediar seems to have fixed the problem with needing two versions ... BUT the cause of the -1 problem is still a bit of a mystery

It DOES take a while for it to get past the "loading kernel -1" screen, though. How long is everyone waiting for it to get past that point?
 
Crediar seems to have fixed the problem with needing two versions ... BUT the cause of the -1 problem is still a bit of a mystery

It DOES take a while for it to get past the "loading kernel -1" screen, though. How long is everyone waiting for it to get past that point?

i have exactly the same problem with -1 kernel error. i only see this error with yuv cable on a green screen, with default cable the screen just turns off. u can see my wii here: http://syscheck.wii-homebrew.com/#!N2U1NWVmYjA4YmM4 with all needed details.

here a screen how the error looks like: https://www.dropbox.com/s/2sm1byz083d9pi0/20130921_152714.jpg
 
Same here, not even a second then no signal display.. Maybe do we need to install a specific cIOS? :blink: On which one is Dios Mios Lite based on?
 
Same here, not even a second then no signal display.. Maybe do we need to install a specific cIOS? :blink: On which one is Dios Mios Lite based on?
Nintendont doesn't use cIOS, it's using official IOS 58 version 24.32 (or 25.32 on WiiU).
If you are not using the correct IOS 58 version, you are prompted with a nice message when launching nintendont, so if you see nintendont menu and text in the top-left corner it means you have the proper IOS version.


i remember crediar say; nintendon't need two diff version 1 for wii and other for wiiU ...
instead it will be two versions : one for SD and one for USB, like with DM/DML.
 
This is as far as user missionfloyd got. Would be nice to know if a wired GC controller is more stable on the raphnet adapter to write a proper ".ini", then see if switching it out for a Wavebird would work.
...I guess I'll PM missionfloyd.
Okay, I got my hands on a wired controller. It didn't make a difference, I have no idea why. This adapter works perfectly with everything else.

Perhaps a newer firmware works better (mine is 2.1, latest is 2.3) but it's not user-upgradeable, at least not without an AVRISP. You would have to ask Raphael to test it ([email protected]) Maybe he'll have some insight into what's going on.
 
Are any at least semi-wireless controllers compatible (usb HID receiver for some other controller)? Preferably bluetooth based.
 
Are any at least semi-wireless controllers compatible (usb HID receiver for some other controller)? Preferably bluetooth based.
There are things like a Wii U Pro to USB adapter that probably would work
http://www.mayflash.com/Products/NINTENDOWiiU/W009.html
Or you could use some GameCube to USB adapter and plug a Wireless GameCube controller into it (like a wavebird)
http://www.mayflash.com/Products/NINTENDOWiiGC/PC051.html
There are also wireless USB gamepads that are NOT Bluetooth. This is what Google gave me:
http://compactiongames.about.com/od/hardware/tp/gamepads.htm
(the first one that says it needs a USB port for the receiver)
 
  • Like
Reactions: DaveBlack
There are things like a Wii U Pro to USB adapter that probably would work
http://www.mayflash.com/Products/NINTENDOWiiU/W009.html
Or you could use some GameCube to USB adapter and plug a Wireless GameCube controller into it (like a wavebird)
http://www.mayflash.com/Products/NINTENDOWiiGC/PC051.html
There are also wireless USB gamepads that are NOT Bluetooth. This is what Google gave me:
http://compactiongames.about.com/od/hardware/tp/gamepads.htm
(the first one that says it needs a USB port for the receiver)
What I want is something like the first one but for a normal wiimote+cc (not pro) for the analog triggers. Or I could wait and see if external input modules are ever supported or if right stick analog trigger toggle is added like with devo.
 
What I want is something like the first one but for a normal wiimote+cc (not pro) for the analog triggers. Or I could wait and see if external input modules are ever supported or if right stick analog trigger toggle is added like with devo.

the mayflash adapter works for both cc, ccpro, and even a nunchuck if you are bored. i know because i have one myself
 
  • Like
Reactions: Maxternal

Site & Scene News

Popular threads in this forum