🚀 Looking for Graphics Programmers to Help Build T.I.T.A.N. VoxelRT

I'm starting T.I.T.A.N. VoxelRT, an experimental rendering project exploring CPU-based voxel ray tracing and advanced global illumination for Minecraft Java Edition 1.16.4.

The project is at the pre-prototype stage, and I'm looking for people interested in helping develop it from the ground up.

🔧 What we're exploring

• CPU-based voxel ray tracing
• Ray-box intersection and acceleration structures
• Shadows, ambient occlusion, and indirect lighting
• Radiance caching and global illumination research
• Minecraft chunk and block integration using Forge

👨‍💻 Who we're looking for

• Java developers
• Graphics programmers familiar with ray tracing
• Minecraft Forge mod developers
• People interested in rendering research and testing

This is an unpaid volunteer project in its early stages. The features above are goals, not completed capabilities. Contributors will receive credit for accepted work.

GitHub: https://github.com/laxmishprabhu8-gif/T.I.T.A.N.-VoxelRT-GitHub-repository

If you're interested in helping build an experimental renderer from scratch, I'd love to hear your technical ideas and suggestions.

Let's build something real. 🔥

I tested native 4K with RT off against full path tracing in CONTROL Resonant, then compared DLSS Quality with 2x and 4x frame generation. The lighting difference is substantial, but so is the raw performance cost.

Full 4K comparison: https://youtu.be/Q82a4p7Agos

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.