Skip to main content
Version: Reality 5.7

Upgrading From 5.6 to 5.7

Reality 5.7 introduces impactful changes you have to consider:

  • All existing user-linked API Keys are deleted during the migration to the standalone API Key system. You must recreate API Keys after migration. Please read REST API Key Authentication System.
  • A new Engine Ownership system is introduced. Engines are now owned by the Hub that starts and manages them. Engines that are not owned by the current Hub cannot be edited or controlled from the UI. You may notice previously-editable engines become locked (N/A or Idle) if they are managed or started by another Hub or if their loader is disconnected. This is expected behavior and part of enforcing correct ownership.
  • Engine Groups removed from Configuration and Launcher modules. Aliases are now superseding Engine Groups. For more details, read Logical Channels Using Aliases
  • Legacy Configuration Host ports are automatically updated to new default port 50052 during installation. The host port setting has been renamed to "Nodos Port" with validation to prevent conflicts with reserved Motion Design ports (30010, 30020, 30030). Also read Firewall Configuration.
  • Reality Hub now enforces plugin states as locked, blocked, or left to Reality's defaults. For more details, please read Default Plugins.
  • Enable Launch for Unreal Engine checkbox is removed since the Unreal Engine Vanilla is no longer supported.
  • Hardware Acceleration in ReadVideo node is disabled by default. You may need to enable it if needed.
  • MDRender and MDRender.UHD licenses introduced for Motion Design channels. Motion Design Preview Channels below 1024x576 do not require a license.
  • All Reality Editor projects now use Arial Unicode MS for broader multilingual character support (Latin, Cyrillic, Greek, Arabic, Hebrew, Asian, and regional scripts).
  • REST API is accessible without a specific REST API license.
  • Text 3D components used within a Blueprint may fail to render in the viewport after saving and reopening the project when attached to the Default Scene Root. Workaround: Replace Default Scene Root with a custom Scene Component.