Default Plugins
Reality Hub enforces plugin states as locked, blocked, or left to Reality's defaults.
Plugins Forced On
Reality Hub always enables the following plugins at startup to ensure Motion Design and remote control workflows:
| Plugin | Engine Default | Forced State |
|---|---|---|
| Motion Design | Enabled ✅ | Enabled ✅ |
| Motion Design Scene State | Disabled ❌ | Enabled ✅ |
| Motion Design Scene State Integration | Disabled ❌ | Enabled ✅ |
| Storm Sync | Disabled ❌ | Enabled ✅ |
| Storm Sync Motion Design Bridge | Disabled ❌ | Enabled ✅ |
| Web Socket Messaging | Disabled ❌ | Enabled ✅ |
| Remote Control | Enabled ✅ | Enabled ✅ |
Plugins Forced Off
These plugins remain disabled to prevent conflicts with Reality Hub workflows. Even if you enable them, launching a project with Reality Hub turns them off at runtime.
| Plugin | Engine Default | Forced State |
|---|---|---|
| nDisplay | Disabled ❌ | Disabled ❌ |
| OpenXR | Disabled ❌ | Disabled ❌ |
| AJAMedia | Disabled ❌ | Disabled ❌ |
| BlackMagicMedia | Disabled ❌ | Disabled ❌ |
Plugins Left To Engine Defaults
Reality Hub does not override the following plugins. Their state follows the engine configuration that ships with your project:
| Plugin | Engine Default | Forced State |
|---|---|---|
| Nodos Link | Enabled ✅ | Enabled ✅ |
| Reality | Enabled ✅ | Enabled ✅ |
Custom Plugins
Reality Hub does not override the state of your custom plugins. Their state follows the engine configuration that ships with your project.