MeshyAI just open-sourced ThreeRT, a real-time path tracing engine built with Rust, wgpu, and a familiar Three.js-style API.
And according to the developers, it can render complex scenes at 60 FPS on an Apple M3 Max laptop.
Real-time global illumination. Reflections. Soft shadows. Emissive lighting.
No traditional shadow maps, light probes, or baked lighting.
But there's a bigger story here.
We're watching increasingly sophisticated rendering technology become accessible to smaller development teams.
WHAT IS THREERT?
ThreeRT combines a high-performance native rendering engine with TypeScript packages for scene construction and gameplay.
Instead of learning an entirely unfamiliar API, developers can describe scenes using familiar concepts from Three.js.
The actual path tracing happens in a separate Rust-based runtime.
WHAT MAKES THREERT INTERESTING?
• Real-time path tracing: simulate lighting, shadows, reflections, and indirect illumination.
• 60 FPS rendering: demonstrated in challenging scenes including Amazon Lumberyard Bistro and Beeple's Zero-Day.
• Hardware acceleration: uses GPU ray-tracing capabilities through Metal and Vulkan where supported.
• Rust + wgpu engine: combines systems-level performance with cross-platform graphics infrastructure.
• Three.js-style API: create scenes with TypeScript using familiar meshes, cameras, lights, and PBR materials.
• No light baking: emissive surfaces, indirect lighting, and reflections are calculated dynamically.
• Game runtime: includes gameplay logic, physics integration, and tools for interactive experiences.
• Open-source engine: released under the MIT license.
THE PERFORMANCE NUMBERS
In Meshy's published Bistro comparison at 1280×720:
• ThreeRT: 15.5 ms per frame, approximately 60 FPS.
• Three.js WebGPU with SSGI, SSR, and TRAA: 34.7 ms, approximately 29 FPS.
• Optimized Three.js WebGL: 15.9 ms, approximately 60 FPS.
The important difference is visual quality.
ThreeRT reports substantially lower error against an offline path-traced reference.
These are the project's own benchmarks, not independently verified results.
THERE'S AN IMPORTANT TECHNICAL DISTINCTION.
ThreeRT isn't simply a JavaScript path tracer running inside your browser.
The full path-traced experience runs in its native client using Rust and wgpu.
The same scene code can also run in a normal web browser through Three.js, using conventional rasterization.
On hardware without suitable ray-tracing support, the engine can use a software BVH fallback.
WHY DOES THIS MATTER?
For years, professional 3D packages and game engines have offered increasingly sophisticated lighting systems.
Now we're seeing smaller teams build specialized rendering engines with APIs familiar to web developers.
And given the recent progress in AI-assisted programming, I suspect we'll see even more custom renderers, game engines, and graphics pipelines.
Of course, writing a functional path tracer is one thing.
Making it fast, temporally stable, compatible with real-world assets, and reliable across hardware is another.
ThreeRT is an interesting engineering achievement, not proof that every AI coding agent can instantly reproduce a mature rendering engine.
But the direction is fascinating.
Advanced real-time rendering is becoming increasingly accessible outside traditional 3D production suites.
TRY THREERT
Official project:
https://threert.dev/
GitHub source code:
https://github.com/meshy-dev/ThreeRT
Applications and demos:
https://threert.app/
npm package:
https://www.npmjs.com/package/@threert/scene
What do you think?
Are we entering an era where every AI-assisted developer can build a custom 3D engine, or is production-grade rendering still a completely different challenge?
#ThreeRT #PathTracing #ThreeJS
YouTube / ABVX
