> No, the current post processing is simply not very efficient (it is
> designed to be very flexible but this limits performance quite
> significantly).  What you think is a second render is simply gathering
> the depth information from the data stored during the main render.

Thanks for your quick reply Christoph.
Is there maybe a trick to bypass the macro bottleneck and quickly dump the
collected depth + normal information into a binary file which I can then
analyze myself? (especially the edge detection is a factor 100 slower than
the actual rendering).

Greetings,
Elmar

Post a reply to this message