I have a problem with the tutorial on creating the main menu, the menu starts working when I start the project only when I open the “MainMenuLevel” level, but I want to achieve that the main menu works when I am on the project map from the third person and not on the empty level MainMenuLevel
Hey there @DmytroNeo! The reason the Play In Editor will always start you in the map you’re currently in is to make sure you can test quickly and efficiently without going through all of your game’s startup sequences. To change this in standalone windows or the actual builds, just change the Game Default Map to the MainMenu:
However, if you want it to automatically go back to the main menu when you start the level temporarily, you’ll have to change to the main menu map in blueprints. This is not a good idea for a myriad of reasons, most specifically iteration time.
Let me know if you have any questions!
I tried to transfer the blueprint code from the MainMenuLevel level to the ThirdPersonExampleMap level, when starting the game, the Main Menu appears, I click on the start button, but nothing happens, why does it not work, because both levels are of the same type that we can create in Content Browser window
I believe what’s happening is that it is working. Looking at your script, when you hit start you load up the third person map. Since you moved the menu to that map, it just relaunches that level, and by extension relaunches the menu. This is the kind of loop we avoid by having the main menu map separate. If you really want it in the same third person map, you’ll have to just remove the menu when you hit play and give control back to the player since it’s already in your play world.
However the proper way would be to leave it in the other map and just have them separate like you did before and just set that map as the defacto starter map. It still won’t launch to it in PIE unless you’re on it, but it will launch the standalone version on the main menu.
1 Like