Forums | Moodkie Interactive

Seems to be fixed but it's weird... Upon initial importing of the asset, ES3 added the Easy Save 3 Manager but because I didn't need it then, I removed it. From my test project I noticed that gameObject and I created my own gameObject in the scene called ES3 and attached the same scripts (ES3 inspec...

ok I started debugging in the ES3 code to find the problem and I found it... Noticed the ref Mgr was null. I removed the ES3 object a while ago as I didn't started integrating with a save system back then. Now of course, I didn't remember I needed the ES3 reference manager. I've added the script to ...

ok so when I'm copying everything to a new project, it seems to work. It stores my SOs with an _ESReference. It's the same SO, same Script as I copied it from one project to another... Is there something I can try to troubleshoot this as I obviously can't upload a project to replicate it... Some mor...

will see if I can copy/paste the classes in a new project so I can replicate it...

Been doing some more digging and I definitely think it's something to do with those SOs. When I let him create an ES3Type from the ItemPreferences I notice he does create a reference: writer.WritePropertyByRef("item", instance.item); But when I do save, he doesn't populate the reference. H...

Not sure if it has something to do with it, but I have a class like this: [System.Serializable] public class ItemPreference { public Item item; [Tooltip("Rate for item per day per population")] public float ratePerPopPerDay; [Tooltip("Priority of the need of the population. Will refle...

I finally refactored my code and the saving does seem to work. No more cyclic references anymore :) The saving does work but now I have an error when I load the data, Here's the full stack: I assume it has something to do with ScriptableObjects? I have plenty of those in my components as references....

So, I manage to fix some things but I notice it's not easy... For example I have a lot of references to components instead of gameObjects and that's one of the issues. If I replace something like this: public MyComponent comp with public GameObject go MyComponent = go.getComponent<MyComponent>(); it...

After some research it looks there is some recursive reference. I changed some and now I get a stackoverflow instead of a crash so it's improving... It's difficult to create a project as I'm already far into my project before I integrated ES3 so that's probably my issue as well... I didn't keep seri...

I'm starting to use ES3 and I already created an object that contains most of the data that I want to save. The type of my data container is Dictionary<string, Dictionary<string, IDataClass>> IDataClass is my own and I have several of these in the dictionary. What could be causing the crash? I don't...