I tried doing that and got a different hash still.In the stream of retrogamer74 they said that you need to erase the first 100 bits of the game and then recalculate the hash.
I tried doing that and got a different hash still.
Edit: First 100 bytes, that is.
I mean, I'd assume bytes. 100 bits is only around 12~13 bytes, which isn't even the full header. And I just tested it anyways and it doesn't match either.he said bits, not bytes.
Yeah sorry my mistake, i misunderstandI tried doing that and got a different hash still.
Edit: First 100 bytes, that is.
I'm using HxD, a hex editor.Setting load bios to true in data/database/config/MarioSunshine.config crash on boot, setting "UseDolHash" : false, as well as taking out hash data in rom.json the game boots. I'm gonna try to strip out stuff in the config files to see what's really needed to keep the game running.
What tools are you guys using to get all the different hashes?
He also said that the hash check can be disabled.he said bits, not bytes.
It seems like only the dol hash can be disabled, not the others unfortunately.He also said that the hash check can be disabled.
They used the PAL ROM as a base, hence it running at 25. The 'keyboard inputs' / unusual characters are done so they can overlay something like '^' with a switch button in the overlayed font, and the cut out voice clips are done so they don't have to rerecord lines or anything.The sunshine .gcm provided does work on dolphin but at 25 fps for me and the videos play audio but only the subtitles, and some of the sound is weird like the name of the button is cut out. Also in the subtitles and the map screen there are references to keyboard inputs.View attachment 224999
View attachment 225000
And I think the hash will be of the .dol executable within the .gcm, not of the iso itself.
010049900F546002\romfs\data\database\hagi\MarioSunshine.json
{
"Info": {
"GCM": {
"Name": "Super Mario Sunshine",
"CountryCode": "EU",
"GameID": "GMSP",
"DVD": 0,
"ROMVersion": 0,
"GCMID": "GMSP.0.0"
},
"Hashes": {
"exe": "f4425036b50590ea5c9357580abe922decf72012",
"media": "763cae402272dd4fc428f45238c3ae040d6cb1a2",
"full": "b23b9b9ee9365e26f8159c36ae80981412bf7372"
},
"UID": "MarioSunshine",
"ShortName": "MarioSunshine"
},
"Mxic": {
"Hashes": ["0xD7E6E7E5", "0x1E9791F9"]
}
}
Would it at all be possible to disable the checks all together?
Maybe set ‘use dol hash’ to false, or comment out/remove hash related categories altogether.... see if ninty actually made them a prerequisite
edit:
looking forward to a compatibility list soon
Maybe nulling it would work - but I'm not sure. Looks like compiled code to me? Disassembly when /sI found a reference to SHA1 in the "main" file you get when you extract the exefs for sunshine's nca
--------------------- MERGED ---------------------------
Would it at all be possible to disable the checks all together?
I'll see what happens, will report back in a bit@KiiWii already suggested this but it was missed
I found a github repo named after one of the terms in the hex data you posted, though I'm not sure how much it will help, or if it will help at all.I found a reference to SHA1 in the "main" file you get when you extract the exefs for sunshine's nca
--------------------- MERGED ---------------------------
Would it at all be possible to disable the checks all together?