Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Amstrad Cpc Save - Restore problems

A topic by AmintaItch created Dec 10, 2023 Views: 175 Replies: 5
Viewing posts 1 to 2

Hi!

I'm running the game on MiSTer Amstrad Cpc 6128 core, that is near to perfect but I've got a problem when I try to restore a saved game.

I save the game on a second blank disk but, when I restore it, I get strange errors like those in the images below. 

Any hint?


Thanks,
Davide






Hi! Thanks for reporting this issue. This didn't happen in testing so I would love to do some more digging to identify what might cause this. Would be great if you could share files/disk images so we can investigate what might be happening. Feel free to reach out to Stefan or myself @sijnstra on the PunyInform discord https://discord.gg/VNztJvcm3g - I can also be found other ways if you don't do Discord.

Thansk to Sijnistra the problem it's solved!

You have simply to put a formatted "save disk" in  the 2nd drive and save always to this disk with: "b:save1",

I take this opportunity to give also my compliments to Stefan, the story is wonderfully written, even better than The Curse of Rabenstein!

Developer

Glad this is resolved! And thank you so much for your feedback, this is the motor that keeps my motivation engine running 鉂わ笍馃檹

Surely this is still a bug that would need fixing, though? There isn't enough space on the original game disc to store a saved game (it requires 11KB and there's only 10KB free), but the interpreter should at least report this and return to the adventure if it fails to save.

Hi Nicholas-Campbell
Thank you for bringing this to my attention. It's a different problem that you've found. The issue in the screenshots was due to swapping the disks during game play. The game continues to read the disk as if it still has the game file content on it. The disk swap has removed the game file so it isn't there anymore. This swap can't be reliably detected.
Please be aware that save game sizes also vary depending on game complexity, as well as how far into the game you are. In general, the interpreter has been successfully detecting and reporting that the disk is full, and gracefully returning. It turns out that the exact current size of the game, and the amount of storage required for this game to save progress hit an edge case where saving the last fraction of a sector wasn't handling the error as well as the rest of the save function does.
Had the game been slightly larger, it would have worked correctly and this would have gone unnoticed. An update to the code is being tested and will be available soon.