Right way for performance, divide scene?

[Kurt-Dekker]

I always favor breaking the scenes up and loading additively.

• reduces overall memory consumption

• lets multiple team members trample on each other less often

• ensures clean “reset” of all objects in a fresh loaded scene

I’m working on a game now where we each have our own “content” level, the level we’re working on.

the content scene has all the lighting baked in.

Just press play and that level has one script that additively loads:

• music scene (just an audiosource on autoplay)
• the player scene (With controls and camera)
• UI overlay (score)
• pause button (could have been merged with UI overlay) <— the only one with an EventSystem.

It’s glorious. First thing the additive loader does is load a black “Loading” screen prefab while it additively loads all the others. We don’t do the loading screen as a scene because scenes always load the NEXT frame, so we would get a flash of our level when we first load it, but now it’s black until all is loaded.

Super slick, no fuss no muss.

If we want to extend in the future, all we need to do is download a fresh scene asset bundle and it’s done.

Here’s what we’re doing:

Unity additive scene loading example - Pastebin.com

Here’s a related post I wrote as well about it:

Removing Duplicates on Load Scene

Why not remove the player from ALL your scenes, put him in his own separate scene, then load scenes additively? That way you don’t even need a Player prefab at all, just have a Player scene and load him additively. I tend to break up all my games into partial scenes, all additively loaded by the game manager: UI player enemy manager other stuff? and then finally I load the content scene. The first batch of screens all have scripts that do nothing until the content scene appears and they kn…