Concepts are fundamental to understanding complex abstract subjects. This section aims to provide a glossary to keep you across the Reality Hub features and its approach to control systems.
Part of a toolset for animating properties, calling, and triggering functions. See Actions
Any object can be placed into a level, such as a Camera and static mesh. See Spawning Reality Actor
Also known as Administrative Rights, it refers to an admin username and password of an Engine that Reality Hub Server is connecting.
User who is capable of governing other users except for the Admin. See The Admin
Displaying interface for previewing an Engine scene. See APM
The file directory contains a project cache. The default project cache is located in the C:\cache
Locally stored Project files.
See Nodegraph Canvas
Assigning a particular set of graphics to be rendered by an Engine(s) configuration. See Channel Assignment
The method employed by the Reality Hub documentation can help you distinguish various entities such as nodes, property groups, etc. See How to Read this Documentation
Also known as cmd.exe or cmd, is the default command-line interpreter for Microsoft Windows.
Free-to-download version of Reality Hub. See FAQ
Building block for data-driven content. Components are part of the Form Builder module. See Form Builder Components
Engine Launch mode with no operation restrictions. See Launcher Interface
The menu lists the connected Reality Loaders. It can be reached by clicking on the Version Number. See Reality Loader
Storing contents and assets in platform-specific format particular formats. See Cook Manager
A file directory for installing and storing Reality Hub Database. See Installation
Collective name of the Database Username, Database Password, and Database Name. See Installation
A feature allows the internal behavior of the node to be investigated. See Node Structure
The time that Reality Hub waits between ping packets. It is measured in seconds. See General Engine Configuration
The duration that RealityHub waits for a response from your Engine before identifying changes.
Supported Engine type & version. It refers to the Engine selection operation in the Renderer section of the Launcher module. See Launcher
Also known as exposing a parameter, the operation that allows suitable Engine elements (such as parameter, function, property, etc.) to be accessible by RealityHub.
Set of management tools for Form Builder elements such as Form Builder Components. Every Form Builder entity has Field Settings.
Also known as a search filter, a tool for refining the search results of a particular module.
Standard designated port for establishing communication between RealityHub Server and Reality Loader.
A feature provides input to various nodes to control them in a three-dimensional space. See Node Structure
Nodegraph operations for multi-Engine configurations. See Gang Mode
The Engine that hosts Projects.
Windows computer name of the Engine you want to reach and control via RealityHub.
The IP address RealityHub listens. See Installation
The Port RealityHub Server accepts connections.
File path where the Engine is installed.
Engine Launch mode with various operational restrictions. See Launcher Interface
License type related to version upgrading within a certain period of time. See Licensing
Policies, and User and User Groups sections of the Advanced User Management Module.
Main units of the RealityHub.
Act of previewing Engine scene. See APM
A node is an object, such as an event, function call, flow control operation, variable, etc. to define the functionality of the particular blueprint that contains it. See Node Structure
A virtual board for conducting nodegraph operations. See Nodegraph
Set of RGraphs shipped with RealityHub.
Two or more connected Nodes. See Operating Nodegraph
Type of Policy without administrative rights. Members of the Non-administrative policy cannot use User Management and Configuration modules. See Advanced User Management
A template form inside the Playout module. See Form Builder & Playout
Set of rules for module/user feature accessibility. Advanced User Management
An application allows you to connect Reality Hub Server to Engines. See Reality Loader
User-side of the Reality Hub. User operations, such as connecting two nodes, occur via the client side through Reality Hub User Interface.
Organized collection of structured information stored in the dbdata folder, contains RGraphs, Actions, etc. See Database Backup and Restore
Microsoft Windows Service to run Reality Hub Database.
Microsoft Windows Service to run Reality Hub.
HTTP IP Address and Port for communication with Reality Hub Server. See Reality Loader
Engine configuration for rendering the Project. See Launcher
Button for synchronizing the gen-lock time, and I/O systems, including tracking and Video I/O. See Launcher Interface
Logic-based pipelines consist of node trees. See RGraph
Network drive that all Engines can read/write derived data. See General Engine Configuration
File path contains the Project that is accessible with Reality Hub for launching. See Launcher
Engine status color indicators. See Status Colors & RealityEngine AMPERE Led Display
A unique ID of the system. It must be delivered to the Licensing Team for any inquiry. See Licensing
The first & default user. It is created during the installation. See Role of the Admin and Administrators
State of an exposed parameter inside the RealityHub. See Controlling Unreal Engine & UState
