[Bf-cycles] Script node updating from OSL defaults

Brecht Van Lommel brechtvanlommel at pandora.be
Fri Jan 11 12:35:33 CET 2013

On Fri, Jan 11, 2013 at 10:54 AM, Lukas Tönne <lukas.toenne at gmail.com> wrote:
> I'd like to clarify a design decision of the OSL script node:
> When changing defaults of OSL input parameter defaults and then
> updating the script node, it will currently not replace the
> default_value of the node inputs. Only when you make a new script node
> instance (or when the parameter did not exist before) will it actually
> replace these input values.
> There are pros and cons to both approaches, but i think for the
> purpose of rapid prototyping it would be preferable to update node
> input values each time. IMHO the supposed workflow is:

I don't think this would be a good change. One reason is that updating
the node is not only done by developers, but also by artists using it
in actual projects. If you have a new version of a script with a
bugfix or new feature then it should be safe to update the node
without breaking materials.

The second reason is that it is useful to develop the node with
multiple objects using different variations of parameters.


More information about the Bf-cycles mailing list