Actions
Emulator Issues #9821
closed
MMU Causes Issues with Savestates
Status:
Invalid
Priority:
Normal
Assignee:
-
% Done:
0%
Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:
Description
If you enable MMU and try to load a savestate that didn't didn't have MMU enabled when it was made, then it will fail to load the savestate, and will act as if the savestate was made using a different version of Dolphin. Likewise, if you make a savestate with MMU enabled and then disbale MMU, you will not be able to load that savestate unless you enable it again.
This happens with the stable 5.0 release, as well as the newest versions.
Updated by JosJuice about 8 years ago
- Status changed from New to Invalid
That's expected behavior. The way memory is handled is so different that it isn't really possible to make savestates compatible.
The message that says that the version doesn't match is wrong, but that has already been filed as issue 9815.
Actions