Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,173,273
  • Replies Replies 42,894
  • Likes Likes 194
the adapter should work fine no one has any issues with it, if your controller has a huge deadzone then its your controller that isnt transmiting the signal to the adapter itself its not nintendont issues, also make sure your using slot 1 and not slot 4 some ppl start with the later slots lol.


you can customize your own dead zones on the controller.ini

Although the deadzones included work perfect on my end

It seems to be working OK now. I deleted Nintendon't from my SD card, redownloaded it and made sure the GC pad was on port 1. Maybe my settings were messed up or the port # really makes a difference.

Thank you both. I'll also take a look at the controller.ini to see what deadzone config I like best.
 
It seems to be working OK now. I deleted Nintendon't from my SD card, redownloaded it and made sure the GC pad was on port 1. Maybe my settings were messed up or the port # really makes a difference.

Thank you both. I'll also take a look at the controller.ini to see what deadzone config I like best.
controller.ini wont work, nintendont has internal controlers inins and only if those dont work is that it will try and find the controller.ini and the adapter has its controller internaly so it will never go to find the controller.ini
 
controller.ini wont work, nintendont has internal controlers inins and only if those dont work is that it will try and find the controller.ini and the adapter has its controller internaly so it will never go to find the controller.ini

Nintendont always checks the usb/sd for a controller.ini before it uses internal ones.
 
  • Like
Reactions: Margen67
nope its the oposite nintendont only tries to use external controller inis if it doesnt find an internal match.

That doesn't sound right at all. How are we supposed to use custom button mapping with a ps3 controller or another controller?
 
That doesn't sound right at all. How are we supposed to use custom button mapping with a ps3 controller or another controller?
you recompile nintendont :P, the way its coded its, if it finds internal then theres no reason to search external which makes sence, everyone that wants custom buttom mapping should be able to recompile aswhell.
 
That needs to be switched.

FIX94
i think its more to be noob proof, becuase alot of ppl get wrong controller inis or outdated ones and then would complain about issues, this i bet its still the case of manny users here that have old and outdated controller inis sitting on their SD/USB.
 
you recompile nintendont :P, the way its coded its, if it finds internal then theres no reason to search external which makes sence, everyone that wants custom buttom mapping should be able to recompile aswhell.
Controller mapping is not something that should require recompiling. Anyway, it appears that Nintendont WILL try to load a controller.ini before falling back to internal configs after reading this section of code: https://code.google.com/p/nintendon-t/source/browse/trunk/kernel/HID.c#229
It only tries to load DefControllers if Data == null, which should only happen if it DVID_DPID.ini, controller.ini, or controller.ini.ini do not exist, or the VID/PID don't match.
 
-sigh- I know I'm probably going to sound like a dick to some people, but we just had the OP updated and people are asking for help without using the troubleshooting form. Can you guys not answer any questions unless they do? I hate seeing situations like with what happened with kiantsu above. Thanks!
 
  • Like
Reactions: tswntk
-sigh- I know I'm probably going to sound like a dick to some people, but we just had the OP updated and people are asking for help without using the troubleshooting form. Can you guys not answer any questions unless they do? I hate seeing situations like with what happened with kiantsu above. Thanks!

agree, except that the form should be applied to more general situations rather than inside "Game Compatibility" in the OP.
May be in "Troubleshooting" and a direct link to the form in "Tutorial Index" and inside "Game Compatibility list" as well.

At the same time don't expect helpers to memorize all the details from the OP apart from those obvious before deciding to offer help to noobs who didn't read the OP. There would always be gray areas.
 
Well, used modmii today, now i Have the Dark Blue theme on sysmenu. Nice!
But usbloadergx still won't mount my usb drive, and using nintendont via wiiflow still only loads nintendont, so I have to choose the game again. Not a real problem, cause I have nintendont as a channel and it works fine ( Now with some cool backgrounds - Thanx Mr. Mysterio and send0r! ), but would be nice to see the covers and stuff.
Any tip?
 
agree, except that the form should be applied to more general situations rather than inside "Game Compatibility" in the OP.
May be in "Troubleshooting" and a direct link to the form in "Tutorial Index" and inside "Game Compatibility list" as well.

At the same time don't expect helpers to memorize all the details from the OP apart from those obvious before deciding to offer help to noobs who didn't read the OP. There would always be gray areas.

It's funny you suggested that because not long after I made the post I requested that Cyan do just that in a PM. Lol
I don't expect helpers to memorize it. They should be able to easily recognize a form, don't you think? You can just copy and paste the form and fill it in. It's really just that simple.
 
It's funny you suggested that because not long after I made the post I requested that Cyan do just that in a PM. Lol
I don't expect helpers to memorize it. They should be able to easily recognize a form, don't you think? You can just copy and paste the form and fill it in. It's really just that simple.

A few months ago, myself and few other members created such a form for people to follow but sadly not many people used it. It contained basic info like console you were using and region, video cables, Nintendont version, game name and region, controller being used, how the game is being loaded, Memory Card type, storage media being use, etc. I was getting tired of people just saying that game X didn't work without giving ANY other info as even the smallest thing could affect game compatibility. I remember how some games would work on Wii but not Wii U and the time when WiiConnect24 caused game freezing.
 
It's funny you suggested that because not long after I made the post I requested that Cyan do just that in a PM. Lol
I don't expect helpers to memorize it. They should be able to easily recognize a form, don't you think? You can just copy and paste the form and fill it in. It's really just that simple.


I mean there is always gray areas where we will help noobs w/o referring them to read the OP even if the details may already be in the OP.
I would not copy and paste the form as I can always refer users to read the OP
 
Here is a little tool that can convert *.gci savegames to *.raw format for Dolphin and Nintendont:
http://www.emutalk.net/threads/38901-New-Dolphin-Memory-Card-Maker

Would fit to savegames section in first post.

I tried that a while ago. It worked pretty well, but it mangled some saves. It also only does GCI and GCS saves. I think it would be a nice addition to the first page, but maybe it should say something like this:

Converting Saves into RAW Memory Cards for Nintendont:

Easier for N00bs-> Simple GCI or GCS to RAW converter.
More Reliable->How to Convert GCI, GCS, or SAV saves to RAW
My tutorial uses the memory card manager that's built-in to Dolphin. I've found it to be the most reliable GameCube save manager in existence!
 

Site & Scene News

Popular threads in this forum