# Rays Behaving Badly No More: MoonRay 2.34.0.1 Fixes the Path

6 January 2026 - [Bela Beier](https://digitalproduction.com/author/belabeier/)

MoonRay 2.34.0.1 lands with a light path visualiser, better macOS and Linux builds, smarter lightsets, and fewer crashes for your next render night.

Three glass optics—two spherical lenses and one rectangular prism—float above a page filled with mathematical equations and diagrams. The lenses reflect a hint of greenery, while the text is displayed clearly beneath them.

*For those who don’t know the tool: [MoonRay](https://docs.openmoonray.org?utm_source=digitalproduction.com&utm_medium=referral&utm_campaign=ongoing) is [DreamWorks Animation](https://www.dreamworks.com/?utm_source=digitalproduction.com&utm_medium=referral&utm_campaign=ongoing)’s in-house [Monte Carlo path tracer](https://graphics.stanford.edu/courses/cs348b-01/course29.hanrahan.pdf?utm_source=digitalproduction.com&utm_medium=referral&utm_campaign=ongoing), open-sourced in 2023 under Apache 2.0. It drives DreamWorks’ film rendering pipeline and supports hybrid CPU/GPU (XPU) modes. MoonRay integrates with DCCs via its Hydra delegate (hdMoonRay) for tools such as [Houdini](https://digitalproduction.com/tag/houdini/) and Katana. The project includes the Arras framework for distributed rendering and collaboration across clusters.*

### Light Path Visualiser Enters the Scene

The new light path visualiser in *moonray_gui* is the most visible change in version 2.34.0.1. It lets artists trace how rays travel through a scene, showing how light interacts with surfaces, volumes, and materials. The visualisation is colour-coded by ray type and can reveal sampling or shading inconsistencies that are otherwise invisible. It also serves as a diagnostic tool for debugging light source or material behaviour.

### Platform Updates: macOS Tahoe Joins, Linux Builds Simplified

MoonRay can now build natively on macOS Tahoe, with Sonoma and Sequoia still supported. The renderer also benefits from dependency updates and inculde fixes, easing compilation on a broader range of Linux distributions. The release aligns with both VFX Reference Platform 2024 and 2025, ensuring compatibility with current production libraries and compilers.

### New Features Across the Pipeline

Version 2.34.0.1 expands flexibility for lighting and shading setups. Per-lobe lightsets are now available in both vector and XPU modes, allowing finer control of multi-lobe BSDFs. Image maps gain bindable “scale” and “offset” attributes, and SceneVariables documentation for image sizing has been clarified. Performance-wise, MoonRay now shares CPU and memory affinity data between processes using shared memory, improving parallel job efficiency. Timing measurements have switched to a more efficient RDTSC-based method for NUMA \[non-uniform memory access\] systems, offering more stable profiling results. Artists can also now select lights and cameras for object-space transformations directly in map shaders, simplifying custom shading graph workflows.

### Fixes: From Subsurface Scatter to Fisheye Crashes

A long list of bug fixes makes this release notably production-friendly. Key repairs include:

- Fixed a **mesh tessellation issue** in tiled renders with the *FisheyeCamera*.
- Resolved **DwaTwoSidedMaterial** artefacts caused by previous lobe lightset work.
- Corrected **crashes** when exceeding BSDF lobe limits or loading oversized *MeshLights*, which now trigger warnings instead.
- Addressed a **memory usage spike** in vector and XPU modes.
- Fixed **missing lightset assignments** in vector subsurface scattering and adjusted over-bright subsurface shading on creases.
- Corrected **normal direction errors** in scalar mode and improved **TransformSpaceMap** behaviour.
- Fixed adaptive light sampling, volume bounce contributions, and a crash in **OpenImageIO 2.4.8** statistics when no images were opened.

### Under the Hood: Clean-Up and Refactoring

DreamWorks also restructured several internal libraries. The noise library moved from *moonshine/lib/common* to *moonray/lib/common*, simplifying dependencies. The integrator logic for Cryptomatte was reduced in complexity, and redundant intersection path types were removed. Code clean-up continues across *lib/rendering/shading*, improving maintainability without changing behaviour.

### Availability

[MoonRay 2.34.0.1](https://openmoonray.org?utm_source=digitalproduction.com&utm_medium=referral&utm_campaign=ongoing) is available now as open-source via the [official repository](https://github.com/dreamworksanimation/openmoonray/releases?utm_source=digitalproduction.com&utm_medium=referral&utm_campaign=ongoing). It can be compiled for Linux and macOS (Tahoe, Sonoma, and Sequoia). GPU rendering requires NVIDIA CUDA/OptiX or Apple Silicon.

### Caution Before Production

As with any open-source renderer update, production users should validate the build and test scene compatibility before deployment in live pipelines.

#### Topics

- [Lighting181 postsSet the mood before anyone says a word. Explore digital lighting, scene illumination and practical approaches to guiding the eye, shaping depth and making an image feel deliberately lit.](https://digitalproduction.com/tag/lighting/)
- [Rendering891 postsThe scene is ready; now the pixels have work to do. Follow rendering engines, optimisation and production workflows that balance image quality, iteration speed and the available computing budget.](https://digitalproduction.com/tag/rendering/)
- [SideFX Houdini360 postsBuild the recipe, then see what it can cook. Explore Houdini’s procedural workflows, simulations and effects techniques, where interconnected operations turn creative rules into detailed, adjustable production assets and shots.](https://digitalproduction.com/tag/sidefx-houdini/)

#### Article details

Published

6 January 2026, 08:00:00 CET (+01:00)

Author

[Bela Beier](https://digitalproduction.com/author/belabeier/)

Reading time

About 3 min

Word count

540

#### Tags

- [array (3)](https://digitalproduction.com/tag/array/)
- [debug (2)](https://digitalproduction.com/tag/debug/)
- [DreamWorks Animation (30)](https://digitalproduction.com/tag/dreamworks-animation/)
- [Foundry Katana (32)](https://digitalproduction.com/tag/foundry-katana/)
- [GPU (204)](https://digitalproduction.com/tag/gpu/)
- [Graphics Processing Unit (204)](https://digitalproduction.com/tag/graphics-processing-unit/)
- [Hydra (16)](https://digitalproduction.com/tag/hydra/)
- [Lighting (181)](https://digitalproduction.com/tag/lighting/)
- [Linux (70)](https://digitalproduction.com/tag/linux/)
- [macOS (110)](https://digitalproduction.com/tag/macos/)
- [MoonRay (4)](https://digitalproduction.com/tag/moonray/)
- [OpenMoonRay (1)](https://digitalproduction.com/tag/openmoonray/)
- [ray tracing (45)](https://digitalproduction.com/tag/ray-tracing/)
- [Renderer (100)](https://digitalproduction.com/tag/renderer/)
- [Rendering (891)](https://digitalproduction.com/tag/rendering/)
- [SideFX Houdini (360)](https://digitalproduction.com/tag/sidefx-houdini/)
- [VFX (1,440)](https://digitalproduction.com/tag/vfx/)
- [Visual Effects (1,440)](https://digitalproduction.com/tag/visual-effects/)
- [XPU (14)](https://digitalproduction.com/tag/xpu/)

#### Permalink

[https://digitalproduction.com/2026/01/06/rays-behaving-badly-no-more-moonray-2-34-0-1-fixes-the-path/](https://digitalproduction.com/2026/01/06/rays-behaving-badly-no-more-moonray-2-34-0-1-fixes-the-path/)