Forums | Moodkie Interactive

Hi there, This indeed seems to be a bug in the Unity 2018.3 beta. I've submitted a bug report to Unity. In the meantime, you can manually edit the array by going to Assets/Plugins/Easy Save 3/Resources/ES3/ and manually modifying the Assemblies containing ES3Types array of the script attached to tha...

Hi there,

The "Assemblies containing ES3Types" list seems to work fine at my end. Would you be able to PM me a project which replicates this?

All the best,
Joel

Hi there, Ahh I understand. I assume that you're using SD card as the location on Android? These are usually formatted as FAT, which is case-insensitive. Windows and MacOS are also case-insensitive (in most cases). However, iOS and Android (aside from the SD card) is case sensitive. It's usually rec...

Hi there, Would you be able to show me the code you're using to save and load? Hopefully then I might be able to see what is happening Also would you be able to add Debug.Log calls where your save and load code is to ensure that the function they're in is getting called correctly? Also one last thin...

Glad to hear that's all working smoothly for you now, let me know if you run into any other problems

All the best,
Joel

It looks to be first-in-first-out as far as I can tell. Perfectly consistent. The .NET documentation for Dictionary notes that: For purposes of enumeration, each item in the dictionary is treated as a KeyValuePair<TKey,TValue> structure representing a value and its key. The order in which the items...

Hi there, Note, I'm not using ES3.Save, but a single ES3File.Sync. I understand. ES3File.Sync stores keys in the order that they are stored in the Dictionary, which is arbitrarily determined by .NET. If you want to control the order that things are written, you would need to use ES3.Save. as if ES3....

Hi there, The file is read from start to end, but note that most recently saved keys are placed at the beginning of the file, not the end. When overwriting an existing key, the key is also moved to the beginning of the file. So you can use this fact to place your data closer to the beginning of the ...

Hi there, In the case of your examples, this performance difference is expected. Easy Save 2 uses binary serialisation rather than JSON, which is much more compact and allows for some performance shortcuts, at the expense of flexibility. There is a feature request for binary formatting in Easy Save ...

So each single call to ES3.Load or ES3.Save has similar overhead as creating an ES3File reference? Generally, yes. ES3.Save also has the major overhead of having to overwrite a key if it already exists. In contrast, an ES3File represents the entire file, so ES3File.Sync does not need to worry about...