New Multi-Scene Changes in 5.3.1p4 Issues

Hello,

I've been working on a plug-in to extend multi-scene editing functionality and the new changes to 5.3.1p4 break very desirable behaviour. I want to be able to load a scene that is NOT a part of the build when in the editor, but since I can no longer access EditorSceneManager while the game is running I can no longer do this.

Please reconsider this functionality.

 

Unless this new behaviour is in the changelog as a new feature or fix you should submit this to the bug tracker as a regression

 

It would be great if you could talk directly to a Unity dev who is working with this. I have no idea who that would be, though.

Maybe if @karl.jones sees this he can give better direction.

 

Hello Steen, thanks for the reply.

What I'm trying to achieve is splitting up levels for workflow purposes and then merging them back together during the build process. For example, you should be able to break apart static geometry from audio placement and lighting, so they all live in separate levels. Then a build script should be able to re-assemble these as if they were a single scene.

You should be able to mimic this same behaviour when playing in the editor, so that you're aware that the scenes do not load separately and do not have to be added to the build settings. You cannot do this using PostProcessScene because that executes too late in the build process (Awake/OnEnable occur on all objects, and then PostProcessScene runs, resulting in different behaviour in the editor vs. at runtime). As a result, you must do this as one of the first Awake() calls you receive.

In 5.3.1p2 and p3 this appeared to work correctly (there's some weird rules at the moment, where if the scenes are already open when you hit play, they remain in their current state), but exiting play mode correctly un-merged the scenes. In the new build, I get a warning that I cannot load scenes that are not apart of the build -- but that's precisely what I want to do.

 

Hello Steen,

Thanks for the response! We have indeed chatted before, you were kind enough to warn me of upcoming changes for my previous plug-in.

That would indeed solve my problem, and you could throw it in the InternalEditorUtility or even the Unsupported class to discourage its use. I could also disconnect the prefabs manually once called in play mode, but I have yet to notice this issue -- can you explain how it manifests? I was previously using the internal LoadSerializedAndForget since 4.x without many issues (until 5.x scene serialization that cuts out the duplicate prefab data changed this).

I think a satisfying fix [which I always bring up] would be for PostProcessScene to be able to execute before Awake() (but preferably after all of the data has been deserialized -- so I could Find() my objects or otherwise traverse links). There appears to be precedence for this as RuntimeInitializeOnLoadAttribute allows you to choose before or after a scene. If we could execute the EditorSceneManager.OpenScene during the PostProcessScene in the editor, it would make my desired functionality less than half as complicated.

Related, I don't quite understand why a scene executes Awake() before it's considered loaded, yet all of the scene data exists and is deserialized. I often run into a case in my logs where gameObject.scene.isLoaded returns false -- that's something I was not expecting, is it a bug or is that intended? I've noticed this behaviour (and the ability to use SceneManger LoadScene during Awake) isn't consistent between loading directly into the scene from the Editor, or calling SceneManager LoadScene to enter the level during a play-in-editor session.

Loosely related, I'm also having issues during the build step in PostProcessScene() (or any other function) because if I'm building a currently-open scene, the gameObject.scene ends up being a temporary scene (e.g. Temp/1.backup) and there's no way to decipher what original scene it belonged to (e.g. Level4.unity).

 

We have run into issues with the new Multi Scene Editor, I and others describe the project breaking problem here:

http://forum.unity3d.com/threads/scene-magically-replaced-with-other-scene.383356/#post-2492421

Really need some help with solving this one.

 

Hello Steen,

Any updates on your side? On mine, I am unable to load a "stripped" object (e.g. prefab) using LoadSerializedFileAndForget. This puts me in an awkward position, where scenes saved with SaveSerializedFileAndForget are not stripped, but work correctly and can be loaded by the Editor during a play session, but actual Unity scenes do not load correctly and there's still currently no way to load them during a play session.