Physically-Based Rendering

When I want to test my intersection code, for example when I break the KD-tree (oops), I usually switch to ASCII mode.

The Stanford bunny in all its binary glory:

................
................
...........**...
........*****...
.....*****......
....*****.......
...******.......
....*****.......
....******......
....*******.....
....*******.....
....*******.....
....******......
....******......
................
................

Note that this render is unbiased :-p

Yes, another blog on ray-tracing!

I am developing a photo-realistic render engine and hopefully this blog will make me stay focused and perhaps get useful comments.

The main objective of this render engine is to produce as accurate and realistic pictures as possible, possibly at the expense of render time.

For this reason this engine will implement physically-based, unbiased modelisation and rendering methods.

It is currently extremely primitive: It only supports Monte Carlo path tracing, simple area lighting scheme and Lambertian reflections.

Here is a test render featuring the famous Stanford dragon: