Concepts are fundamental to understanding complex abstract subjects. This section aims to provide a glossary to keep you across the RealityHub features and its approach to control systems.
Any object that can be placed into a level, such as a Camera, and static mesh.
Also known as Administrative Rights, it refers to an admin username and password of an Engine that RealityHub Server is connecting.
The file directory contains a project cache. The default project cache is located in the C:\cache
Locally stored Project files.
Also known as cmd.exe or cmd, is the default command-line interpreter for Microsoft Windows.
The duration that RealityHub waits for a response from your Engine before identifying changes.
Also known as exposing a parameter, the operation that allows suitable Engine elements (such as parameter, function, property, etc.) to be accessible by RealityHub.
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.
The Engine that hosts Projects.
Windows computer name of the Engine you want to reach and control via RealityHub.
The Port RealityHub Server accepts connections.
File path where the Engine is installed.
Main units of the RealityHub.
A node is an object such as an event, function call, flow control operation, variable, etc. that can be used in the RGraph to define the functionality of the particular blueprint that contains it. See Node Structure
Set of RGraphs shipped with RealityHub.
User-side of the RealityHub. User operations (such as connecting two nodes) occur via the client side through RealityHub User Interface.
Microsoft Windows Service to run RealityHub Database.
Microsoft Windows Service to run RealityHub.
Engine status color indicators. See Status Colors & RealityEngine AMPERE Led Display