Ocarina of Time Randomizer Save flag issues #945
Millennium-Eagle
started this conversation in
General
Replies: 2 comments 3 replies
-
Interesting, this should be identical to the RetroArch version. As to how it may have happened, I truly have no idea, it would have been a problem with the core itself, if it's not a game bug. I don't do anything special with the core that could cause something like this. If it really is a problem, it would be good to come up with a reproducible test case so that it can be figured out. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Do you change the file names of the ROMs before adding them to the phone? And/or do you have |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
A while ago, I had an issue in an Ocarina of Time Triforce Hunt Rando where loading an autosave state could cause me to lose triforce pieces; permanantly if I saved the game afterwards, as the chests that contained them would stay open. After that, I turned off autosave states, but I have since learned that this isn't an issue that should necessarily happen with all emulators, and in fact, does not seem to happen with most of them.
More importantly, however, after playing tons of Randos with no issues, I discovered that one of the skulltulas I hadn't collected yet was missing (the one on the graveyard wall as child). I know I didn't forget about collecting it because it required boomerang and I had only just gotten boomerang. I might have killed it with slingshot to see what it was, but I don't remember, and killing it shouldn't remove it unless you collect the item it drops. Luckily, it was only a couple of rupees, according to the spoiler log, but if it was anything important I would have been screwed. I reloaded the area and changed time of day multiple times to see if it would reappear, but to no avail.
I reported the issue to the devs in the Oot Rando discord, but they seemed to be under the impression that it was an emulator issue, as they haven't heard of an issue like this happening before in one of their officially supported emulators. I also brought up the Triforce Hunt issue, and they also haven't heard of that problem before, which more or less confirmed it was an emulator issue for them.
I don't know what could cause this issue, but it might also be worth nothing that I have never, ever encountered a TLB exception in this emulator, despite this emulator having the same workaround for it in its options as Retroarch's Mupen64 Plus Next does. I don't know if that helps work out any of the differences between this emulator and other Mupen64 Plus versions that could cause these other issues.
Beta Was this translation helpful? Give feedback.
All reactions