karba this versión 2.16a don't have f-stop, why ?

is a problema work without f-stop
please add again this option
thank you
happy 2015
change in 2.15:merid888 wrote:thank you for new reléase
karba this versión 2.16a don't have f-stop, why ?![]()
is a problema work without f-stop
please add again this option
thank you
happy 2015
makes sense to me.Removed the pins "Fstop" and "ISO" from the camera imager node, since they only control exposure which is done already by the exposure pin. The only thing these two pins added was confusion, since some people expected the ability to control the depth of field with Fstop. You can find a Lua script graph that emulates the old behaviour here: viewtopic.php?f=73&t=43944
Some of the render elements seem to be comparable to max elements, including z depth. So it´s not really compatible with octane, or of any use in comps, as it is now.wastzzz wrote:All the Render Elements now work with production rendering, BUT their quality is not acceptable, borders are jagged. They also have the wrong anti aliasing settings.Karba wrote:I have updated the installer to 2.16a. I forgot to fix network render statistic.
Please make them use the same anti aliasing filter size as in the Kernel settings, and improve the sampling, or let us choose the number of samples.
Thank you,
M.
Try to enable Alphashadows I think i had this problem when I used dirt material and no alpha shadows enabled http://render.otoy.com/forum/viewtopic. ... ne#p211354noelnoel wrote:white line between the intersection of two objets with opacity, not matter if its diffuse, glossy or specular material, no matter kernel or gi mode, always appears.
there its a way to avoid?
octane for max 2.15