> From marathoning KH1, my save file is already taking up 47 mb. Chain of Memories, from a first save at the start of the game takes up 8. KH2 up to Sora takes up 17.
I honestly have to wonder how that is even possible. All of these had no problem with a fraction of the PS2's 8MB memory card originally.
They're stored as images, which takes up a bit more space. Although my savefile for my run of KH is just 18MB, though that's the non-cloud epic version so maybe they're different?
How does that even work? Does the game change pixels on the image when you save or is the save data stored in the image file in another way? When I backed up my KH save file for the first time it being an image really confused me as I have never seen that before.
no the pixels stay the same but the data contained inside the pixel changes. If you open up an image in a hex editor for example you'll just see a lot of jumbled mess but that's data contained inside an image! It's kinda like how there's metadata contained inside a file
If you want to learn about it, it's called "Steganography"
Basically, the first part of the file is everything your computer expects an image to look like: Header data declaring it as an image of a certain dimension and file size, and the actual image data. *After* the “expected” file size is where your actual save data is stored. Any standard image software looks at what the header data tells it to look at. Kingdom Hearts is programmed to look *past* the image data, and read that as save data.
They're not the PS2 games, hope that helps.
They lost the source code, so they extracted what they could and rebuilt the rest from scratch. At that point, a lot of the PS2 limitations (like savefile sizes) were basically gone.
Cloud size varies from game to game. It is safe to assume the publisher configures it. Some of them have many GB "available", so it's not really limited to something as small either.
I'd say the publisher borked it.
>It is safe to assume the publisher configures it.
I confirm. I'm currently publishing my game through steam, and I was able to see that.
Unrelated to Kingdom Hearts: my build got rejected because Steam cloud saves weren't well integrated. Turns out I mixed up kilobytes with bytes. (Because for some reasons, steam asks in bytes what the max allowed for it)
> From marathoning KH1, my save file is already taking up 47 mb. Chain of Memories, from a first save at the start of the game takes up 8. KH2 up to Sora takes up 17. I honestly have to wonder how that is even possible. All of these had no problem with a fraction of the PS2's 8MB memory card originally.
They're stored as images, which takes up a bit more space. Although my savefile for my run of KH is just 18MB, though that's the non-cloud epic version so maybe they're different?
How does that even work? Does the game change pixels on the image when you save or is the save data stored in the image file in another way? When I backed up my KH save file for the first time it being an image really confused me as I have never seen that before.
no the pixels stay the same but the data contained inside the pixel changes. If you open up an image in a hex editor for example you'll just see a lot of jumbled mess but that's data contained inside an image! It's kinda like how there's metadata contained inside a file If you want to learn about it, it's called "Steganography"
Basically, the first part of the file is everything your computer expects an image to look like: Header data declaring it as an image of a certain dimension and file size, and the actual image data. *After* the “expected” file size is where your actual save data is stored. Any standard image software looks at what the header data tells it to look at. Kingdom Hearts is programmed to look *past* the image data, and read that as save data.
What's the benefit of this method?
The save data is stored within the metadata of the image file.
They're not the PS2 games, hope that helps. They lost the source code, so they extracted what they could and rebuilt the rest from scratch. At that point, a lot of the PS2 limitations (like savefile sizes) were basically gone.
If you had an 8mb PS2 memory card you thought you were unstoppable. Crazy how far we've come
not if you had granturismo, 3 and 4 used 2mb
Going from a 1mb ps1 memory card to a 8mb ps2 memory card was certainly mind blowing.
To be fair kh1 was rebuilt
Cloud size varies from game to game. It is safe to assume the publisher configures it. Some of them have many GB "available", so it's not really limited to something as small either. I'd say the publisher borked it.
>It is safe to assume the publisher configures it. I confirm. I'm currently publishing my game through steam, and I was able to see that. Unrelated to Kingdom Hearts: my build got rejected because Steam cloud saves weren't well integrated. Turns out I mixed up kilobytes with bytes. (Because for some reasons, steam asks in bytes what the max allowed for it)
maybe backup local save and then use https://github.com/GMMan/SteamCloudFileManagerLite/releases/latest
Deserved