Emulator Issues #6498
closed
Dolphin Lacks the ability to check Gamecube Disc Integrity
Added by JMC4789 over 10 years ago.
Updated about 5 years ago.
Issue type:
Feature request
Relates to performance:
No
Relates to maintainability:
No
Description
There are a lot of bad dumps on the internet for gamecube games, and some of them cause crashes, graphical defects, and other issues that are not dolphin's fault. A way to check the md5, and compare it to redump.org from within dolphin, and perhaps even warn the user (or at least allow the user to check from game properties) would be greatly appreciated. Wii games already have a disc integrity check.
F-Zero GX is a good example, and there are patched isos of Melee floating around that people try to use on Netplay that cause desyncs with normal players.
Even if netplay can't use the md5/disc integrity check, by telling people that they can check it from within dolphin or maybe they get a popup/warning/anything if it's bad.
The possible issue for this would be romhacks, but, I don't think it'd be a huge issue if handled correctly.
- Status changed from New to Accepted
- Issue type changed from Bug to Feature request
- Priority set to Normal
- Category set to ui
- Milestone set to Next
- Operating system N/A added
As a first draft we could probably provide something to compute the file MD5 from Dolphin, without any automatic checking. This might go in 4.0 if we're quick enough to implement it.
I don't want to implement anything that communicates with a remote server until we are using a good framework for the Dolphin UI.
- Milestone changed from Next to Current
4.0 was released, moving Milestone-Next to Milestone-Current.
- Milestone changed from Current to Next
Moving to next milestone since these issues are not critical to a new release.
If you feel strongly about this issue and want it to block the next Dolphin release, please assign yourself as owner and re-add Milestone-Current.
It would be nice to have the ability to do an entire library scan within Dolphin as well as a per disc check if that's possible.
One quick way to tell if an ISO's integrity is invalid could be to check the filesize. Unless it has been compressed, any valid GC ISO should always be 1.36 GB. Any GC file below that size could be marked as invalid.
As for where the user could check this, file integrity could be listed in ISO properties along with the MD5 checksum. The MD5 integrity check could be done when computing an MD5 sum.
- Milestone changed from Next to Current
5.0 was released, moving Milestone-Next to Milestone-Current.
- Status changed from Accepted to Duplicate
We have MD5 calculation now (issue 6499). What's left is looking up the hash in a database, which is better described by issue 10867, so I'm marking this as a duplicate of that.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by