[Bf-committers] No caustics

[Sergey Sharybin]

It's rather easy to do to make it consistent without braking render result
compatibility. Scripts would break because RNA will change tho.


On Thu, Aug 21, 2014 at 5:40 AM, Bassam Kurdali <bassam at urchn.org> wrote:

> On Thu, 2014-08-14 at 18:40 -0700, gandalf3 wrote:
> > This has bugged me for a while now..
> > Is there particular reason the "no caustics" option in *render settings
> >  > light paths* is called "no caustics" as opposed to just "caustics"?
> - was it a good idea to do it this way?
> Not sure! you're right in that it seems like the logic is kinda reversed
> on both checkboxes (shadow and caustics)
> - is it a good idea to change it now?
> Also not sure!!! can this be done and preserve compatibility with
> existing files? If not, then I'd vote against this: too many files to
> fix...(not to mention python scripts)
> >
> > It seems
> > (
> http://wiki.blender.org/index.php/Dev:2.5/Source/Architecture/RNA#Properties
> )
> > it's preferred to avoid such names, so is there some special case here
> > that I'm missing?
> >
>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin