Gaffer 0.59 includes some important changes to how Boxes are exported for use as References (.grf files).
We no longer reset the default values to those currently set on the node.
If you ever export a Box, or publish a reference, read on!
Continue reading “Gaffer 0.59 : Reference export changes”Gaffer 0.58.6.0 brings with it a host of improvements to the Spreadsheet node:
To support these features, editing is now achieved via double click. Read on to learn more about these changes.
Read moreGaffer 0.58 contains a caching optimisation that can significantly improve interactive performance in many cases. But this optimisation can also reveal subtle bugs in Nodes that may have gone unnoticed until now. In this post we’ll explore why that is the case, and outline some useful strategies for catching and eradicating such bugs from your custom nodes.
Continue reading “Gaffer 0.58.0 : We’re going on a bug hunt”Gaffer 0.57.0.0 introduced Edit Scopes. They are fundamental in our endeavours to make Gaffer more user friendly for everyday tasks. They provide a container for node graph edits made by interactive tools in the UI. In this post, we take a quick look at how they work.
Check out the video above to see them in action then read on for more details.
Continue reading “0.57.0: Edit Scopes introduction”
As adoption of Gaffer 0.56 or later is contingent on moving to Arnold 6, we appreciate it may take a little longer to switch production shows over. People may also move directly to the the upcoming release of 0.57.
This post contains a quick recap of the main artist-facing changes in the 0.56 series for those moving up more recently.
Continue reading “0.56 series: New features recap”
We’ve made a long-awaited tweak to the Set node in the recently released Gaffer 0.56.0.0. The confusing Paths plug .vs. PathFilter debate is finally over.
TL;DR: Just use a PathFilter – Paths is no more.
Continue reading “0.56.0: Set node tweaks”For this instalment in our ground-up series about integrating Gaffer into a pipeline, we cover how to change node defaults.
All Gaffer nodes have plugs, whether they are visible in the Graph Editor for easy connection, or in the Node Editor as settings. These plugs have default values defined by the node’s programming. It may be the case however, that these defaults aren’t the most useful values for your use. To help with this, Gaffer allows you to provide your own, “user” defaults.
Continue reading “G4P – part 6 – Node defaults”
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”Gaffer 0.55.0.0 introduces the NameSwitch node; like a Switch node, but using names instead of indices for switching between the inputs. This post shows an example of the NameSwitch in use, and describes how you might customise its UI to better suit your pipeline.
Continue reading “Customising the NameSwitch node UI”Gaffer’s Box node is a staple building block sharing chunks of node graph (via the Reference system), or quickly building tools via expressions and promoted plugs.
The Gaffer docs have a page covering Box nodes and how to use them. In this post we take a quick look at how to re-create a simple GroundPlane tool made in the UI, using only Gaffer’s python API.
Continue reading “Scripting Box nodes”
