[Bf-cycles] Script node updating from OSL defaults

Lukas Tönne lukas.toenne at gmail.com
Fri Jan 11 10:54:17 CET 2013

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:

1. Write OSL script, test and adjust usable defaults
2. When the script is ready for use, make instances of it and tweak
values in the node editor

So i would suggest replacing values for all input sockets on every
recompile of the script, even if it means potentially losing some
individual settings. When writing a script i think it is more
important to quickly test the OSL defaults than to keep the values in
the node editor. One can always link the script node to constant input
nodes (at least for floats and colors atm) which will remain the same
during testing.

More information about the Bf-cycles mailing list