Forums | Moodkie Interactive

Hi there, Performance very much depends on the data, the hardware you're running on, and when you save. If you're frequently changing individual items in the array and need to save that change immediately then it would make sense to save items as individual keys. However, if you do this you will def...

As this is a generic error, and there are no line numbers for where this is happening, it's difficult to know exactly what is happening. However, the most likely cause is that the path provided is not a valid path for iOS. However, this would only throw this error in earlier versions of Easy Save. J...

Hi there,

It's not possible to tell what is happening as what you've posted is the stacktrace of an error message rather than the error message itself.

All the best,
Joel

Hi there,

It's not possible in the way you've described unfortunately as random-access happens at a key level, not a field level. The alternative would be to save the variable as a separate key.

All the best,
Joel

Hi there, When I save and load the list from ScriptB, ES3 automatically creates an object and adds the component. This indicates that you're saving a GameObject, not a script. Instead you should save the script and use ES3.LoadInto to load the data into an existing script instance. Another option wo...

Number of keys is usually a much bigger factor than file size, but in both cases you can follow the Improving Performance guide to improve this significantly:

https://docs.moodkie.com/easy-save-3/es ... rformance/

All the best,
Joel

Hi there, You would need to save the entire ScriptableObject again, or instead of saving the ScriptableObject, save it's fields separately. Note that generally a ScriptableObject with loads of fields isn't going to be particularly intensive to save unless the fields themselves are complex types (i.e...

Hi there, Please could you double check that you have the PLAYMAKER_1_8_OR_NEWER is defined in Edit > Project Settings > Player > Scripting Define Symbols? That's the only other thing I can think of which would cause this. If it's absent then this would indicate a bug at PlayMaker's end as it would ...

The tutorial project is saving the assets when quitting but not their position in the game. Not sure if that is something we are supposed to change but I do not see any instructions so I'm confused. Basically all the shapes spawn at position (0,1,-10) Thanks for the heads-up, it looks like we expor...

Hi there, We've not released any updates recently, and we hadn't made any changes to the PlayMaker actions in the previous update. Missing actions usually means that there's a compilation error in your project preventing scripts from being compiled. Could you confirm whether you're getting any compi...