[Bf-cycles] Script node updating from OSL defaults
matt at mke3.net
Sat Jan 12 01:07:17 CET 2013
On Sat, Jan 12, 2013 at 11:03 AM, Matt Ebb <matt at mke3.net> wrote:
> Many pipelines also use some kind of versioning system, with variations on
> either updating automatically with the ability to roll back, or newly added
> nodes picking up the new version where existing nodes remain the same.
I should clarify that in a workflow like this, you're usually not working
'live', but in a more private work area, and when you're ready to roll it
out to other artists, it would be published to an asset system/file
server/etc where the new version will be available for others.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bf-cycles