-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while ripping mario kart double dash #11
Comments
Sorry to hear you're having this issue, it sounds like this is either an issue with the ROM itself or finding the right directory. Was this ROM an NKit ISO downloaded from Vimm's Lair? If so, this might be the same issue as #9. If not, could you calculate the file's SHA256 via this site and tell me what it is? |
Thanks for the reply! Neither seemed to work when i tried. I also just tried downloading the pure ISO straight up from another website altogether, and got the same SHA256 result + error |
Actually, I've just verified that NKit ISOs should work since a recent change I made, so #9 should no longer be applicable here. So I'm not really sure exactly what is causing the issue you're facing. Is it possible you're using actually using a .CISO formatted ROM? I've just tried testing those too, and can verify those still don't work. If it's not a .CISO, could you give the SHA1 of the original version of the file before you converted it? |
Actually nevermind, I just figured out how to add support for CISO ROMs lol. Can you download the latest build and try again? If it's still not working, then you can try sending the SHA1 like I mentioned above? |
Grabbing latest worked for some reason lol, with the same roms. |
Hi there! I'm new to this tool, and really excited to try it out. I get this error while trying to rip MKDD though:
It produces no files before the error. I am using an ISO file that I renamed to "mario_kart_double_dash.gcm", and placed it in the cli/roms folder. I verified that Dolphin can run that file "mario_kart_double_dash.gcm" just fine.
If you have any insight if this is user error or a new bug, that would be much appreciated!
The text was updated successfully, but these errors were encountered: