Originally posted by natnew
for some reason, every time I try and load state, I get the message "unable to load state 0" even if I saved .25 seconds ago
Yep, broken for me too. Apparently I managed to zero out the "ZSNES Save State File V143\x1a\x8fZMZ ZMZ ZMZ ZMZ" header from the savestates, making ZMZ think it's an emulator native savestate, despite not being so. At least the error handler got tested.
Fixed. There are far too many ways to break something that worked yesterday.
And because I got bored, you can now stick in non-SNES cores.
Known bugs, mostly things I won't fix:
- Checksums always report broken - are there any in non-SNES ROMs? If yes, how do I find them without teaching ZMZ about every single ROM type?
- Internal ROM names are garbage - are there any in non-SNES ROMs? If yes, how do I find them without teaching ZMZ about every single ROM type?
- Everything that isn't SNES is letterboxed - I can't resize the window without breaking the menues completely, and I'm too lazy to add an upscaler to set the image to 256x224.
- Some cores may print UNSUPPORTED LIBRETRO CORE with sound working - this is caused by trying to show a too big image. It's not impossible to fix, but I'm not going to care until, at least, I find a libretro core that triggers that.
- File extensions are still .zst/.srm/etc for non-SNES cores. There's no obvious replacement, and there's not even any obvious way to ask a libretro core which system it emulates.
- It doesn't pick different cores for different ROM types. You can copy ZMZ to multiple folders if you want ZMZ for everything.
- ROMs larger than 64MB won't load either. It is fixable, but I don't think there are any that large ROMs that make sense in ZMZ.
Still, vba-next doesn't misbehave too badly.
(The bad part is that I'm starting to like it.)
<blm> zsnes users are the flatearthers of emulation