ReLayerOpen navigation
ReLayer support
Get back to building your interface.
Start with the focused checks below. For project-specific help, join Discord or email Ryuxin Entertainment.
Discord support
Ask integration questions and share the exact Unity version, target platform, and relevant ReLayer Console diagnostic.
Contact contact@ryuxinenter.com for support that should not be posted in a public community channel.
Common checks
Solve the usual setup issues first.
ReLayer fails closed when the toolchain, runtime backend, or output is incompatible. The Console message normally names the failing boundary.
Node.js or npm is not found+
Use Node.js ^20.19.0 or ≥22.12.0. Set RELAYER_NPM_PATH to an absolute npm or pnpm executable when Unity cannot inherit your shell path, then choose Tools/ReLayer/Restart Overlay Session.
The Windows overlay does not open+
Install the Microsoft Edge WebView2 Runtime and confirm the target is Windows x86_64. Windows ARM64 is outside the packaged first-party runtime matrix.
Play Mode shows old production UI+
Use Auto or BuiltOverlay. ReLayer fingerprints the active project source and package build inputs, then rebuilds stale production output before using it.
React controls do not receive input+
Add data-relayer-hit to the interactive surface. Transparent overlay regions intentionally remain available to Unity input.
Live Twin is waiting+
Enter Play Mode with one active ReLayer WebView. A twin opened in Edit Mode waits and attaches automatically. Use Tools/ReLayer/Live Twin/Stop before starting a fresh session if needed.
WebGL cannot load the overlay+
Use HTTPS in production, prefer one origin, and verify CORS plus CSP permissions for the overlay document, modules, styles, assets, connections, inline nonce-bearing blocks, and blob: module URLs.
Keep the full guide nearby.
The packaged ReLayer 1.1.1 User Guide includes detailed platform, bridge, broker, and integration contracts.