PS4 PS4 Unity game save corrupted

[pink1]

I've been working on a game using Unity & I've ran into a few problems the big one is saving on the PS4. If I use the newest PS4-Fake-PKG-Tools it doesn't save at all & if I use the ones from RetroGamer74s guide it saves but when I restart the game the save is always corrupted.
I feel like I must be missing something but I can't figure it out. If anyone has any ideas or knows what I'm doing wrong I'd love to hear it.

PS. I'm just using playerprefs for saving.

 

[Gregor]

I don't know if this will be helpful as it's been a very long time since I've messed with ps4 pkgs. have you tried liborbispkg? it's the homebrew equivalent of the pkg tools that a lot of homebrew developers use, because I don't think it uses any sony code. I think you have to inject the keystone for fpkg tools, but liborbispkg is more versatile as it will add everything instead of skipping certain files normally created by the official pkg tools, which would cause errors. I don't remember that much more atm, but I'll let you know if I remember anything else (if this was even helpful).

 

[Gregor]

sorry for the double-post, but btw, here it is: https://github.com/maxton/LibOrbisPkg

iirc, the difference is that the normal tool uses .net framework, and I think "core" uses .net Core Framework, if using cmdline. afaik, that's the only difference, but I could be wrong. I know that lightning mods uses this for his stuff, and OpenOrbis does as well by default, I think.

 

[pink1]

sorry for the double-post, but btw, here it is: https://github.com/maxton/LibOrbisPkg

iirc, the difference is that the normal tool uses .net framework, and I think "core" uses .net Core Framework, if using cmdline. afaik, that's the only difference, but I could be wrong. I know that lightning mods uses this for his stuff, and OpenOrbis does as well by default, I think.

Thank you, I'll check this out & see if repacking with this solves the problem.
Thank you so much for your time

Edit I've been talking to the amazing Lapy & he's trying to get me straightened out

 

[pink1]

After trying to repackage it I was still having trouble so I tried removing all calls to the save & it was still saying the save was corrupted. I was about to pull out the last of my hair when it hit me the only thing it could be was the save icon, my icon was at 32 bit depth. Removed the save icon & is no longer corrupting the save.

Thanks to everyone who took the time to read this and offer advice.

 

[Gregor]

After trying to repackage it I was still having trouble so I tried removing all calls to the save & it was still saying the save was corrupted. I was about to pull out the last of my hair when it hit me the only thing it could be was the save icon, my icon was at 32 bit depth. Removed the save icon & is no longer corrupting the save.

Thanks to everyone who took the time to read this and offer advice.

wow! glad you got it fixed, my friend. I know the ps4 is very stingy. it doesn't accept certain title ids, for example. the ps4 fpkg generator will stop a pkg from being built if it has a title id the ps4 won't accept; liborbispkg won't though, so if you try installing it on the ps4, it will error at install iirc. that's a negative about liborbispkg being less restrictive, so I think that's why most homebrew start with an I-something in terms of title/content ids.

 

[pink1]

wow! glad you got it fixed, my friend. I know the ps4 is very stingy. it doesn't accept certain title ids, for example. the ps4 fpkg generator will stop a pkg from being built if it has a title id the ps4 won't accept; liborbispkg won't though, so if you try installing it on the ps4, it will error at install iirc. that's a negative about liborbispkg being less restrictive, so I think that's why most homebrew start with an I-something in terms of title/content ids.

I feel a little silly because it refused to build with a start-up image that was 32bit.
Now I'm down to fixing one more bug in mode b(sounds better than code I forgot to write) & I should be about ready to post it

 

[Gregor]

I feel a little silly because it refused to build with a start-up image that was 32bit.
Now I'm down to fixing one more bug in mode b(sounds better than code I forgot to write) & I should be about ready to post it

maybe it's a good thing that ps4 fpkg generator is so restrictive, because the ps4 itself is such as well. the ps4 fpkg stuff is from the official sdk, so it's sony code. it's simply a hacked version of it to allow fpkg. I guess it's trying to prevent mistakes by developers or something. they built liborbispkg to get away from that, but being less restrictive isn't always the best thing, considering the ps4 itself is pretty restrictive. I was able to build the homebrew store, with the help of LM, on the system, but it would only install with a very specific content id iirc. maybe they're trying to prevent unauthorized content from being installed? I got banned on the ps3 about ten or more years ago, and I had no pirated content on my system, but where they get you is that "unauthorized content," which I think includes homebrew of any kind.