Forums | Moodkie Interactive

Hi there, They don't get different reference IDs every run because they're not referenced per se. It's that you're creating a new instance each time, which means it's a different instance on every run, so it will have a different instance ID. You can try assigning your own reference ID using ES3Ref...

Do the sprites just get random ref values every run because they aren't referenced by MonoBehaviors in a scene? I have a MonoBehaviour that references the ScriptableObject chain that ultimately has a reference to the Sprite. I would just expect ES3 to be able to traverse that hierarchy to get the Sp...

Hi there, This will most likely be because a reference to that Sprite doesn't exist in the manager. Are you getting any warnings when you load? All the best, Joel That's the issue. Unfortunately it wasn't an issue before the Unity & ES3 update. At the moment, I don't know if it was only caused ...

I'd like to see serialization attributes to let me specify per field how ES3 will save the field. When you have a scenario where you have references to instances of ScriptableObjects as well as regular ScriptableObject references. You will likely want to save the ScriptableObject instance (Object.In...

Updated to 2019.4.1f1 and latest Easy Save 3 and now Sprites are being deserialized as null objects.
Looking in the save file JSON I see
"Graphic" : {
"_ES3Ref" : "3523149218884764385"
},
as the stored value. Maybe that isn't correct?

This can happen if you have a Don'tDestroyOnLoad set on the manager. I don't remember how to make it automatically get added to scenes again so can't help you once you remove the DDOL.

Same behavior for me. I'm using a 'do not destroy on load' script for a lot of UI items which are shared between the start menu and any given scene. I didn't actually notice it was an issue with ES3 and loading scenes additive until I saw the title of this thread. After noticing that, I slapped a 'd...