Understanding Reality Hub UI Warnings

UI warnings are intended to inform you of potential issues or unexpected situations you may encounter during your interaction with Reality Hub.

These messages can include error messages, such as 'Failed to retrieve system FPS,' or informative messages, such as 'Your session has been terminated by the administrator.

Community Edition supports only localhost

If you're using the Community Edition of Reality Hub, your license permits you to utilize only your local computer setup.

In this version, all components of your Reality Suite (including the Reality Engine, Reality Hub Server, Reality Hub Client, and Zero Density Licensing) are located within the same computer.

As a result, it's not possible to control another Engine on your network or using multiple engines.

Failed to delete <cache name> from the cache

If you encounter this warning, it's advisable to verify your administrative credentials for the storage where the cache is located and confirm that it's not being utilized by another project.

Additionally, please refer to the Cache Management and Shared DDC sections for more guidance.

Failed to obtain <license name> license

If you come across this warning, it's recommended to refresh the Reality Hub page. If the issue persists, reach out to your administrator to ensure that your user management settings allow access to the license for your account.

Additionally, please explore the Advanced User Management section for further assistance.

Failed to retrieve path source

If you see the warning "Failed to retrieve path source," it could signal an incorrect path, a missing file or folder, or permission problems.

Here's what you can do in such a situation:

  • Check the path again to ensure its accuracy.

  • Confirm the existence of the file or folder you're trying to access.

  • Make sure you have the required permissions to read or access them.

Failed to retrieve project sources

if you encounter the warning "Failed to retrieve project sources," it could indicate missing or corrupted project files, network issues, or permission problems.

Here's what you can do in this case:

  • Double-check that the project folder is where it's supposed to be and hasn't been relocated or deleted.

  • Inspect the project folder for any corrupted files.

  • Ensure a stable network connection.

  • Verify that you have the necessary permissions to access both the project folder and its files.

Reserved names "Live" or "Live |" cannot be used

You can't use the reserved names "Live" or "Live |" for saving RGraphs and UStates. Currently in use RGraphs and UStates have unique names starts with Live until they're saved. So, avoid using these names when saving your RGraphs and UStates.

Selected engine is in-use

If you encounter this warning, it indicates that the Engine you are attempting to add to Renderers is currently busy. To use that specific engine, you must first stop it. Please also visit Launcher section for more information.

Selected group has in-use engine(s)

If you come across this warning, it means that the Engine group you're trying to launch currently has one or more engines in operation.

To utilize the engine groups, you need to stop the engines that are currently unavailable in the group. Additionally, please refer to the Grouping section for further information.

Your session is terminated by <user name>

An individual in your organization with administrative privileges has ended your active session. If you encounter this warning, you can contact with your admin. See also Advanced User Management for detailed information.

Failed to parse JXD file

If you encounter the warning 'Failed to parse JXD file,' it indicates that Reality Hub encountered an issue while attempting to interpret the structure and content of a file.

This error may indicate:

  • The JXD file itself could be corrupted or damaged, preventing Reality Hub from interpreting its contents correctly.

  • The JXD file might contain errors in its structure or syntax, such as missing commas, brackets, or improper use of quotes.

Here are the steps you can take:

  • Verify the integrity of the file by obtaining the JXD file again from the original source. Downloading errors can sometimes corrupt files. If the file was created elsewhere, ensure it was saved properly and hasn't been accidentally modified.

  • Validate the file format using a JSON validator tool to check if the JXD file adheres to the correct JSON format. If errors are identified, correct the formatting mistakes in the JXD file using a text editor.

If the error persists, do not hesitate to reach our Support Department.

Last updated