Should i separate my main menu screen Widgets to a new level before starting the game? or should i just put them together in one Level?
which is Better / efficient / smoother ?
There is no “better” there is only “better for your particular use case.”
If you want the main level to be a background for your main menu, and clicking “start” in the main menu to simply fade out the menu overlay and bring the main level in focus, then your main menu should be a widget in the regular game level. You could also prevent the player controller from possessing a pawn initially, and spawn/possess the pawn once the menu is exited.
On the other hand, if you want the main level to load “from scratch” and “begin play” to mean that actual gameplay begins, you’ll want the main menu to be a different level. Similarly, if you have many different maps/levels, and don’t know which one the player will start with, choosing one as the background just likely means you’ll load another one when starting the game anyway.
So, personally, I prefer the “main menu is a different level” approach, but there’s no “right” or “wrong” only “what fits better with what you want to do.”
1 Like
yes, i like that too!
I guess I’ll go and separate my menu screen, also i was thinking to add graphics settings,
so, if I set the graphics first to low in menu screen, then the main level will load faster? or just the same?
one important reason to handle your main menu on a separate level, is it will help with GC. iv had issues in the past where a menu wouldn’t GC properly, and only when i changed over to a new level would the memory be freed.
1 Like
Not really – graphics quality is more about frame rate once loaded; most of the data is still loaded (especially for something that’s menu-only)
Most of an Unreal Engine program start-up time is loading and preparing the engine itself.
1 Like