[gfodor]

Uh, what. Sampled raytracing is the most natural approach to indirect lighting, displacement mapping, subsurface scattering, and anti-aliasing.

As far as non-realistic rendering goes I am not sure how this is relevant, you can alter the properties of light and still use ray tracing, and many effects use image based techniques anyway.

Raster will die in the long run, it's pretty obvious.

[lcrs]

Raytracing may be conceptually the most natural but it's not always the best choice for a lot of these cases - displacement, motion blur, depth of field and anti-aliasing are still often handled much more quickly by micropolygon/scanline rendering even if the lighting and shading is raytraced. Hair and fur is pretty problematic with raytracing too.

That said, physically-based shading is massively easier to art-direct, even if the "front end" as it were of the renderer isn't naively tracing rays from the camera. There's a killer set of slides and notes documenting ILM and Sony's switch to PBR here: http://renderwonk.com/publications/s2010-shading-course/

[exDM69]

> Raster will die in the long run, it's pretty obvious.

Care to elaborate why you think this is the case?

Even when doing raytracing, the fastest way to do the first pass is to rasterize your triangles and output hit data to textures (similarly to deferred rendering).

Additionally, triangle rasterizerization can be used for vector graphics, etc while raytracing is inherently only for 3d content.

I think that in the future we will have some kind of hardware acceleration for raytracing along with traditional triangle rasterization and they will be used together.

[gfodor]

In the long run graphics will probably converge on an approach that properly estimates the rendering equation. That's why I think ray tracing ultimately will be the preferred solution.

(I'm talking on a extremely long timeline)

[dragonwriter]

> Sampled raytracing is the most natural approach to indirect lighting

Its been a while (~15 years or so) since I looked very deeply into this, but at that time I thought that radiosity was notably superior to raytracing for indirect lighting, and everyone and their cousin seemed to be doing hybrid ray tracing/radiosity systems for realistic rendering.

[rayDawg]

ah, what do we use to determine form factors in radiosity? oh yeah ray tracing.

[rayDawg]

>Raster will die in the long run, it's pretty obvious. I see, so I guess you plan to ray trace your gui and the text on screen too?

[gfodor]

What do you think?

[duaneb]

> Sampled raytracing

This covers about 100 different algorithms. Pick one.

[rayDawg]

I think that's the point.

[duaneb]

So, you didn't address the problem of "There's no obvious raytracing algorithm." All of the above algorithms have tradeoffs that make them ill advised in some sense. None of the above algorithms can handle displacement mapping or dynamic scenery with any speed. Get back to me when you solve those ridiculously combinatorial problem—any object can interact with any other object. And when you can animate objects in constant time between frames (as opposed to, at best, O(log(n)), and at worst, O(n)), maybe it'll be useful for realtime.