As I see it, the f-stop value in the defocus node has nothing to do with what f-stop is in Cycles (and in reality). This value in the defocus node is a purely creative tool, and as such should stay, but the name should change to "focal blur" so it is not confused with the concept and mechanism of f-stop, IMHO.
On Tue, May 12, 2015 at 7:10 AM, Knapp <[email protected]> wrote: > Is it not so that you set it in cycles and then live with the results but > in the compositor you can change it real time and see the results? I would > not want to loose the interactive aspect. > > On Mon, May 11, 2015 at 11:55 PM, Sergey Sharybin <[email protected]> > wrote: > > > I'm not sure how you can drop F-Stop from the defocus node. it's not > > guaranteed that render scene is used for compositing, meaning different > > value might be needed. > > > > On Tue, May 12, 2015 at 2:27 AM, Antony Riakiotakis <[email protected]> > > wrote: > > > > > -- > Douglas E Knapp > > Massage in Gelsenkirchen-Buer: > http://douglas.bespin.org/tcm/ztab1.htm > Please link to me and trade links with me! > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
