Renderu.com
10.3 KPosts
68.3 KFollowers
35.0 MVisits
Alex Rowan

Meshy open-sources ThreeRT, a 60 fps ray tracer for three.js

Soft
Meshy открыла исходный код ThreeRT — трассировщика лучей для three.js на 60 к/с

The Meshy team has released as open source ThreeRT, an engine with real-time path tracing. A scene in it is described the same way as in three.js. Light is computed on the graphics card's hardware ray tracing units. The engine has no shadow maps, light probes or lightmaps, and nothing about the lighting needs baking. The developers quote 60 frames per second with a moving camera and attribute that to full production scenes.

For technical artists and developers who build showcases, configurators and browser games on three.js, this is a notable change. Realistic light in such projects usually rests on baking and screen-space effects, whereas ThreeRT recomputes the lighting from scratch in every frame. Meshy calls the project a research effort.

“Write your scene the way you would write it in three.js, and ThreeRT path traces every light on your graphics card's hardware ray tracing units.”
— from the Meshy announcement

What the engine works out on its own

In the GitHub repository ThreeRT is described as a path tracer hidden behind a three.js-style API. The core is written in Rust and wgpu, while the packages for scene description and game logic are made in TypeScript. All lighting is traced:

  • shadows from every light source;
  • bounced light, that is, global illumination;
  • reflections;
  • emissive surfaces that light the room themselves.

In practice this means the following. To get a light bounce in three.js, an artist usually has to bake lightmaps, place probes and re-bake the scene after every rearrangement. In ThreeRT the lighting is calculated on every frame, so changing object positions or the time of day requires no re-baking. A minimal scene with default settings already gets sky light, soft shadows, bounced light and reflections. Light is set in physical units: the sun in the example gives 90,000 lx, and an emissive surface becomes a light source in its own right. Models can be loaded as glTF.

The authors stress that the 60 fps hold while the camera is moving, and that the image does not keep cleaning itself up gradually after the view comes to a stop. Amazon Lumberyard Bistro and Zero-Day by Beeple are taken as benchmarks. Both, according to the developers, run at that frame rate on a laptop, and the live demos were recorded on an Apple M3 Max.

The game runtime

On the project site ThreeRT is called a game runtime: scene code and game logic run inside the engine. The same scene file runs in any browser as ordinary three.js. On the engine the team built a shooter, OpenStrike.

There is also a direct comparison. The same scene is run in ThreeRT and in three.js with all of its means: shadow maps, environment map lighting and, on WebGPU, screen-space global illumination, screen-space reflections and temporal anti-aliasing. A reference frame produced by path tracing is shown alongside.

Interactive scenes have been published as well. The sculpture gallery recreates a museum hall at real scale: a scanned marble bust, two bronzes and a porcelain horse stand under a glass ceiling, with paintings from The Met's open collection on the walls. Daylight comes through the ceiling and bounces off the parquet, while in the evening the hall is lit by spots alone. In the boutique demo six products stand on podiums and shelves. The only light comes from track spots, shelf lighting and a table lamp, and the colour of the sneaker and the armchair can be switched. For product visualisers this is an example close to their work: pools of light, soft shadows and reflections in the polished floor are traced in real time. The demo packages contain sources from which a project of your own is created with a single command.

The browser versions of the demos state outright that the view in the browser is rasterised, while ThreeRT traces the same scene. The traced image is available in the engine's native client; the browser gets the raster version on three.js.

How ThreeRT differs from earlier attempts

Tracing in three.js has been tried before. The THREE.js-PathTracing-Renderer project works on top of WebGL. It delivers global illumination, reflections, refractions and caustics at 30–60 fps, and the image in it is built progressively. three-realtime-rt, published in July 2026 under an MIT licence, is built as a hybrid. Materials are drawn by the ordinary rasterisation of three.js, and only the lighting is traced: soft shadows and one light bounce with temporal denoising on WebGL2. It is plugged in by replacing a single render call.

Both projects compute rays in shaders, without the graphics card's dedicated units. ThreeRT bets on hardware ray tracing and its own native core, and for that it takes tracing out of the browser.

What is still missing

The move to a native runtime is probably linked to the fact that browser graphics APIs still have no standard access to a graphics card's RT units. So the traced image goes to whoever opens the project in the ThreeRT client; on an ordinary web page the raster version remains.

Some of the details that matter for a decision are not disclosed in the materials. The repository lists clients for macOS (Apple silicon) and iPhone/iPad, and the platform list on the site also names Steam Deck and Android, but there are no specific graphics card requirements and no data on how the load grows with the number of light sources and triangles. The company also does not explain how the research engine relates to its main line of work, 3D model generation. A scenario in which generated models are shown straight away in a traced scene remains conjecture for now.

Which approach to light in three.js is closer to you?

  • Baking lightmaps
  • Hybrid three-realtime-rt
0
Related news:
New Xbox promises ray tracing an order of magnitude faster
Emm of Scenario releases 40 animation loops for AI agents
Meshy turns any photo into a 3D relief for printing
PixiJS Adds 3D to the 2D Scene and Opens an MIT-Licensed Beta
Comments:0
post date