Warp <war### [at] tagpovrayorg> wrote:
> Btw, I don't think it's the first recursion level (ie. the rays shot
> from the camera) which consume the majority of the rendering time. The
> majority is consumed by the additional rays spawned recursively from
> the first and subsequent intersecions.
>
>   Even if your idea worked it would only speed up the first recursion
> level, but not the others.
>
> --
>                                                           - Warp

maybe you could marching squares to get outlines of the objects being
rendered and then only intersect the objects before the seen one.
You can also predict multiple subsequent levels.
As this will already trace most of the pixels you don't have to retrace
those (except for AA).
BTW, implementing marching squares also increases quality of AA because it
misses less subpixel lines (should pixels found to be wrongly antialiased
be retraced if they are a bit of (under-antialiased)?)
Still, I think most of the time is spent not figuring out whether there is
an intersection but where is it (think of parametric surfaces).

Post a reply to this message