Noisy prefab localRefs changes

[Torsteinara]

We're using Easy Save 3 for our current project and are mostly very happy with it. But when we modify prefabs and scenes it updates the localRefs in a bunch of other prefabs, in a way that's unpredictable to us. Which causes a lot of noise when we're committing our work in git. Sometimes every ES3 enabled prefab in the project will have its localRefs changed without us knowing why. The localRefs in the ES3Prefab components also contain lots of references to things all over the project, not just components local to the prefab.

Is this the intended behaviour for ES3, or have we configured it incorrectly somehow?

We're using Auto Save, and have a multi scene setup. Which works great for us. Some components are saved directly in the scenes but most are spawned in at runtime as ES3 prefabs. I read something in a different topic that made it sound like prefabs with the ES3Prefab component should not be placed in scenes at edit time. Is that the case? We do have some instances of this. But we could make scene-specific versions of those prefabs.

[Joel]

Hi there,

The localRefs are the dependencies of the prefabs, so if there are cross-prefab dependencies then this would be expected behaviour.

If there aren't, please could you replicate this in a new project with a simple scene and send it to me using the form at moodkie.com/repro.

I read something in a different topic that made it sound like prefabs with the ES3Prefab component should not be placed in scenes at edit time. Is that the case? We do have some instances of this.

There are specific situations where you shouldn't have the ES3Prefab Component (for example if you're saving the destroyed state of the GameObjects), but I wouldn't worry about this unless you're having issues with these GameObjects.

All the best,
Joel