Hacking Nintendont

  • Thread starter Thread starter sabykos
  • Start date Start date
  • Views Views 10,168,129
  • Replies Replies 42,894
  • Likes Likes 194
well is a shame collosseum doesnt have mcemulation

XD freezes with a beeping sound after the first cutscene but vs mode and mcemu works perfectly shame about the freeze tough.

XD is working after the cutscene.
I loaded a save file I had and the game seemed to play fine, although when I tried to enter a machine for inventory stuff, it froze.
 
XD is working after the cutscene.
I loaded a save file I had and the game seemed to play fine, although when I tried to enter a machine for inventory stuff, it froze.
i assumed the cutscene was the freeze and the game isself should work i guess i must miss a fix or so to pass the cutscene.
 
i assumed the cutscene was the freeze and the game isself should work i guess i must miss a fix or so to pass the cutscene.

No no, sorry.
I meant to say, it DOES freeze in the cutscene for me too.
But if you load a save file past that cutscene, it works.
I don't know of it freezes for other cutscenes though.
 
REV: 115
SIXAXIS
USB

Could someone shed some light into why my SIXAXIS pad is not working? This is the first time I have tested Nintendont since the Alpha that only played wind waker. The pad worked fine then.

I'm launching nintendont from USB and have https://github.com/Nanolx/nintendont-controller/blob/master/nintendont_ps3.ini Renamed to controller.ini in the root on my USB drive.

Pad is connected to the bottom rear USB port, flash drive is on the top rear port.

The pad works fine in HIDtest

Have enabled HIDdevice in settings.

Always get the error that "HID:Config does not match device"
Followed by an instant restart.


I have tried deleting nincfg.bin and starting again, still no joy.

Don't know if it helps, but this is the contents of nloader.log

Code:
Kernel:"/shared1/00000031.app"
KernelSize:168512
LoaderSize:00000594
PHeaders:15
PHOffset:52
Type:1 Offset:0000
 
Bug report 1.101-1.117

GSNE8P
Sonic Adventure 2 Battle

Freezes before Sonic and Shadow transform to fight the end boss.
 
my left stick moves down, on r116 works fine

Remember that the sticks should be left at their "Home" position.
If you move them while Nintendon't is loading, you will have problems like the character moving to one direction only even if you are not moving the sticks.
 
  • Like
Reactions: 1 person
I want to know what is the main difference for Cheats, Cheats Path, Use HID and USB.
USB and Cheats Path are the ones that interest me the most
NIN_CFG_CHEAT = Tells nintendont to enable cheat codes/game patches.
NIN_CFG_CHEAT_PATH = Tells nintendont to use the path in the nincfg.bin instead of looking in /games/gameID/, so when you generate nincfg.bin you can put any path to CheatPath[255];.
NIN_CFG_HID = Tells nintendont to use USB controllers instead of Gamecube controller. it's enabled by default on WiiU. it can be used in mixed mode on Wii (2 GC controller + 1 HID controller for multiplayer games for example).
NIN_CFG_USB = Tells nintendont to use USB kernel, instead of SD kernel. Enable this setting if the ISO is on USB, Disable it if the ISO is on SD card.
 
NIN_CFG_CHEAT = Tells nintendont to enable cheat codes/game patches.
NIN_CFG_CHEAT_PATH = Tells nintendont to use the path in the nincfg.bin instead of looking in /games/gameID/, so when you generate nincfg.bin you can put any path to CheatPath[255];.
NIN_CFG_HID = Tells nintendont to use USB controllers instead of Gamecube controller. it's enabled by default on WiiU. it can be used in mixed mode on Wii (2 GC controller + 1 HID controller for multiplayer games for example).
NIN_CFG_USB = Tells nintendont to use USB kernel, instead of SD kernel. Enable this setting if the ISO is on USB, Disable it if the ISO is on SD card.

Thank you, Cyan, for the response!
One thing is still not clear to me:
CheatPath[255], we can change the path of the cheat codes by changing it in the source code and then compiling it?
Or can we change the path manually in some file inside nincfg.bin?
 
Can somebody confirm that Mario Party 7 (PAL) has black on boot? It seems I'm the only one who's testing this game and editing the compat list for it. For me this games has black screen since v1.72, but since the NTSC version is working on v1.101 (according to the compat list), I have to consider that the problem is on my end. Would be nice, if somebody could test this.
 
CheatPath[255], we can change the path of the cheat codes by changing it in the source code and then compiling it?
Or can we change the path manually in some file inside nincfg.bin?
You don't change the path in the source code.
When you use an external loader (GX, Wiiflow, postloader), the loader generate the nincfg.bin files which contains all the settings, and then launches nintendont.
Nintendont use this file's content as base for its own settings.

When the loader generate the nincfg.bin file, it can store two different path in it : the ISO path and the Cheat path.
it means that the loader can point to whatever path and file you want, the game don't need to be in /games/, the cheats don't need to be in /games/GameID/ etc.
USBLoaderGX are storing cheat codes in sd:/codes/, so when you launch a game with USBGX it write the cheat path in nincfg.bin and tells nintendont to use the given path instead of the default one.

nincfg.bin format is as follow:
Code:
typedef struct NIN_CFG 
{
	u32		Magicbytes;		// 0x01070CF6
	u32		Version;		// 0x00000002 since r42
	u32		Config;
	u32		VideoMode;
	u32		Language;
	char		GamePath[255];
	char		CheatPath[255];
	u32		MaxPads;
	u32		GameID;
} NIN_CFG;

the unsigned int "Config" is the one which stores the settings:
Code:
enum ninconfig
{
	NIN_CFG_CHEATS		= (1<<0),
	NIN_CFG_DEBUGGER	= (1<<1),
	NIN_CFG_DEBUGWAIT	= (1<<2),
	NIN_CFG_MEMCARDEMU	= (1<<3),
	NIN_CFG_CHEAT_PATH	= (1<<4),
	NIN_CFG_FORCE_WIDE	= (1<<5),
	NIN_CFG_FORCE_PROG	= (1<<6),
	NIN_CFG_AUTO_BOOT	= (1<<7),
	NIN_CFG_HID		= (1<<8),
	NIN_CFG_OSREPORT	= (1<<9),
	NIN_CFG_USB		= (1<<10),
	NIN_CFG_LED		= (1<<11),
};
 
  • Like
Reactions: ShadowOne333
You don't change the path in the source code.
When you use an external loader (GX, Wiiflow, postloader), the loader generate the nincfg.bin files which contains all the settings, and then launches nintendont.
Nintendont use this file's content as base for its own settings.

When the loader generate the nincfg.bin file, it can store two different path in it : the ISO path and the Cheat path.
it means that the loader can point to whatever path and file you want, the game don't need to be in /games/, the cheats don't need to be in /games/GameID/ etc.
USBLoaderGX are storing cheat codes in sd:/codes/, so when you launch a game with USBGX it write the cheat path in nincfg.bin and tells nintendont to use the given path instead of the default one.

nincfg.bin format is as follow:
Code:
typedef struct NIN_CFG
{
u32 Magicbytes; // 0x01070CF6
u32 Version; // 0x00000002 since r42
u32 Config;
u32 VideoMode;
u32 Language;
char GamePath[255];
char CheatPath[255];
u32 MaxPads;
u32 GameID;
} NIN_CFG;

the unsigned int "Config" is the one which stores the settings:
Code:
enum ninconfig
{
NIN_CFG_CHEATS = (1<<0),
NIN_CFG_DEBUGGER = (1<<1),
NIN_CFG_DEBUGWAIT = (1<<2),
NIN_CFG_MEMCARDEMU = (1<<3),
NIN_CFG_CHEAT_PATH = (1<<4),
NIN_CFG_FORCE_WIDE = (1<<5),
NIN_CFG_FORCE_PROG = (1<<6),
NIN_CFG_AUTO_BOOT = (1<<7),
NIN_CFG_HID = (1<<8),
NIN_CFG_OSREPORT = (1<<9),
NIN_CFG_USB = (1<<10),
NIN_CFG_LED = (1<<11),
};
So that means that once I load nintendont from a loader like Wiiflow, it will change the default path in the nincfg.bin file of intendon't, after that, if I enable CHEATS PATH, Nintendont will go to the patch chosen by the loader for the cheats in .gct format, right?
 
REV: 115
SIXAXIS
USB

Could someone shed some light into why my SIXAXIS pad is not working? This is the first time I have tested Nintendont since the Alpha that only played wind waker. The pad worked fine then.

I'm launching nintendont from USB and have https://github.com/Nanolx/nintendont-controller/blob/master/nintendont_ps3.ini Renamed to controller.ini in the root on my USB drive.

Pad is connected to the bottom rear USB port, flash drive is on the top rear port.

The pad works fine in HIDtest

Have enabled HIDdevice in settings.

Always get the error that "HID:Config does not match device"
Followed by an instant restart.


I have tried deleting nincfg.bin and starting again, still no joy.

Don't know if it helps, but this is the contents of nloader.log

Code:
Kernel:"/shared1/00000031.app"
KernelSize:168512
LoaderSize:00000594
PHeaders:15
PHOffset:52
Type:1 Offset:0000




Just realized I'm an idiot. I was right clicking and saving the INI file, instead of following the link and copying the button info into a fresh controller.ini.

Everything working grand now.
 
REV: 115
SIXAXIS
USB

Could someone shed some light into why my SIXAXIS pad is not working? This is the first time I have tested Nintendont since the Alpha that only played wind waker. The pad worked fine then.

I'm launching nintendont from USB and have https://github.com/Nanolx/nintendont-controller/blob/master/nintendont_ps3.ini Renamed to controller.ini in the root on my USB drive.

Pad is connected to the bottom rear USB port, flash drive is on the top rear port.

The pad works fine in HIDtest

Have enabled HIDdevice in settings.

Always get the error that "HID:Config does not match device"
Followed by an instant restart.


I have tried deleting nincfg.bin and starting again, still no joy.

Don't know if it helps, but this is the contents of nloader.log

Code:
Kernel:"/shared1/00000031.app"
KernelSize:168512
LoaderSize:00000594
PHeaders:15
PHOffset:52
Type:1 Offset:0000


Man, you can download:

http://www.mediafire.com/download/3zk7zash44i88mv/controller.ini

And put in the root usb drive, just this! I have a PS3 dualshock too. Delete the old file.
Try this!Tested and works!
 

Site & Scene News

Popular threads in this forum