save 50% Rendertime, Fix mr Render Element Bug!

[thorsten hartmann]

Yes! Yeah! Super!

 

I can´t believe it. Save 50% Rendertime. Fix the Render Elements Bug with Render Optimizer V3!

 

deactivate "contrast all Buffers" with RO V3, and you have the same speed as Vray Render Elements.

...

2014 can comming!

 

Render Optimizer V3: http://www.infinity-vision.de/page/ro_menue

 

 

have fun!

 

mfg

hot chip

Edited December 29, 2013 by thorsten hartmann

[blank...]

Little explanation:

 

http://forum.nvidia-arc.com/showthread.php?12729-save-50-Rendertime-Fix-mr-Render-Element-Bug!&p=47573#post47573

 

Vray actually has the same setting. In Vray it's called "consider for anti-aliasing".

 

In the case where mental ray or Vray samples passes/buffers, it will look at framebuffers other than the beauty to apply anti-aliasing. In many cases this may trigger more samples than what might be visible in the beauty. These extra samples are applied to all passes to be sure they match, not just the pass that requires it. (Maybe a reflection buffer has noise that isn't noticeable in the beauty for example)

 

If you turn this off, then only the beauty is considered for anti-aliasing. This may speed up rendering a lot but if you use frambuffers or passes to significantly change the result in post, it may introduce more noise.

 

So the question here is: how often do you use only the beauty even if outputting framebuffers and how often do you push a particular framebuffer pass where it needs to be as clean as the beauty?

 

At The Mill we often composite the beauty and then only use passes to subtly adjust the result. So we can often turn this option off. But if you reconstruct and make significant changes using a pass then this might cause problems if it's off.

 

Vray users complain of a similar effect with "consider for anti-aliasing" on so they have been known to turn it off if they don't need it.