Search and browse the Moray docs

Troubleshooting

When something looks wrong, open the console first. Each export prints anything Moray approximated or skipped ("Moray export: ...") and the renderer prints anything it ran on the CPU instead of the GPU ("Moray render engine: ..."). On Windows use Window > Toggle System Console; on macOS and Linux, start Blender from a terminal and read that terminal. Include those lines when you contact us.

Moray is not in the Render Engine list

  • Check the Blender version: Moray needs Blender 5.2 or a newer 5.x release.
  • Check that you installed the zip for your platform (windows-x86_64, linux-x86_64 or macos-arm64). Intel Macs are not supported.
  • In Edit > Preferences > Get Extensions, check that Moray is installed and enabled.

Moray does not start on Linux

Moray needs glibc 2.34 or newer and an x86-64 CPU with AVX2. RHEL / Rocky / Alma 8 and Ubuntu 20.04 are too old. Check with ldd --version.

Renders are watermarked

  • No key is activated, or the activation could not be verified for more than 7 days. Open Edit > Preferences > Add-ons > Moray and check the licence status. Connect to the internet and check again; reconnecting restores the licence without activating again.
  • The key was refunded, or the seat was deactivated from another machine or from your account. Activate again if you still have a free seat.

Activation fails

  • Both seats are in use. Deactivate one (from the other machine, or from your account page), then try again.
  • The machine cannot reach the licence server. Check the connection, proxy and firewall, then try again.
  • Check the key was pasted in full, without spaces.

The GPU is not used

  • With Execution Mode on Auto, Moray uses the GPU only when it finds a supported one. NVIDIA GPUs must be Turing or newer; A100 / A30 and GTX 10 series and older render on the CPU.
  • Update the NVIDIA driver.
  • RTX 50 series and H100 compile the included PTX on first use, so the first render starts more slowly.
  • On Apple Silicon the GPU traces rays and the CPU shades, so Mac GPU renders gain less than NVIDIA ones.

Materials or textures look wrong

  • Node graphs are translated as closely as possible, not 1:1. Look for "Moray export: ..." lines that name an untranslated node.
  • A texture that is missing or cannot be converted renders magenta. Check the path, or run Moray menu > Force Rebuild .tx.
  • See Known limitations for what differs from Cycles.

The render looks brighter or darker than Cycles

Cycles Film Exposure is not applied: Moray's beauty is unscaled scene-linear. Apply exposure in comp or in the view transform.

Farm node errors

  • error: set MOONRAY_ROOT or REZ_MOONRAY_ROOT: set the variable on the node.
  • file outputs need a paid Moray license (MORAY_LICENSE_KEY + MORAY_LICENSE_CACHE) (Windows): set both variables, and activate on that node under the account that runs the job.
  • More in Farm rendering.