Hacking Nintendont

[Cyan]

edit: I was wrong
I thought updating "last working" at the same time as "Version" was a good idea, but when a new revision is released, the "last working" is not accurate anymore.
"Last tested" would be a better name? "Tested and working" ?


If you think of a better way to manage the wiki (without limiting who can edit the page, unless it becomes necessary for vandalism), let us know.
Of course, only users with correct setup (1:1 iso, etc.) should update the wiki, if users don't have correct setup they might mistakenly mark the game as not working because they don't do proper tests (different settings, older revisions, etc.)
We can't determine who has correct setup and gain right to edit or not.

 

[nakata6790]

Of course, only users with correct setup (1:1 iso, etc.) should update the wiki, if users don't have correct setup they might mistakenly mark the game as not working because they don't do proper tests (different settings, older revisions, etc.)
We can't determine who has correct setup and gain right to edit or not.

Exactly... in this thread alone, multiple occasions of false ''not working'' games were reported, only to later discover that it was due to badly trimmed isos.

 

[VashTS]

What about adding only games that work? That's how I do my testing. If it doesn't work, then I don't report it, just games that work.

There can also be a non-compatible list on a separate wiki.

 

[Cyan]

games working in old revision doesn't always work on newer revision.
You would remove them, instead of keep it and telling the user that it used to work up until revision xxx ?

 

[faku1810]

IMO, the wiki is fine the way it is, as long as people fills the "Last working" field only when the update is about the game no longer working or if new Issues appear (because then the last version is needed to pinpoint the cause). If you test the game with a newer revision and it still works fine, you should only update the version number.

But I would add a rule that before editing the list, they should make a post here (or make a new thread for Nintendont Compatibility Tests) to give details about the test made. Then in the notes section of the wiki, they can add a "Last test info" link to said post. That way we'll know who edits the wiki, and the setup they had at the time, and others who have the same game can test to confirm or correct the wiki.

I know it sounds like too much work, but it'd be useful, one single post saying "I use a Wii, HDD, these settings, played X, Y, and Z games for this amount of time, and found these issues." This has been done by a few people in the past to say which games were working or had issues, so it's possible.

 

[VashTS]

games working in old revision doesn't always work on newer revision.
You would remove them, instead of keep it and telling the user that it used to work up until revision xxx ?

Right so it would be this game works on rev x.xx, so we know if its not working its probably your iso or something else. if the list contains only working titles with the rev it works with, thats all i need.

then the list containing not working can specify why not (if it can be explained of course), then if that gets fixed in a newer rev we know which games to test, instead of having to test them all.

IDK maybe my idea isn't good, but I like it. a list of working games and the latest rev they worked on.

 

[faku1810]

Right so it would be this game works on rev x.xx, so we know if its not working its probably your iso or something else. if the list contains only working titles with the rev it works with, thats all i need.

then the list containing not working can specify why not (if it can be explained of course), then if that gets fixed in a newer rev we know which games to test, instead of having to test them all.

IDK maybe my idea isn't good, but I like it. a list of working games and the latest rev they worked on.

You still would have to test the games from both lists to find if a working game stopped working, or you'd keep getting posts of "this game is in the working list, but it doesn't work in latest rev"; and then you'd have to ask all the details about that person's setup, test it yourself if you can, and then go back and test a few revs to find which one broke that game if it did. So in the end, nothing changes and you're only making more work because you have to keep two lists updated.

 

[dapuginto]

I've been trying to get my Dualshock 4 to work on Nintendont but whenever I boot it up it says the controller.ini does not match and reboots. I have put the .ini in the root of the usb loading the game and made sure it wasn't .ini.ini and made sure it was the DS4 ini file. Anyone know what the problem is?

 

[faku1810]

I've been trying to get my Dualshock 4 to work on Nintendont but whenever I boot it up it says the controller.ini does not match and reboots. I have put the .ini in the root of the usb loading the game and made sure it wasn't .ini.ini and made sure it was the DS4 ini file. Anyone know what the problem is?

If it "doesn't match" the VID and PID of your controller must be different from the .ini

 

[dapuginto]

If it "doesn't match" the VID and PID of your controller must be different from the .ini

Any known way to change that?

 

[Deleted member 342493]

Any known way to change that?

You need to modify the controller.ini to match with your controller.

 

[faku1810]

Any known way to change that?

Open HIDTest (link in the first post) check what PID and VID is detected, then compare it to your controller.ini and change it if it's different. If it is, you should also use HIDTest to make sure the buttons are correctly configured as they may be different as well.

 

[Adeka]

Well I can't do any compatibility updates for awhile. Let someone play my Wii U and they decided they were going to format my drive. RIP over 1 terabyte in files

At times like this I wish UStealth was in every version released.

 

[faku1810]

Well I can't do any compatibility updates for awhile. Let someone play my Wii U and they decided they were going to format my drive. RIP over 1 terabyte in files

At times like this I wish UStealth was in every version released.

I'm surprised you haven't killed them yet. But you still had the option to unplug the HDD when not in use by you, i suppose. Adding UStealth (from what i've seen in the "issue" reported in the page) shouldn't be hard, even the first post mentions what's needed to recompile nintendont and make it work, I wonder why the devs haven't made that change to the source yet.

 

[ShadowOne333]

Well I can't do any compatibility updates for awhile. Let someone play my Wii U and they decided they were going to format my drive. RIP over 1 terabyte in files

At times like this I wish UStealth was in every version released.

Actually, that's something that is bugging me.

Maxternal has been releasing UStealth support for some revisions before, yet none of those changes he did were kept for further releases.
Why developers?
WHY?! XD

 

[VinsCool]

Well I can't do any compatibility updates for awhile. Let someone play my Wii U and they decided they were going to format my drive. RIP over 1 terabyte in files

At times like this I wish UStealth was in every version released.

What a shame And I agree with you, UStealth support might be implemented instead being "optional" and being obligated to compile a "mod" version to actually get it.

 

[uyjulian]

Actually, that's something that is bugging me.

Maxternal has been releasing UStealth support for some revisions before, yet none of those changes he did were kept for further releases.
Why developers?
WHY?! XD

Because it requires changes to the dependencies, not the source of Nintendont.

 

[Deleted member 342493]

Actually, that's something that is bugging me.

Maxternal has been releasing UStealth support for some revisions before, yet none of those changes he did were kept for further releases.
Why developers?
WHY?! XD

Yeah, it would be good having Ustealth, but I'm fine for now, maybe in the future, I always access vWii pressing the B button.

 

[VinsCool]

Because it requires changes to the dependencies, not the source of Nintendont.

would it be complicated to point the "libfatmod" in source folder instead of dependencies?

 

[markehmus]

cuz its easy enough for an old dumb ass like me who never did PC shit in school to build Nintendon-t with Maxternals tools , i cant believe how lazy all these spoon fed kids are

take a lesson from this and use the 5mins it takes to read up on how to and you wont be sorry