Search the Community
Showing results for tags 'save states'.
Found 2 results
This is the number one thing that drives me nuts about the 3DO; saving. There is very little save memory (32kb sram); and no way to get in to manage saves unless you are playing a game and run out of memory. THEN you have to guess what you are deleting since most of the file names are nonsense. Does anyone know a fool proof easy disk to get into the memory manager? I believe it's on one of the demo/sample disks but I went into three the other day and couldn't find it. Why they would not allow you to access this when no disk is inserted is beyond me. There is the "japan only" 256 KB memory unit but it's like $200 bucks, which is a joke. Anyone have one? Also---If you remove your optical drive with the SD Card unit; i wonder if you can do save states to that unit; or if it still goes into the system sram? Oh well; any help appreciated as this frequently irritates the hell out of me when going on long 3DO gaming bouts.
Thanks to Shamus et al. I was not sure where to send this, so I will post it here. Attached is a patch against the current git version. Tested only on Linux/x86-64/Qt4. virtualjaguar-savestates.diff.txt There is a new 'Tools' menu, with Dump/Load and the option to choose from 10 save slots per game. Notes: Sometimes the audio will be screwed up after loading the save state. Try loading the state several times, by holding down the load button/key for a second or two. The escape key toggles full screen mode. (It was F9 ...) F5/F8 are mapped to Dump/Load. Fixed sample buffer overrun in DSPSampleCallback. Should compile with either Qt4 or Qt5. Stopped randomizing RAM contents on startup, in order to better compress the state file.