Process: Level Building, Playing & Packaging
This article extends on the basic primer by further explaining the concepts in the title and how to use some of the tools and best practices.
Last updated
This article extends on the basic primer by further explaining the concepts in the title and how to use some of the tools and best practices.
Last updated
You are reading an old article for Unreal Engine 4 - it should still work for Unreal Engine 5 though!
This article covers the process of a project, particularly on building, playing and packaging.
Unreal Engine provides a series of template files with various pre-sets with reliable parameters and native Unreal Engine content to start. Upon starting a New Project:
Using Blueprint, select a Template File.
Confirm the type of Template that this is and whether the starting content is appropriate for the intended experience.
Choose the target hardware: Desktop/Console or Mobile/Tablet. Unreal Engine will automatically optimise content for this choice.
Choose a quality level: Maximum or Scalable quality.
Desktop/Console experiences should target Maximum quality, while Mobile/Tablet should target Scalable quality, however if the intended experience is very dynamic and graphically intensive, consider using Scalable.
Both the target hardware and quality setting can be tweaked under [Edit > Project Settings > Target Hardware] in the future.
Begin the project with Starter Content enabled or not. Unreal Engine Starter Content consists of some basic architectural, environmental and prop assets and materials.
Choose a directory and filename (folder name) for the project. This will be the location where the project files will be created as well as the structure for the Content Browser.
[Create Project] to finalise the settings and create the project. Upon creation being finished, Unreal Engine proper will launch automatically.
Unreal Engine also has built-in resources available other than the Starter Content. For example, the basic controllable basic sky Blueprint can be found in this content.
In the Content Browser, [View Options > Show Engine Content] to enable the content.
Toggle the Sources Panel
Engine Content should now be available to browse through.
Be wary of which content source you are searching for resources from. The default Content folder is where user content is located.
To begin creating an experience, a Level needs to be created or used. If a Level has not been made available yet, do so via [RMB] in the content browser to create a level.
From here, you can add actors of geometry, lights and effects to the level, and interactive elements and actor behaviours to complete the experience.
Building is the process that forces the Engine to compile the level so that it runs properly.
Building pre-computes all static elements; the lighting data and builds light maps, navigation data and geometry data, this is done to avoid needing the Engine to waste resources dynamically calculating content that will not change.
The engine will let you know when a rebuild is required, usually after an instance of new information added or tweaked in the scene, such as a new light source, new geometry or a change in material.
When lighting is being built, the default process is to send the data off to the Cloud to render. During this time, any edits made to the lighting and materials will not be reflected, requiring another Build afterwards.
Upon errors, the Message Log will pop up automatically. (The Message Log can usually be found through [Window > Developer Tools > Message Log] )
This logger documents all errors and their possible reasons.
Playing is a concept captured in the [Play] menu in the Toolbar.
The [Play] tool, [or keybinding Alt + P] allows you to test the current level by automatically placing you in control of the camera/generating a camera.
Modes changes the default behaviour of the [Play] button, with the main modes being:
[Play in Editor] is the default Play action, automatically possessing a player.
[Simulate] plays the game without possessing a player, enabling you to debug and test from a different point of view. This can also be accessed by pressing [Shift + 1] to regain mouse control during Play in Editor and clicking [Eject].
[VR Preview] is available if a VR headset has been set up.
As a subset of Playing, if there are any errors that arise when playing your experience, it is necessary to find out where these errors may lie. This is an especially prominent process if blueprints/code is being used.
Packaging prepares your project for ease of distribution, providing a folder with an .exe that can now run outside of Unreal Engine.
[File > Package Project]
[Build Configuration > Shipping]
Enable Full Rebuild through [Packaging > Project > Check Full Rebuild]
Confirm the startup map through [Map & Modes > Default Maps > Game Default Map]
Return to [File > Package Project]
Choose the appropriate platform
Go through the Saving dialogue
This will output a project folder with a .exe file that can copied and distributed, and ran on a VR-enabled machine. This folder and its contents must be kept together.
The HTC VIVEs at MSD run on Windows Machines, this should be the chosen platform for export.
When iterating builds to the same folder, Unreal Engine by default only modifies files that have been changed. During development it is recommended to turn off full rebuild to save time, but the final project should go through a Full Rebuild to be safe.
Toggle Full Rebuild through [File > Packaging Settings > Toggle Full Rebuild]
