Quiet Runtime Editor
Quiet Runtime Editor is designed to build and edit levels runtime. Version 3.1
Quiet Runtime Editor is a framework project with related runtime features designed to create, save, load, and edit levels.
The editor works in two modes:
- Edit Mode – to design scenes.
- Play Mode – to play in designed scenes with your player character.
Main Feature
The core of the project is the Runtime World Outliner. In the project's current version, the World Outliner's foundation is BP_QuietTreeManager. This actor needs to be placed in the level and initializes the entire system at startup.
BP_QuietTreeManager(Manager) stores the world tree, manages the history of actions, generates the user interface, and connects all the editor's features into a single working environment. It contains SerializerComponent and HistoryCompoent. Also, the Manager keeps the Router.
Serialization
The project is based on the ability to serialize objects to JSON. This allows you to edit properties, copy, save to disk, and keep a history of actions for undo-redo.
You can serialize desired classes manually using the provided serialization pipeline.
Communications
Different editor parts are independent and communicated through an intermediary object-router. The router registers objects by request and keeps them with the Gameplay Tag key. Thus, you can pass a command or request between any two system parts without accessing them directly. Also, you can wrap any data or objects with JSON and send them through the router.
Other Features
Scene Save and Load System.
The manager saves and loads scenes into the Documents/QuietRuntimeEditor/SaveGames folder in Json-file with the WBP_SceneManager widget. Also, you can rename and delete scenes with it.
Runtime Datasmith Import – You can import udatasmith, gltf, and glb files runtime.
Runtime Actor Details (WBP_DetailsWidget) – This feature allows you to edit the serialized properties of actors.
Runtime Content Browser (WBP_QuietContentBrowser) – an important feature that allows you to add content to scenes. It grabs assets from the UserContent folder.
Runtime Material Editor (WBP_QuietMaterialEditor) – a widget for creating and editing Dynamic Materials. Users can create a dynamic material by dragging MaterialInstanceConstant from the ContentBrowser. Also, you can serialize your materials to represent their parameters as you want.
Actions History – this feature registers user actions and stores needed data for Undo-Redo to Json-file.
Runtime Transformation Gizmo allows you to edit actor transforms at runtime.
Actor Transform Tools – multiple tools to transform, align and populate actors.
Runtime Color Wheel (WBP_ColorPickerWindow) – this widget allows a user to select the desired color.
Technical Details
Features:
- Runtime World Outliner
- Runtime Actor Details
- Runtime Content Browser
- Runtime Material Editor
- Runtime Spline Editor
- Actions History
- Camera History
- Scene save and load system
- Runtime Transformation Gizmo
- Runtime Datasmith Import
- Warning Dialogs
- Runtime Color Wheel
- Asset Preview Maker
- Actor Transform Tools
- Scatter
Number of Blueprints: 128
Number of Blueprint Interfaces: 4
Number of Enums: 14
Number of Structures: 2
Number of Widget Blueprints: 99
Example Content (User Content Folder):
- Static Meshes: 67
- LODs: No
- Materials: 37
- Textures: 48
Used Plugins:
- JsonBlueprintUtilities
- BlueprintFileUtils
- EnhancedInput
- DatasmithRuntime
Input: Mouse, Keyboard
Network Replicated: No
Supported Development Platforms:
- Windows: Yes
- Mac: Yes
Important/Additional Notes:
- Runtime Editor is built exclusively on blueprints, with some limitations and non-obvious solutions.
- The Content Browser is built based on Asset Registry functions and does not work in Standalone Mode, where these functions are unavailable. However, in the packaged build, everything works well.
- Path Tracer does not work in the shipping build.
- Blueprints cannot auto-access class properties, so you have to serialize your classes with the provided serialization pipeline manually.
