Glossary
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 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.
Assigning a particular set of graphics to be rendered by an Engine(s) configuration. See Channel Assignment
The method employed by the RealityHub 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.
Building block for data-driven content. Components are part of the Form Builder module. See Form Builder Components
The menu lists the connected Reality Loaders. It can be reached by clicking on the Version Number. See Reality Loader
The time that RealityHub 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
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.
Type of Policy without administrative rights. Members of the Non-administrative policy cannot use User Management and Configuration modules. See Advanced User Management
User-side of the RealityHub. User operations, such as connecting two nodes, occur via the client side through RealityHub 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 RealityHub Database.
Microsoft Windows Service to run RealityHub.
Button for synchronizing the gen-lock time, and I/O systems, including tracking and Video I/O. See Launcher Interface
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
Last modified 2d ago