Forums | Moodkie Interactive

Hey it looks like the project file is too big to PM, even compressed. Should I PM you a drive or dropbox link?

I thought that might be the case. In an attempt to assess that, I debugged with breakpoints at Start/Awakes in each of my prefab instance's components. This may or may not be a flawed approach to zeroing in on the problem, but my results showed no positional changes until passing each of my breakpoi...

Hey there, I have a prefab instance whose transform.position I'd like to retain when loaded. Currently, when I call the ES3.Load function, my instance is loaded with the prefab's original transform.position, rather than the instance's. Calling the load function a second time moves the prefab instanc...

While working on the simple scene to send over, I was unable to reproduce the bug. Meaning EasySave3 worked perfectly as expected. So I took a look in my project, and surprise surprise. The bug was occurring due to my own error. In short, I failed to enable prefab saving on my prefab's nested prefab...

I've confirmed the JSON file (I love the formatting ES3 provides) includes the missing colliders. If I press play, save the prefab, disable an enabled collider, and hit load, the collider reverts to its saved, 'enabled' state.

Hey there, I definitely missed that step, but after following the steps to add my prefabs' references to the manager while the scene they are in was open, the problem persists. It's not unexpected, with the level of complexity involved in my prefabs. What's surprising is that this is effecting the B...

Hi there, I’m testing the implementation of EasySave3 in my project and have run into an issue. I’ve added an ES3 manager to my scene, and enabled ES3 for prefabs, as well as defined each custom type I have as components on the Prefab I wish to save. In addition to custom types, my Prefab has two Bo...