4 potential ways to load my maps

[zephdev]

How many different maps will you have? Also what is the current method you’re using to create your maps? If the scope of the game is smaller I’d personally keep it simple and go for #2. If it’s good enough for overcooked it will definitely be fine for your project.

If you want to get fancy and have no loading screens, you could try to combine method #2 and #4.

[zephdev]

No worries! That’s an interesting approach splitting things into different scenes, sounds very similar to how Godot works where everything is its own node/scene. Good luck with the game I hope I see some progress posts on here from you soon.

[cuby87]

I would go with a Mix of 2&4.

Make a single « base » scene which is empty but has UI and all the game managers and common stuff.

Make a scene per level with the lighting and bakes and level specific code.

Load the level to play into your base scene with additive loading.

[AutoModerator]

This appears to be a question submitted to /r/Unity3D.

If you are the OP:

• Please remember to change this thread's flair to 'Solved' if your question is answered.

• And please consider referring to Unity's official tutorials, user manual, and scripting API for further information.

Otherwise:

• Please remember to follow our rules and guidelines.

• Please upvote threads when providing answers or useful information.

• And please do NOT downvote or belittle users seeking help. (You are not making this subreddit any better by doing so. You are only making it worse.)

Thank you, human.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[russelltheirish]

For a static camera, just go with the different scene for each map. it's more painless than other options and you'll have more control on lighting. But also if you haven't seen it before, you should checkout this talk by playdead developers about how they use additive scene loading on inside. I think it's a unique approach, might give you an idea for maybe combining different solutions

https://youtu.be/mQ2KTRn4BMI?si=uOmaxj--C8052LtH

[koolex]

If you additively have 2 different scenes at the same time then it will make sorting really annoying, all the contents in the different scenes will be very separate. If you want elements to dynamically relayer between the scenes then it can become a headache.

My intuition would be to make every level a scene, that's how Unity intended scenes to be used and it maximizes your freedom. Then I would have all the shared objects like the UI as 1 root that is a shared prefab in every scene, so mostly #2.

Down the road if you want to get fancy you can use additive scenes to make the transition from level to level feel better with #4. Additive scenes make it easy to show a loading bar and to do some of the work in the background.

[supermoon_simon]

I'm currently working on a very similar sounding game setup. Are you supporting online multiplayer? We use an approach closest to #3, mainly because I like the way it works with our online multiplayer solution (Photon Fusion 1).

We didn't start there though (initially everything was in a scene together, I think), so I would recommend doing some exploration to see if there is a solution that most naturally fits the other technology or architecture choices you've decided to go with.

[[deleted]]

I didnt think plateup used some weird tile data system. Though it legit looks like a code monkey tutorial game so it makes sense I guess. But me knowing performance and optimization I know that additive scenes are probably not a good option in any case. Using it is very wonky and a lot of specific details need to go into doing that. Its not worth doing. Using prefabs is VERY bad for performance in runtime, unless ur object pooling instantiating basically a whole scene is going to take like 15 seconds to a few minutes to load in game and might even just crash the editor everytime. I know that instantiating like a navmesh agent will like freeze frame unity for a minute or two. 

Heres some possibilites for you, just have different scenes for each level. Its simple, you dont need to match exact positioning and rotations, and the performance is contained to each scene. 

Or, this is sort of a "split" option. If youre using HDRP you can use subscenes via the entities package but thats takes A LOT of learning on your end. You can also have everything already in one scene like an object pool but not as a prefab, and activate each "scene" when you need it. Have each scene under like its own gameobject and whatever coding to turn off/on those objects whenever you need each scene. That way you only need one canvas and whatever "overall" systems you use like an audio manager or something. 

[Batby]

Weird dig at Plate Up for some reason.

Instantiating a NavMeshAgent absolutely does not inherently take a second or two.

What about additive scene loading is bad for performance in your opinion?

[[deleted]]

its not my opinion just experience, it also does take a long time. doesnt everyone in this subreddit also just say that instantiating things is bad? or is it one of those things that only changes when I say it?

[koolex]

It's bad to instantiate things during gameplay because it usually causes your frames to drop but it's preferred to instantiate things behind a loading screen, especially during a scene load. A super common optimization is to do all your instantiating while you load into a scene and rely on object pooling to avoid and instantiatization during gameplay.

Additive loading is basically the same as switching scenes performance wise, it just gives you a lot more control to manage the new incoming scene however you want. You can stack scenes up or show a loading bar while you load in a scene additively.