News for hackers. Stuff that matters.
Re:The Tungsten Renderer by rndn on Monday January 12, 2015 @06:07PM (#8877072)
It looks like voxel cone tracing is becoming popular at the moment. Both approaches have the disadvantage that you need to keep the entire scene in video memory, however with VCT that memory usage is bounded by the voxel resolution and integration over large solid angles is very cheap and has no aliasing. It's probably also a disadvantage of GPU path tracing that it makes little use of the features that graphics cards provide.
Re:The Tungsten Renderer by wtracy on Monday January 12, 2015 @09:20PM (#8877741)
Here's an article on a voxel raytracer focused on realtime operation: https://directtovideo.wordpress.com/2013/05/08/real-time-ray...

And here's a video of the raytracer discussed in the above link: https://www.youtube.com/watch?v=i8hSZGTXTx8

Re:The Tungsten Renderer by rndn on Tuesday January 13, 2015 @06:33AM (#8879141)
I'm not sure how well this renderer handles arbitrary scenes through. Pieces of broken glass are very suitable for GPU raytracing, because rendering them is not a "branchy" task since there is no scattering, only definite reflection/refraction. The reflections also make it look like there were a lot more triangles. With Monte Carlo sampling you need 4x samples for .5x error, which means that a lot of samples are needed for scattered indirect illumination in a typical scene (I think in the order of 100 to 1000). In VCT you only need 7-13 samples but a lot of preprocessing.
Re:The Tungsten Renderer by wtracy on Tuesday January 13, 2015 @01:22PM (#8881584)
The author mentions that he chose reflective materials for exactly that reason.

Realtime renderers still struggle with things like Monte Carlo.