warning
Execute the following via the PythonEditor :
import GafferScene
n = GafferScene.ShaderAssignment()
n["in"]["childNames"].setValue( IECore.InternedStringVectorData( [
"turtles", "all", "the", "way", "down"
] ) )
root.addChild( n )Then look at the innocent looking ShaderAssignment node in the HierarchyView, and marvel at its recursive uselessness.
How does this work? Answers on the back of a postcard please…
Let’s face it, there’s only so much you can learn about Gaffer from a ball of cows. Wouldn’t it be great if there were some more comprehensive examples that resembled how you might work in a studio environment? Something with real assets and light rigs, that showed how to build a multi-shot workflow using a single template script? Well, now there is!
Continue reading “New Gaffer Examples”Gaffer allows scene locations to be organised into sets, and then uses a simple expression language to combine sets for use in light linking, shader assignments and the like. In this short post we’ll discuss a historical limitation of set expressions and present some useful improvements made in Gaffer 0.56.0.0.
Continue reading “0.56.0: New set expression operators”A common pattern that arises in production is the “shot-specific branch switcher”, typically using a Switch or NameSwitch node to choose the right branch for the current shot. In the fictitious example below, this pattern is employed to select the right render settings per shot, with an ArnoldOptions and StandardOptions node on each branch.
Another major release, so soon? You bet. This time we have fewer changes, but they’re quite far-reaching. Included are major updates to the main application’s editor UI, new scene manipulator features, and the new CopyPrimitiveVariables and NameSwitch nodes. Let’s take a tour.
Continue reading “Gaffer 0.55.0.0”
The Gaffer development team will be at SIGGRAPH 2018!
Members from Image Engine’s R&D team will take part in 3 presentations this year.
Continue reading “Gaffer at SIGGRAPH 2018”