summaryrefslogtreecommitdiff
path: root/Source/Android/code-style-java.xml
diff options
context:
space:
mode:
authorJosJuice <josjuice@gmail.com>2020-02-23 20:56:18 +0100
committerJosJuice <josjuice@gmail.com>2020-06-17 12:32:39 +0200
commit75d032161f5d9ca450d21520eaa75a5be2f1f9ee (patch)
treecaec92efd4eda45dd16c24eac0674df655321f80 /Source/Android/code-style-java.xml
parent7cdd0e243080f791bc48d89aa94e5886e6a6ebd9 (diff)
DiscIO: Rework the implementation of TGC reading
Fixes https://bugs.dolphin-emu.org/issues/10654. To quote the documenation file included with the program tgctogcm: "TGC's are miniaturized .gcm images with a 32kB header. The embedded gcm contains some bogus data, namely: -FST Location (0x424 in gcm) -DOL Location (0x420 in gcm) -FST File offsets (all files are offset/spoofed by a certain amount)" Dolphin has been handling the values at 0x420 and 0x424 by simply overwriting them with a working value (just like tgctogcm does), but it has used a different approach for the file offsets in the FST. Instead of changing the offsets that are stored in the FST, Dolphin changed where the files actually are placed on the virtual disc. My hope was that this would make the loading times more accurate to how they are when running a TGC file as part of a larger disc. However, there are TGC files where we would need to move files backwards on the disc in order to do this (this is what issue 10654 is about), so the approach we have been using is flawed. This change makes Dolphin overwrite offsets in the FST instead, like tgctogcm does. Other than making Dolphin handle the affected TGC files correctly, this change also makes it so that unnecessary padding data isn't written if you use Dolphin to convert a TGC file to an ISO file. This feature is not actually implemented in Dolphin as of now, but I'm planning to add it in the near future as part of a larger feature.
Diffstat (limited to 'Source/Android/code-style-java.xml')
0 files changed, 0 insertions, 0 deletions