Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,170,476
  • Replies Replies 42,894
  • Likes Likes 194
Also, a little update for everyone who has been trying to help me. I woke up today and tried an SD card that I hadn't previously tried. I formatted it to be safe, and put 1 GameCube game on it. The game ran, and quit as it should! It went back to USB Loader GX, and I was able to select and load the game AGAIN with no freezing! I was very excited at this point, so I went back to the home menu and plugged my HDD in. I went back into USB Loader Gx and tried to launch a game that was on the HDD, it launched fine. When I quit though, it got stuck on "Initializing USB device" and eventually froze up. I unplugged my system and HDD and restarted. This time I went into the HBC and launched Nintendont through there. I was able to look at the settings and quit Ninendont without a lockup for the first time!

I'm assuming it must have been how my other 2 SD cards were formatted, and I don't think my Wii U likes my HDD either. I had an internally powered HDD that I used for my softmodded Wii, so I bought a Y cable and have been trying to use it for the vWii. Is it a better idea to just get an externally powered one for the vWii? Is there a list of "recommended HDD" for the vWii?

Again, I just wanted to update everyone, and hopefully the issue was either my HDD and SD card, or a combination of the two.

Thanks for all the responses and help I've received over the past 2 days. Hopefully this is the end of the headaches!

Hmm, maybe there's a hidden partition on the drive that's interfering? I don't see anything in your SysCheck that should be causing it.

I'm not that familiar with the Wii U but I would think it should work if it worked on your Wii. I know the Y-Cable is usually a must on the Wii U.
 
Hmm, maybe there's a hidden partition on the drive that's interfering? I don't see anything in your SysCheck that should be causing it.

I'm not that familiar with the Wii U but I would think it should work if it worked on your Wii. I know the Y-Cable is usually a must on the Wii U.

I reformatted the drive how it's supposed to be, and still had trouble. The weird thing is when its just the original SD card alone, it freezes. When it's the original HDD alone, it freezes. But this new SD card ALONE seems to be running everything just fine. I'll have to shop for a new HDD i assume.
 
Hello Everyone,

I have heard that many people have been getting "Update Error= -3" when attempting to download different files such as titles.txt, ect. I have found a solution to this problem. All you have to do is move Nintendont to a separate storage device, run it, and put it back on the original storage device. This seems to remove the error which is caused by the new FatFS module added to Nintendont in v4.408(?).
 
  • Like
Reactions: AbdallahTerro
I reformatted the drive how it's supposed to be, and still had trouble. The weird thing is when its just the original SD card alone, it freezes. When it's the original HDD alone, it freezes. But this new SD card ALONE seems to be running everything just fine. I'll have to shop for a new HDD i assume.

Give it a bit. From the post below yours it sounds like there could be an issue with Nintendont. :)
 
Hello Everyone,

I have heard that many people have been getting "Update Error= -3" when attempting to download different files such as titles.txt, ect. I have found a solution to this problem. All you have to do is move Nintendont to a separate storage device, run it, and put it back on the original storage device. This seems to remove the error which is caused by the new FatFS module added to Nintendont in v4.408(?).
-3 error was an error on nintendont update code that was fixed alot of revs ago lol i think it was fixed on 412 or something also btw we are now on 421 so your using a very outdated version already xD.
 
-3 error was an error on nintendont update code that was fixed alot of revs ago lol i think it was fixed on 412 or something also btw we are now on 421 so your using a very outdated version already xD.

We still see -3 errors even after it was fixed. It s device dependent and many times go away if we retry. The guy was testing 421
 
We still see -3 errors even after it was fixed. It s device dependent and many times go away if we retry. The guy was testing 421
he didnt posted his version and preety much everyone on github that was having this issue got it fixed when fix fixed the code so yeah if he is having a connection problem it could be his internet failling not the code since that was fixed for everyone reporting it.

-3 error also appears if your internet connection fails so it has nthing to due with the usb device.



I have been having trouble using the shutdown and reset combos on native gc controllers. is anyone else having trouble with it and/or know how to fix it?
if you have native on then no reset combos work if native is off you simply press the reset combo for the required controller, remenber gc controller trough wii gc ports and gc controller trough the wiiu gc adapter have diferent reset codes.
 
Is there a download link for MSAA mod build ?
Not yet i'm still figuring a few things out and reordering it so it makes more sense.
When progressive is off for instance i've set to force interlaced and deflicker, that and more modes like 240i/p, 288i/p, 576p, 980i, 1152i for 980i, 1152i i've set to turn progressive off.
I added a option to turn Deflicker off for interlaced resolutions for hdtv.
Next I plan on adding the following options:
Boot via BIOS
Wiimote profile: Also plan on adding a in-game prompt / message when using the combo button to show your current profile.
Vertical overscan correction: Not quite sure about this one yet I think it might just be setting the framebuffer height to fit
inside the VI window, that's how the width adjustment from 640-720 currently works?
 
he didnt posted his version and preety much everyone on github that was having this issue got it fixed when fix fixed the code so yeah if he is having a connection problem it could be his internet failling not the code since that was fixed for everyone reporting it.
-3 error also appears if your internet connection fails so it has nthing to due with the usb device.
error -3 happens when the file fails to create or extract. so It can happen not only when downloading the boot.dol but also the titles.txt or extracting the controllers.zip
Code:
if (extractZip(uf,0,1,0)) {
or
Code:
if (f_open_char(&file, filepath, FA_WRITE|FA_CREATE_ALWAYS) != FR_OK) {
if it's due to connection problems you should get error -1
Many users who got this problem after the fix in v412 solved their issues when they moved the boot dol to another device
I wrote a code in the mastermod to just get prevent this error from appearing by adding a retry function when error -3 occurs
maybe the FR_OK needs more time to init I don't know but there's for sure something there that needs to be looked at
 
Last edited by AbdallahTerro,
It reduces stair-stepping / jagged-edges to make them appear as a more believable straight line or curved edge on 3d models.
One you see 480iaa it's hard to go back to 480p even Wii games look like shit without aa,
Ferrari: The Race Experience has awful jaggies.
Is there some other requirement for the aa to show on your modded nintendont? (i download it but it doesnt show the aa stuff on the settings screen)

Here is a picture:

4ee4579bf5a80f2bd6f9bbf3330a19ad.jpg


I know that my old tv has some overscan issues (mostly vertical issues as the top portion of the screen barely shows some stuff there), that makes some games a little difficult when they have vital info there.
 
Is there some other requirement for the aa to show on your modded nintendont? (i download it but it doesnt show the aa stuff on the settings screen)

Here is a picture:

4ee4579bf5a80f2bd6f9bbf3330a19ad.jpg


I know that my old tv has some overscan issues (mostly vertical issues as the top portion of the screen barely shows some stuff there), that makes some games a little difficult when they have vital info there.

This isn't mine, I haven't put anything out yet and it'll probably be at least 2 weeks before I do anymore coding.
Taking a rest next week and seeing a physio, ive trapped a nerve in my shoulder :-( I knew something was odd
when the vien in my spine snapped / contracted back.
 
This isn't mine, I haven't put anything out yet and it'll probably be at least 2 weeks before I do anymore coding.
Taking a rest next week and seeing a physio, ive trapped a nerve in my shoulder :-( I knew something was odd
when the vien in my spine snapped / contracted back.
Ouch, that had to hurt. And yep i notice after i post [emoji28]
 
Ouch, that had to hurt. And yep i notice after i post [emoji28]
Yep I yelped in agony, I was almost on the floor, my shouldar ain't painful though it's more of an annoying
ache, still I don't want it getting any worse.
 
Not yet i'm still figuring a few things out and reordering it so it makes more sense.
When progressive is off for instance i've set to force interlaced and deflicker, that and more modes like 240i/p, 288i/p, 576p, 980i, 1152i for 980i, 1152i i've set to turn progressive off.
I added a option to turn Deflicker off for interlaced resolutions for hdtv.
Next I plan on adding the following options:
Boot via BIOS
Wiimote profile: Also plan on adding a in-game prompt / message when using the combo button to show your current profile.
Vertical overscan correction: Not quite sure about this one yet I think it might just be setting the framebuffer height to fit
inside the VI window, that's how the width adjustment from 640-720 currently works?
Pretty nice options, especially the BIOS one since that would eliminate the necessity of renaming/deleting the files, looking forward to it. Get well from your shoulder injury.
 
Not yet i'm still figuring a few things out and reordering it so it makes more sense.
When progressive is off for instance i've set to force interlaced and deflicker, that and more modes like 240i/p, 288i/p, 576p, 980i, 1152i for 980i, 1152i i've set to turn progressive off.
I added a option to turn Deflicker off for interlaced resolutions for hdtv.
Next I plan on adding the following options:
Boot via BIOS
Wiimote profile: Also plan on adding a in-game prompt / message when using the combo button to show your current profile.
Vertical overscan correction: Not quite sure about this one yet I think it might just be setting the framebuffer height to fit
inside the VI window, that's how the width adjustment from 640-720 currently works?
I'm really looking forward to these changes! :)
Will you be pushing them to the main version?
 
Hey guys, I have a suggestion for a feature for Nintendont. So you know how when using a classic/wii u pro controller you can hit the minus button in game and it will change the a,b,x and y button layouts. It would be really cool if maybe something similar could be done for the shoulder buttons where, say, if you hold minus you could swap the buttons so that instead of ZL=L,ZR=R and R=Z it could be switched to where L=L,R=R, and ZR=Z. Or perhaps instead of a button it could just be a regular option on the menu since it's more a matter of preference, unlike with the face buttons where you need to change it on the fly for baseball games.
 

Site & Scene News

Popular threads in this forum