UI3 Game Modes

The Game Mode defines the type of interface and controls for your project.

The Game Mode can be selected in the World Properties. Each (persistent) level has its own World Properties. If you only have one level then this is the persistent level. This way you can have multiple different Game Modes in the same Project.

There are 4 Game Modes to choose from:

• SDotUI3_GameModeKeyboard for keyboard and mouse support
• SDotUI3_GameModeTouch for touch controls
• SDotUI3_GameModeGamepad for XBOX Gamepad support
• SDotUI3_GameModeVR for VR headsets with a controller or gamepad.

Read on for more details about how to use these Game Modes.

Put all your assets into sub levels if you want to use the same scene for different game modes. Then create a persistent level for each game mode and add the asset levels as sub levels. Put a copy of the UI3 Info Map in the persistent level for each game mode and make the necessary changes for the game mode. Now any changes to the scene in the sub levels will lead to all versions to be changed as those share the same sub levels.

This is the default Game Mode.

Technically this Game Mode uses the SDotUI3_CharacterV3 and the SDotUI3_ControllerKeyMouse. The Game Mode itself is empty.

You can use the defaults for anything regarding the look and functionality of the interface.

Tip: click on the little yellow arrow next to the value to set the parameter back to its default value.

Use this Game Mode for touch screen devices. Also use it if you want to Pixel Stream onto a touch screen device.

Technically this Game Mode uses the SDotUI3_CharacterV3 and the SDotUI3_ControllerTouch. The Game Mode itself is empty.

During development it might be useful to simulate the touch screen input with the mouse. You can find this setting in the Project Settings -> Input. Or use the Keyboard Game Mode during development.

To test the controls without having a touch screen input device:

Settings in the Info Map blueprint:

Use this Game Mode with a XBox gamepad controller or any other controller. Find some more info for the use of other controllers at the end of the page.

Technically this Game Mode uses the SDotUI3_CharacterV3 and the SDotUI3_ControllerGamepad. The controller blueprint contains all the blueprints to navigate the Main menu.

Settings in the Info Map blueprint:

How to use a different controller with the user interface is explained at the end of this page.

Use this Game Mode for VR scenes. You can use a XBox gamepad controller, a VIVE controller or the Oculus Rift controller by default. Find some more info for the use of other controllers at the end of the page.

Technically this Game Mode uses the SDotUI3_CharacterV3 and the SDotUI3_ControllerGamepad. The controller blueprint contains all the blueprints to navigate the Main menu. The game mode blueprint has some additional blueprints for VR to work.

Settings in the Info Map blueprint:

Once they work you have to add their buttons to the input controls in the Project Settings. Open the settings and navigate to Input by clicking on the link on the left side. Then add your controller buttons to the Bindings. This should be somewhat self explanatory.

Action Mappings are button clicks like ENTER, or shortcuts like I for a screenshot.

Axis Mappings are movement controls like player movement forward or mouse looking to the side. Anything that isn't a simple click.

Detailed information is on the Unreal Engine Documentation about Input.

Unreal Engine Documentation - Input