Godot Ray Tracing: The NVIDIA RTX Fork

A fork, not a feature

At GDC 2026, NVIDIA released a path tracing fork of the Godot engine . This is not a plugin you drop into your project. It is a modified version of Godot itself , hosted under NVIDIA’s GitHub organization and released under the MIT license.

The fork required low-level rendering changes  that could not be done as an addon within Godot’s current architecture. NVIDIA modified the rendering pipeline to replace rasterization with full path tracing, which means every pixel in the scene is computed by simulating actual light bounces rather than using screen-space approximations.

80.lv covered the launch , and the Godot community response on the forums has been a mix of excitement and realistic caution.

The path tracer itself uses the Vulkan API, making it technically GPU-agnostic . Any GPU with Vulkan ray tracing extensions could theoretically run the path tracer. But there is a catch: the denoiser currently uses DLSS Ray Reconstruction, which is NVIDIA-only . Path-traced images are extremely noisy at real-time frame rates. Without a denoiser, you get a grainy mess. So in practice, you need an NVIDIA RTX card right now.

AMD and Intel denoiser support is in development according to NVIDIA , but there is no timeline.

How this actually works

Traditional game rendering uses rasterization: project every triangle onto the screen, then fake lighting with a stack of tricks (shadow maps, screen-space reflections, ambient occlusion probes). It is fast and looks good enough for most games. Every Godot game you have played uses this approach.

Path tracing flips the model. Instead of projecting geometry to pixels, you shoot rays from the camera into the scene and simulate how light actually bounces between surfaces. Reflections are physically accurate. Soft shadows happen automatically. Global illumination is a natural result, not a separate system you have to tune.

The tradeoff is brutal on performance. A single path-traced frame might need thousands of rays per pixel to converge to a clean image. Real-time path tracing is only possible because modern GPUs have dedicated RT cores that accelerate ray-scene intersection tests, and because AI-based denoisers can reconstruct a clean image from a noisy one rendered with far fewer samples.

Most shipped games that advertise “ray tracing” actually use a hybrid approach: rasterize most of the scene, then use RT for specific effects like reflections or shadows. The NVIDIA Godot fork goes further with full path tracing, where the entire image is ray-traced. This is the same approach used in NVIDIA’s RTX Remix for classic game mods .

NVIDIA’s fork and Godot’s native RT work

Here is what makes the current situation interesting: there are two separate efforts to bring ray tracing to Godot, and they are happening in parallel.

NVIDIA’s fork is the one that gets the headlines. It is a working path tracer you can build and run today. NVIDIA has stated their intention to merge this back into mainline Godot via PR, or alternatively make it available as an addon . Neither has happened yet.

Godot’s native work is quieter but arguably more important long-term. Godot 4.7 dev 1 added initial Vulkan ray tracing plumbing  by contributor Antonio Caggiano. This is foundational work: setting up the Vulkan ray tracing extensions, acceleration structures, and pipeline objects that future RT features would build on. It is not a path tracer. It is the infrastructure that could support one.

The best outcome is convergence: NVIDIA’s path tracer gets refined, the Godot core team reviews and adapts the rendering changes, and some version of RT support lands in mainline Godot. Whether that happens as a merged PR or an official GDExtension addon remains to be seen.

Honestly? Not much yet.

If you are building a 2D platformer, a roguelike, or even a stylized 3D game, this changes nothing about your workflow today. And that is okay.

Path tracing is a AAA rendering technique. It demands a high-end GPU from your players, it limits your audience to desktop, and it solves a problem (photorealistic lighting) that most indie games do not have. The games driving Godot’s growth on Steam, which doubled yearly to 2,864 titles in the 2025-26 period , are almost entirely games that look great with rasterization.

But the trajectory matters more than the current state. Here is why:

Credibility. When studios evaluate Godot for 3D projects, “does it support ray tracing?” is a checkbox question. The answer used to be a flat no. Now it is “NVIDIA built a working implementation, and native support is in development.” That shifts conversations.

Future-proofing. Hardware moves fast. RT cores are in laptop GPUs now. In three to four years, the GPU floor for consumers will include capable RT hardware. Having the rendering infrastructure ready before that happens is the right timing.

Developer mindshare. Search interest for “godot rtx” grew +950% year-over-year . That is from a small base (30 searches/month), but it signals that developers are asking the question. “Godot ray tracing” sits at 70 monthly searches with +57% growth . The curiosity is there.

What you need to run this

The NVIDIA fork requires a GPU with Vulkan ray tracing extensions. In practice, that means:

• NVIDIA: RTX 2060 or newer (Turing architecture and up). The denoiser requires DLSS, so RTX is mandatory on the NVIDIA side.
• AMD: RDNA 2 or newer (RX 6000 series and up) have Vulkan RT support. The path tracer should run, but without DLSS Ray Reconstruction, the output will be noisy. AMD denoiser support is planned but not available.
• Intel: Arc GPUs support Vulkan RT. Same denoiser limitation as AMD.

For reference, path tracing is expensive. Even NVIDIA’s own RTX Remix targets 30-60 FPS at 1080p on an RTX 4070 for remastered classic games. A complex Godot scene with path tracing will push hardware hard. This is not something you ship to players with minimum-spec GTX 1060s.

Unreal has had this for years

Let’s be direct: Unreal Engine has supported ray tracing since version 4.22 in 2019 . Lumen, Unreal 5’s global illumination system, uses a hybrid approach with software and hardware ray tracing. Fortnite runs Lumen on consoles. This is production-proven technology.

Godot is not competing with Unreal on photorealistic rendering, and it should not try. If your project needs Lumen-quality global illumination, Nanite-level geometry, and MetaHuman character fidelity, Unreal is the right engine.

What the NVIDIA fork demonstrates is that Godot’s Vulkan renderer is flexible enough to support path tracing at all. For an open-source engine that was primarily 2D-focused five years ago, that is significant. Godot 4.6 already brought Jolt Physics as the default and overhauled screen-space reflections , and the 3D pipeline keeps improving with each release.

The gap with Unreal on high-end rendering is still wide. But it is narrowing, and the NVIDIA fork proves the architecture can support it.

The signal is bigger than the feature

Even if 95% of Godot developers never touch path tracing, this fork matters for three reasons:

NVIDIA is investing engineering resources in Godot. This is not a weekend hack. Building a path tracer that integrates with Godot’s rendering pipeline, scene system, and material model is serious work. NVIDIA choosing to do this signals that they see Godot as a platform worth supporting.

It validates Godot’s architecture. The fact that NVIDIA could build this as a fork (rather than requiring a ground-up rewrite) suggests that Godot’s Vulkan renderer is well-structured enough to support advanced rendering techniques. That bodes well for future graphics features.

It gives the Godot rendering team a reference implementation. Even if the NVIDIA fork never merges directly, the core team can study the approach, identify which architectural changes are needed, and incorporate lessons into the native RT work happening in 4.7.

For most developers reading this, the practical advice is simple: keep building your game with Godot’s current renderer. It is good, it is getting better, and it handles everything from 2D pixel art to stylized 3D well. Ray tracing will be there when the hardware catches up and the feature stabilizes.

The fact that it exists at all is the real story.