Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,169,171
  • Replies Replies 42,894
  • Likes Likes 194
Can someone help me again? I keep getting this... It's odd. My controller kept going inactive every few hours into the game, so I had to restart it every time that happened but then it stopped once more and no longer works and I keep getting this... Anyone have any ideas why? :(

This is the error or what it says that I keep getting... It's attached below :)
photo (4).JPG





As you can see, there's no error but the HID thing just never loads, and it only lets me leave if I disconnect the controller, which is then when it says that there's an error. What's going wrong here? :(
 
Can someone help me again? I keep getting this... It's odd. My controller kept going inactive every few hours into the game, so I had to restart it every time that happened but then it stopped once more and no longer works and I keep getting this... Anyone have any ideas why? :(

This is the error or what it says that I keep getting... It's attached below :)View attachment 9721




As you can see, there's no error but the HID thing just never loads, and it only lets me leave if I disconnect the controller, which is then when it says that there's an error. What's going wrong here? :(
what controller are you using? did you try your controller on another device to see if your controller didnt die or something? since you said he kept disconnecting and now doesnt even connect.
 
Thanks again for the responce :) Um, it's just a PS3 controller, and it's the right type. It is the Dual Shock Sixaxis.

Die? Oh, you mean that the USB cable doesn't charge the controller? I dunno if it has died, as it's flashing red, sometimes but then suddenly goes on certain bits. Like, it's flashing on the Wii menu of the Wii U, Homebrew Channel, The HID test, I keep getting 'Failed to open config' error and it stops flashing and it stops flashing when trying to boot the game but there it works, it can open the config. What's going on? :(
 
Thanks again for the responce :) Um, it's just a PS3 controller, and it's the right type. It is the Dual Shock Sixaxis.

Die? Oh, you mean that the USB cable doesn't charge the controller? I dunno if it has died, as it's flashing red, sometimes but then suddenly goes on certain bits. Like, it's flashing on the Wii menu of the Wii U, Homebrew Channel, The HID test, I keep getting 'Failed to open config' error and it stops flashing and it stops flashing when trying to boot the game but there it works, it can open the config. What's going on? :(
seems like either your controller is dying or your charging cable is getting bad and loosing connection my original ps3 charging cable had this problem i had to replace it with one i had for a phone since its preety standard cable, try another cable if you have any i found out my cable had issues but it took me awhile, its a fragil cable any bent my break the connections inside giving it an unstable connection.
 
Can anyone else confirm Dragon Ball z Budokai 2 is broken with the latest version.

I'm using USB on a WiiU detects my PS4 controller but the games goes to black.
 
no idea what that means in the hid test another thing is your ini file got corrupted somehow? but i doubt it tough.



I have no idea, either... I don't think so, as I tried doing the whole process all over again and that hasn't fixed anything.


The Wii U Pro Controller charging cable didn't help one bit... or is it just not compatible?
 
I have no idea, either... I don't think so, as I tried doing the whole process all over again and that hasn't fixed anything.


The Wii U Pro Controller charging cable didn't help one bit... or is it just not compatible?
its just a cable if it fits it should work the ps3 controller does all the work the cable is just a cable, well maybe trying out to use your ps3 controller on the ps3 with the cable to see if the hid is working(noone wiressly)
 
Drome Racers (USA) [GD9E69] *NOT WORKING*
Sources: 1:1 ISO and Shrunked Image
DSP: v2
Nintendont Build: v1.143
Loader: USB Loader GX v.r1230
Memory Card Support:
Widescreen 480p Support:
Shrunk: Not Working / Shrunk Size: 819 MB
Status: Not Working
Issue: Black screen on boot
 
  • Like
Reactions: VinsCool
Thank you Howard for adding a check for Version 2.
I also think It's nintendont which should check the version sent by the loader and adapt the settings accordingly, instead of reseting the settings on version mismatch.

I updated the detection to work with argsboot too.
I removed NIN_CFG_OLD_VERSION because if you update to version 4, then version 3 would also become an old version, so the chosen setting name wasn't clear enough.
I think either using the value (ncfg->version == 2) or defining a NIN_CFG_OLD_VERSION2 is better.
I didn't add check for Version 1 (I think all loaders are updated to at least version 2 now, but users might still have an old loader).

I also allowed MaxPad == 0 with Argsboot.

I did a patch, could you check if it's good?
It's been a long time I didn't work on nintendont, I don't want to commit without asking.

patch from 143 to 144
Rename to boot.dol <-- NOT the official release available on svn. it's my own build which allow autoboot from USBLoaderGX, but it doesn't support audio streaming.


Edit:
I'm not sure the check you did is correct here:
in global.c, when checking cfg version 2 size
if(BytesRead != 540)
540 is the size of cfg v3, it implies that the loader added MemCardBlock in its cfg struct, but didn't update the version to 3.
the best way would be to check all previous v2 sizes (532 (maxPads), 536 (MaxPads+GameID), and current sizeof(NIN_CFG) if you want)

Edit:
- I there a check for already created memory card size to prevent data loss? I found it.
- Is it possible to expand an existing memory card size? it's currently using the found size only.
- Isn't ninmem.raw forced 16MB like on first nintendont versions?
 
  • Like
Reactions: ALSINJAN
I'll try with a fresh config once more, to hope that fixes it...



EDIT: Never mind, that didn't work either... Oh... What on earth could be going wrong? The controller is compatible, so what could be going wrong? Does anyone have any ideas, at all?
 

Site & Scene News

Popular threads in this forum