kalast at gmail.com
Mon May 11 23:27:27 CEST 2015
Indeed there is redundancy there. There's just one reason it hasn't
been merged: cycles has its own f-stop number. Ideally we would import
the camera f-stop from blender during rendering but that would require
us to do a version patch -from- cycles camera data to blender to keep
old files working. I am not sure if this is possible..
Personally I don't have any preference over keeping or dropping one of
the two. I can see merits in both ways. Agree it should totally be up
to the users.
On 11 May 2015 at 23:06, Jeroen Bakker <j.bakker at atmind.nl> wrote:
> Hi all,
> just noticed that there are currently 2 places where you can/need to set
> the F-Stop.
> 1. In the camera settings (was first only visible in cycles, but since
> viewport project it is also visible for blender renderer)
> 2. In the compositor defocus node.
> The compositor defocus node does not work without having a camera setup
> as it reads the Distance from the camera. But still we need to set the
> F-Stop in the defocus node.
> Is there a reason why these values have not been merged?
> If not I would suggest to remove the F-stop field from the defocus node
> and read the value from the camera itself. But maybe we should ask the
> Jeroen & Monique.
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers