Skip to main content

Unreal Engine DevLog #20: Prototype UMG Menu Updates 4 & 4.1 [Free Source Code]

Welcome to yet another update on my Prototype UMG Menu system for Unreal Engine 4. As always, it's free to use for both non-commercial and commercial purposes. No attributes required. You can find the source code at: 


The official thread in the Unreal Engine forums:
https://forums.unrealengine.com/showthread.php?63037-FREE-UMG-Menu-System-Prototype-Source-Code

Anyways, if you're using it for the first time, you can go ahead and grab the source right away. But please do let me know if you encounter any bugs in v4.7.6 or higher. The rest of this post details the changes made in the latest updates. So it's more useful for people who have been using an earlier version of this menu system in their projects already. So now that's out of the way, we'll first get to the changes made as part of the Update 4. 

Update 4

1) Persistent graphics settings across multiple instances: First of all, as promised, this update brings persistent graphics settings into the mix. That means that your graphics settings once changed will be saved and retrieved in future instances of the game. You do not need to keep on changing it every time.

2) Scrollbar Bug fix: I came across a bug that prevented scrollbars from closing down when the user is moving on to other menus. Well, that has been fixed and you will not leave any scrollbars hanging after this.

Listed below are screenshots depicting the changes made to various blueprints:
  • A new blueprint 'BP_SaveSettings' derived from the SaveGame class. After creating the blueprint, just initialize the variables shown in the class along with their corresponding values. Make sure that you give the 'SaveSlotName' variable a name to recognize the save game slot as shown.
  • 'Event Init' logic in the Game Instance blueprint. Copy the entire connected logic to your project. This makes sure that the game retrieves saved settings, every time you launch the game. If there are no saved files, it will go for the default values stored in the variables as before.
  • Add a new function 'SaveSettings' within the Game Instance blueprint. This function takes care of saving the current video settings. 
  • And here comes the final part of the logic for the save system. Just call the above function from the video settings widget when the user goes back to the options menu.
  • This next piece of logic takes care of the scrollbar bug mentioned earlier in the post. Just call the 'Collapse Scrollbox' function when returning to the options menu from the video settings menu. Same blueprint network mentioned in the previous screenshot.


With that, we're at the end of changes made in Update 4. I've released a very minor 4.1 Update to fix an issue that arises when you try adding this project into other projects.

Update 4.1
  • Create a new Game Mode blueprint named 'MainMenuGameMode'. Set this as the default game mode for the Main Menu map. Now under this game mode settings, set the HUD to 'BP_MyHUD'. Make the same changes in Project Settings >> Maps and Modes as well. That's all.

Alright, so that's it. It's currently built in v4.7.6 of Unreal Engine. I have done a couple of tests in v4.8.2 and it seems to be working, but I can't confirm yet until I do more tests. So if anyone comes across any bugs, do let me know. I thought that we'll put official version numbers from now on. So this one is officially v1.41 of the Prototype UMG Menu System and we have come to the end of this post. Have a great week.

Signing off.

Popular posts from this blog

Unreal Engine 4 Tutorial: Smooth Zoom using Mouse Wheel for Top Down Template

Well, I had already written a tutorial for implementing Smooth Zoom functionality for Top Down Template. But it was based on keyboard inputs. Since most Top Down PC games use mouse wheel for zoom, I decided to make a tutorial for the same. The core logic here is the same as the one implemented by Ryan Jon for the custom camera in his RTS Community Project. If anyone's interested, they can get the code for the RTS Community Project here:

UE4 RTS Community Project

Anyways, he has replaced the default camera for the characters with a general camera since that's more ideal for developing an RTS game. Since a basic Top Down game with a single playable character does not need a separate custom camera, I decided to implement the same functionality for the default player camera in UE4's Top Down Template. So let's get down to it.

First of all we need to make a custom curve from the content browser. We will be using this curve to define the smooth camera movement while zooming …

Unreal Engine Tutorial: Create Circular Ring Material without Textures

Hi, welcome back for another tutorial. It's been quite a while since I put up a tutorial as I've been busy working on toolkits for the Marketplace. One of my earlier tutorials [link: Unit Selection Decals for RTS Games] had focused on how to create ring materials using textures, as well as using them to display unit selection decals for RTS games. However, a drawback associated with using textures was that it prevented the user from changing the inner & outer radius of the ring. And during prototyping stages of a product, it's far better to implement structures that can be changed easily from within the engine so that you don't have to create a new asset from an external package every time you need to test out a new idea. I've found this approach quite useful while working on my own products. Hence, this tutorial focuses on creating a ring material that can be adjusted both from within the material editor as well as dynamically at runtime.

Alright before we get …

Unreal Engine Diaries #11: Nav Mesh Configuration

[This episode of Unreal Engine Diaries focuses primarily on nav mesh configuration, nav areas & configuration of agent types.

Source: Unreal Engine 4 AI Support Twitch Broadcast with Mieszko: https://www.youtube.com/watch?v=7LaazCv4rB0]

1. The Recast NavMesh has a couple of attributes named 'CellSize' & 'CellHeight' under the 'Generation' section in it's details panel. Together they determine the resolution of the nav mesh & lowering these values can create more precise nav meshes. It could be especially useful when there are lot of holes in the nav mesh due to the surface properties of the terrain. However, lowering them also makes the nav mesh calculations more expensive.

2. If runtime nav mesh generation is enabled, it would be best to set the 'Tile Size' attribute of Recast NavMesh to the minimum viable amount.
3. The 'Min Region Area' parameter which can also be found under 'Generation' section of Recast NavMesh can be i…