Hello,
I'm working on a project to translate SRW GC, along with Dashman who's also on here. https://forums.dolphin-emu.org/Thread-so...breakpoint
We've made some great progress so far. VWF has been implemented, which is the biggest thing that I've been responsible for. However, the font itself has to be hacked into memory. Currently, we have a small bit of free space where we've inserted the font, but it starts overwriting important data if we put too much in. As such, we'd rather replace the original font with our new font on the disc, but that requires us to understand the compression/decompression algorithm.
We have the original file from the iso, and we have the decompressed file pulled from memory. If I try launching Dolphin normally, the data is immediately in memory. If I don't skip BIOS and use the IPL, the moment that the contents appear in memory is after the processor exits from a loop where it's querying 0x8145D998 constantly. Once that value is non-zero, the data is where it should be. I'm pretty confident that this is some combination of DMA and using the operating system's decompression algorithm. I was wondering if that decompression routine is documented somewhere?
Thanks
I'm working on a project to translate SRW GC, along with Dashman who's also on here. https://forums.dolphin-emu.org/Thread-so...breakpoint
We've made some great progress so far. VWF has been implemented, which is the biggest thing that I've been responsible for. However, the font itself has to be hacked into memory. Currently, we have a small bit of free space where we've inserted the font, but it starts overwriting important data if we put too much in. As such, we'd rather replace the original font with our new font on the disc, but that requires us to understand the compression/decompression algorithm.
We have the original file from the iso, and we have the decompressed file pulled from memory. If I try launching Dolphin normally, the data is immediately in memory. If I don't skip BIOS and use the IPL, the moment that the contents appear in memory is after the processor exits from a loop where it's querying 0x8145D998 constantly. Once that value is non-zero, the data is where it should be. I'm pretty confident that this is some combination of DMA and using the operating system's decompression algorithm. I was wondering if that decompression routine is documented somewhere?
Thanks