Emulator Issues #9915
Final Fantasy Crystal Chronicles (Goblin Wall - Mogmail) Read/write error
Final Fantasy Crystal Chronicles
Game ID? (right click the game in the game list, properties, info tab)
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
What's the problem? Describe what went wrong.
Memory write error when opening mail mogmail in "Goblin Wall"
When you close the mail, you get a memory read error
What steps will reproduce the problem?
Tested on single and dual core option
Tested from in game save and from savestate before error read/write started (at boss, last hit to kill and move foward)
Disable "Use Panic Handlers" before you start
- Go to "Goblin wall"
- Beat the boss
- Watch the myrrh cutscene
- Mogmail cutscene starts up and you are given a letter
- Open the mail to respond > Game gives out "Warning: Invalid write" error every frame in the log (http://puu.sh/sxacq/30c9773337.txt loops)
- Exit the menu to go back in to the game > Game gives out "Warning: Invalid read" error in the log (http://puu.sh/sxaro/040b7765d8.txt loops)
- Screen will be black with some audio stutter >> Can not continue
Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?
What are your PC specifications? (CPU, GPU, Operating System, more)
Operating System - Windows 10 Pro 64-bit
CPU - Intel Core i5 6600K @ 3.50GHz
RAM - 16.0GB Dual-Channel @ 1069MHz (15-15-15-35)
Motherboard - ASUSTeK COMPUTER INC. Z170-A (LGA1151)
Graphics - BenQ LCD (1280x720@60Hz) - 2047MB NVIDIA GeForce GTX 670 (EVGA)
Storage - 465GB Samsung SSD 850 EVO 500GB (SSD)
Is there any other relevant information? (e.g. logs, screenshots,
Error log with bother errors in it - http://puu.sh/sx7HF/7f164a4fac.txt
Can provide video if needed
#1 Updated by Nar almost 3 years ago
Issue started with version 5.0-540 (Dynamic BAT, PR #4146). Activating MMU causes the FPS drop to 0 but music continues playing.
In earlier versions, you could complete the dungeon without errors, but then the game saved to a different .gci file with a different header.
#2 Updated by JMC4789 over 2 years ago
- Status changed from New to Questionable
This is definitely a valid issue of some sort, but the bisect is a false positive. MMU emulation just made the previously dangerous behavior no longer happen and crash the game instead, which is favorable.
I have no idea how to test this unfortunately.
#9 Updated by DrevasBellmare 11 months ago
I created an account solely for the purpose of Posting this.
After Multiple tries with the usage of v.5.0-9719 Dolphin to no avail, I went and used an old copy i happened to have of v.4.0-9224 of Dolphin, and following the words of JMC4789, I created a Copy of my Save file under GC USA in a diffrent folder in case. And then tried it again. Not only does v.4.0-9224 run FFCC faster then v.5.0-9719, it successfully passed and saved at the mailmoogle with no troubles at all. No editing or whatsoever needed.
Hope that helps!
#12 Updated by fantesykikachu 8 months ago
I don't know what DrevasBellmare did to get it to work, but i just tried 4.0-9224 and I still get save file corruption, just like everything before 5.0-540 (after which the game just locks up). I then went back and tested 4.0.2, 4.0.1, 4.0, 3.5, 3.0, and I even dug up my archived copy of 2.0, and all of them have save file corruption, (and in case anyone asks I deleted all previous copies of dolphin between tests and moved my "Documents\Dolphin Emulator" folder somewhere else so i was always starting from a clean state between tests. So no, there is no working old build.
If anyone whats to try and fix this but doesn't want to play the game, I can provide save states and FIFO logs from both 5.0 and the latest development version, and if need be I can dump the assembly in visual studio, or GDB but with both of those I don't really know what I'm doing.
It has been so long, and many updates. Has this issue been fixed yet? Has anyone tested to see if it works in the EUR version? The latest development version is 5.0-11199, and the latest stable is 5.0.
What could the older versions of the game be doing right at this point that the newer versions fail at?
The older versions aren't doing it right. Instead of crashing, they're corrupting memory in a way that affects the ability to save.
And no, the issue hasn't been fixed yet. Not sure if anyone has tested the European version, but I haven't heard anyone saying that that version works, at least.
I just tested to clear Goblin Wall on 5.0-11535 with no use. I'm also kind of disappointed that this issue gets no love because isn't a bug that crashes the game at a certain point for everybody pretty important? The issue happens on both NTSC and PAL. I don't know about the Japanese version.
If you want to get past this point without a corrupted save file, use a build prior to 4.0-8131. I bisected that this is the build where the save file corruption started.
"Issue doesn't get any love."
You have no idea how many hours various devs have put into trying to fix this. Sometimes issues like this don't have a clear solution and take a ton of debugging. With all the work that's been done on it, we still don't know what causes it.
Can you retest your bisect? That build doesn't actually touch emulation whatsoever. There are a few builds in that area that seem like they could maybe be related, but definitely not that one. That one just changes the WXWidgets GUI to display savestate information... which no longer exists.
If a second bisect points to that same build... then I'm seriously confused.
I tried around the builds near 4.0-8131, and suddenly, the save file corruption also happened on 4.0-8127. When I try out these builds, I always get the error message "Memory stride is too small". Unfortunately, the bisect tool is broken right now, it takes some time to try out the builds.