Get Easy Save from the Unity Asset StoreHello again!
So I believe I've ran into this issue before, but I want to make sure I understand how ES2 is expected to work.
I have a custom class named "ObjectDescriptor.cs" and have used "Manage Types" to specify all the variables that are saved for this class.
I have creates several save files for this class.
I then have modified ObjectDescriptor.cs and added some new fields that need to get saved.
After adding the new fields, the load for older files isn't working, and I get a "Failed to read past end of stream" error.
Is this expected? If so, this creates a headaches because it difficult to add new features to my game and retain compatibility with older save files.
Can you explain how to handle something like this? I need my game to be able to load both older and newer save files. Thanks!
Backward compatability
Re: Backward compatability
Hi there,
I describe a method of doing this in the second post of this thread which should guide you in the right direction: http://www.moodkie.com/forum/viewtopic. ... 853&p=2195
All the best,
Joel
I describe a method of doing this in the second post of this thread which should guide you in the right direction: http://www.moodkie.com/forum/viewtopic. ... 853&p=2195
All the best,
Joel
-
trendtimer
- Posts: 21
- Joined: Wed Jun 08, 2016 9:31 pm
Re: Backward compatability
Thanks. I'm saving a version number in my files now and will implement the solution you proposed. This should work. It's definitely good to get this kind of thing sorted out before releasing! It would be a real problem if you got stuck in a situation were adding to the game caused old save files to break.
On another happy note, I'm finally starting to test saving and loading games from a Built game instead of the editor. I've been disappointed at how slow the loading and saving has been while running in the editor, but it's much much faster (maybe 8-10 times?) when running a Built game! I'm not sure what causes the slowness in the editor. It's not necessarily ES2 being slow. I'm doing a lot of object instantiation, and animation script instantiation, and also doing a ton organizing objects into parent/child hierarchies.
On another happy note, I'm finally starting to test saving and loading games from a Built game instead of the editor. I've been disappointed at how slow the loading and saving has been while running in the editor, but it's much much faster (maybe 8-10 times?) when running a Built game! I'm not sure what causes the slowness in the editor. It's not necessarily ES2 being slow. I'm doing a lot of object instantiation, and animation script instantiation, and also doing a ton organizing objects into parent/child hierarchies.
Re: Backward compatability
Glad to hear that solved your problem. You'll be glad to hear that Easy Save 3 (which will be a free update for all existing users) will automatically do this for you.
With regards to performance, I believe the Editor is much slower than at runtime (not just for Easy Save but for all code) as there's a lot of debugging/sandboxing going on which doesn't happen in a built player. I've found that having the Profiler open especially reduces performance.
All the best,
Joel
With regards to performance, I believe the Editor is much slower than at runtime (not just for Easy Save but for all code) as there's a lot of debugging/sandboxing going on which doesn't happen in a built player. I've found that having the Profiler open especially reduces performance.
All the best,
Joel