I feel like this must be pretty early on if there isn’t yet a checkmark for the feature “lights.”

Yeah this is neat but it is 90% not done and that is being generous.

For a open source path tracer with a full glTF compatible material model and lighting and runs in the browser check out:

https://github.com/gkjohnson/three-gpu-pathtracer

Or if you want hardcore features look at Moonray from Dreamworks:

https://github.com/dreamworksanimation/openmoonray

Yes, there are definitely better resources out there. This is just a WIP I had that I thought I’d share.

People might feel misguided with the submission title not mentioning that. I liked the pictures though !

See also, nVidia's guide on writing a CUDA accelerated raytracer: https://developer.nvidia.com/blog/accelerated-ray-tracing-cu...

Good job. It's a decent undertaking for a single person.

From a cursory glance, you might also be able to speed up the CPU backend by getting rid of the shared_ptrs and defining a stricter memory ownership model.

Damn this is sick! Grats on your effort so far!

"the project now uses CUDA, so i changed to C++11 since thats what nvcc supports."

I feel like nvcc supports at least 17 maybe even 20 already.

Indeed, C++20 already, although some stuff is still missing like modules.

What's the story with regards to high dynamic range and tone mapping in raytracers in general? I only know of Filmic Blender to advertise this as a feature

Most professional renderers operate in linear floating point space and thus handle hdr with ease.

Why not help Blender instead of reimplenenting it all?

Blender already has CUDA-accelerated raytracing; this is a hobbyist building their own raytracer for the fun of it.

Have you heard of the word "hobby"?

I'm kind of with you, but I suppose its a culture/mind-set thing.

I hate reinventing the wheel, but who knows what kind of innovation could happen by combining unique experiences and lessons someone can learn for future use.

For instance, I made a laser pointer, I could have bought one for $10-$100, but I decided to make my own, learn about Electrical Engineering and optics. I never finished it, but it taught me a ton about EE along the way. Now I am quite comfortable with EE, except the parts I'm uncomfortable about ofc :)

To learn! Everyone should write a ray tracer (or three) on their own before even attempting to dive into a big open source production renderer. An established high profile project isn’t a great place to learn the fundamentals, since those parts are already done, and they don’t necessarily want people contributing who aren’t ready for it or are just there for personal learning purposes. It’s not fair to call it ‘reimplementing’, this project isn’t trying to be Blender. There are loads of other reasons to write a non-Blender renderer aside from learning, including writing one for games or interactive or scientific applications, needing special features, doing research and experimenting with rendering algorithms and data representations, needing a very small/fast/light renderer codebase, etc. etc.

TBH, I'm amazed at how efficient CUDA is compared to CPU on even a fairly lowly GPU. RTX 3050ti vs AMD Ryzen 5 6600H and I see close to 30x in pytorch.

It makes me wonder if CPUs will start adding a lot of matrix math specific extensions in the near future.

That was Larrabee whole idea, and AVX is what is left of it.

I thought ray tracing was very branchy type code which is not suited for GPU. If I have a bundle of rays strike an object, they could all scatter different directions and end up following very different paths in the scene. Is it hard to make all rays execute the same code at the same time?