How should the menu of a Unity project be structured?

[MiguelAppStudio]

Hello, I hope you can help me.
I am trying to create a project with several mini games that I have been creating in tutorials and some open source to fill.
I have some doubt. Each mini game has its own scene, some even multiple scenes.
I have created a scene for the main menu, which takes me to each of the games.
The question is:
1 - yes, within the main menu, I must create other menus with the settings of all the games, that is, create as many settings menus, as there are games in the App

2 - I must create a scene in each game to create the settings and options.

Which option is the one that will give more fluidity to the App, option 1 or option 2?

Or is there another way to do it other than these?
Thank you

[Kurt-Dekker]

Additive scene loading is one possible solution:

Right way for performance, divide scene?

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 …

Right way for performance, divide scene?

Glad you asked… going this route definitely requires slightly-higher awareness of what scene is what. In no particular order, responding to you questions, When the game or level is over, I try to go to a fresh “end level” scene (not additively!) and clear everything else out (except overall ongoing game manager obviously, as a singleton) when the game gets paused I stop time and bring up a pause scene that sorts above all else, then unload it and restart the time. OR if you quit, I just …

Problem with canvas & UI prefabs

There are underlying reasons this happened and you can track it down by examining everything about each scene’s canvas setup and scaling that are different from the other. But keep in mind it might not be super-easily to address it in the general case, especially if you start partitioning your UI into chunks. An alternate workflow is to put chunks of your UI into separate scenes and then load those scenes additively. For instance you might have the following scenes, all loaded additively: c…

A multi-scene loader thingy:

Unity additive scene loading example - Pastebin.com

My typical Scene Loader:

https://gist.github.com/kurtdekker/862da3bc22ee13aff61a7606ece6fdd3

Other notes on additive scene loading:

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…

Timing of scene loading:

Function called from preloader script doesn't change parent of gameobject (in the second scene)

If line 8 relies on something being present from the scene load in line 7 (in GameController), it won't be: scenes are loaded at the end of frame and would never be available until the next frame, at the very earliest. You can trivially make void Start() into a coroutine by declaring it to return an IEnumerator, then put a while loop (with a yield return null; in it!!!) to wait until the scene loads and you find the "Trains" object, then proceed. Obviously you would need to interlock other t…

Also, if something exists only in one scene, DO NOT MAKE A PREFAB out of it. It’s a waste of time and needlessly splits your work between two files, the prefab and the scene, leading to many possible errors and edge cases.

Two similar examples of checking if everything is ready to go:

Daily Events and content changes

I think multiple scenes are definitely worth chasing. You need to make everything in your game tolerant of perhaps not having stuff ready at the same time, and you have to track things that you need only ONE of: Camera (Main) Audio Listener EventSystem I like to put all of those in the BASE scene if possible, then load other scenes like UI and pause and the level itself, etc. You have to sort of figure out which works for you. You can actually make Start() be a coroutine too, such as lookin…

Unit scripts calling Start function before other scripts

Indeed. I like to use a lot of additively-loaded scenes, so I tend to code my individual item controllers (including the player controller) so that they are happy to wait around if other stuff isn’t ready yet. You can make Start() into a coroutine, which is a super-easy way to get this kind of lazy-sloppy startup that is extremely tolerant of late loading and uneven loading. // typical base framework for all entities bool ready; IEnumerator Start () { // don't proceed unt…

[Cornysam]

If i understand properly, I think you kinda want an approach like option 1. I would say have a MenuManager that is set to DontDestroyOnLoad and persists over all scenes. You can then tell the MenuManager what scene/mini-game is active and then enable/disable them accordingly. You will need a menu for each mini-game it seems.

[MiguelAppStudio]

@Kurt-Dekker

Additive scene loading is one possible solution:

https://discussions.unity.com/t/820920/2
https://discussions.unity.com/t/820920/4

https://discussions.unity.com/t/824447/2

A multi-scene loader thingy:

https://pastebin.com/Vecczt5Q

My typical Scene Loader:

https://gist.github.com/kurtdekker/862da3bc22ee13aff61a7606ece6fdd3

Other notes on additive scene loading:

https://discussions.unity.com/t/805654/2

Timing of scene loading:

https://discussions.unity.com/t/813922/2

Also, if something exists only in one scene, DO NOT MAKE A PREFAB out of it. It’s a waste of time and needlessly splits your work between two files, the prefab and the scene, leading to many possible errors and edge cases.

Two similar examples of checking if everything is ready to go:

https://discussions.unity.com/t/840487/10

https://discussions.unity.com/t/851480/4

Thanks for sharing your knowledge with us, it’s amazing.
Your explanation really seems incredible to me with all these data that you have shown.
You certainly know exactly what you are talking about.
I think I understand, after reviewing all your links (tomorrow I will review everything again), that the most correct thing is to put each menu in an individual scene.
I have seen your SceneHelper.cs files, but I don’t know how to use it in my project, I have little experience.
I’m trying to learn and the things I’ve created so far have been following online courses
I will find another way to navigate between the scenes of the game.
Thanks for your explanation, you have been very helpful.
From today, I will follow in your footsteps, I think you are a person who knows a lot about Unity.
Thank you