c-ray

I did a lot of this for my raytracer, c-ray [1]. Originally it was just a self-contained C program, but I got tired of writing buggy and limited asset import/export code, so eventually I put together a minimal public C API [2] that I then wrapped with CPython bindings [3] and some additional python code [4] to expose a more 'pythonic' API. It's all still a WIP, but it has already allowed me to write a Blender plugin [5], so now I can play around with my renderer directly in Blender, and test with more complex scenes others have made. Fun project, and it's really cool to see my little renderer in the interactive viewport in Blender, but I have also learned that I don't particularly enjoy working with non-trivial amounts of Python code. [1] https://github.com/vkoskiv/c-ray [2] https://github.com/vkoskiv/c-ray/blob/51a742b2ee4d0b570975cd...

If anyone here happens to like both C (C99) and raytracing, I've been working on c-ray[1] for a while now. It's your average pathtracer, but has some nice features such as clustered network rendering, a really fast BVH and an up-and-coming node-based material system. Scene descriptions are expressed as JSON. I'm looking into building a Blender plugin to be able to use it from there. Coding style is what I prefer - code should be dumb and simple, using nothing more than basic control flow, structs and functions. C suits this goal very nicely. [1] https://github.com/vkoskiv/c-ray

> which I implemented for RenderMan Cool, you work at Pixar? I've been working on a small hobby renderer [1] for a few years, and RenderMan has been a big inspiration! [1] https://github.com/vkoskiv/c-ray