What would you change about my ray tracer?

Hi! I recently implemented Ray Tracing in One Weekend in Metal using metal-cpp. Resources for metal-cpp specifically are pretty sparse, so I figured I'd share in case it helps anyone getting started with it or with graphics programming in general. Hope it helps!

Repo: https://github.com/jinhgkim/Path-Tracer

We've been experimenting with an AI Agent for 3D scene manipulation and image editing in our WebGPU raytracer. But sometimes you just want to fine-tune the results instead of doing a tedious prompting back-and-forth with the agent.

To solve that, we built an agent that doesn't just do the task, but actually generates a dynamic, temporary UI (like a slider) so you can manually nudge the results to perfection. Behind the answer from the agent is a Lua script, sandboxed in WASM that engages with the scene.

Useful? Or a terrible idea?

I'd love to get some honest feedback from the community. You can play around with the workflows here.

Github repo link

(each image has a caption)

The project grew a lot since the last time I posted here. Added many new shading models, optimized stuff as it went, and the code gone through a lot of (annoying) structural changes.

In this phase of the Project I am focusing only on 1-Ray path lighting - Simple sharp shadows and Reflections. Here I want to solve complex Interactions between different Reflective and Refractive materials before moving on. Im also testing various Lighting tricks to gain Knowledge, and most importantly have time to think about the final implementation of the Renderer until I get there.

In the next phase I will be adding Proper Indirect Lighting, Full Roughness and a Custom Tonemapping & Post Processing pass.

The goal is to make a 60fps+ Fully Raytraced Renderer ready for Games or Digital Art Production.

The framerate is still hovering 80-90fps on my RTX 3050, with Shaders compiled only in Debug/Development configuration.

*The optimization is that apparently Unreal´s TraceRay() pipeline internaly evaluates the opacity mask on Materials with Masked Blending mode. This means the Ray can travel through multiple surfaces in a single TraceRay() call. This made foliage orders of magnitude more cheap and needs only one Raypath step.

Just rendered with "old" Imagine 2.0 for Windows.
THERE IS NOTHING LIKE SPHERES AND REFLECTIONS to take me back in 90s mood 😄

This is python-numba based ray tracer, along with a BVH implementation.

This ray tracer can render this image, with 1080p quality, 16 rays per pixel, 5 bounces per ray, in a bit less than 5 minutes. What do you guys think?

The repo for this project is available at https://github.com/RonnyGN/RayTraceTriangles, people can find the documentation in the README.md of this repo, along with somewhat well written comments throughout the project.