Gaffer 1.7.6: Painting, Lighting and MCP

For those who don’t know the tool: Gaffer is a free, open-source, node-based VFX application for scene assembly, look development, lighting, rendering, image processing and pipeline automation.

Gaffer 1.7.6.0 sharpens its light and attribute editors and adds geometry controls. The preceding 1.7.5.0 release introduced an MCP interface that lets an AI assistant control a running Gaffer session or launch a headless one. Instead of promising to solve the pipeline, the interface gives an assistant access to an actual pipeline application. A modest ambition, and therefore a useful one.

A graph that has real work to do

Gaffer’s node graph manages scene hierarchies, filters, instancing, shader assignments, lighting, render passes and image-processing operations. Deferred, multithreaded evaluation helps it handle complex scenes without eagerly calculating every branch. Artists can inspect and modify scene contents non-destructively, while technical directors can drive the same operations through Python, C++ and Open Shading Language.

Renderer support includes Arnold, Cycles, 3Delight and RenderMan, with a renderer abstraction layer for shared workflows. The current download and compatibility page names Arnold 7.4 and 7.5, Cycles 5.1.0, 3Delight 2 and RenderMan 26.3, 27.2 and 27.3, plus Tractor 2 and optional Deadline integration. Gaffer also builds on production libraries including OpenEXR, OpenImageIO, OpenColorIO, Cortex and Open Shading Language. It is released under the BSD licence, so studios can adapt and integrate it rather than negotiate with a licensing committee every time someone wants to automate Tuesday.

The MCP connection, and the small matter of trust

Version 1.7.5.0 added an mcpEnabled setting to PythonEditor. Once enabled, an AI assistant or large language model can execute arbitrary Python in Gaffer and receive screenshots of the interface or captures from image nodes as feedback. The separate gaffer mcp application supports launching and controlling a headless session. Its underlying API includes Gaffer.MCP.Server, HTTP and stream transports, and extension points for custom tools. The assistant operates the application through Python instead of simply explaining its interface.

The phrase ‘execute arbitrary Python’ deserves a second reading. The MCP connection is useful for controlled experimentation, repeatable tasks, graph inspection and pipeline assistance, but it also gives the connected assistant the capabilities of the Python environment it reaches.

Painting geometry, not merely drawing conclusions

The same 1.7.5.0 release added PrimitiveVariablePaint for partial edits to primitive-variable values and PaintTool for painting colours and masks into vertex primitive variables. Artists can paint selected attribute data for localised look-development and geometry changes without maintaining a complete alternative mesh for every adjustment. DataStore gained a default plug, while the Viewer, SceneInspector and SceneReader gained support for half-typed OpenVDB grids. Arnold gained support for rendering volume levels of detail stored in VDB, and SceneReader began writing ParticleField3DGaussianSplat USD prims and reading their spherical-harmonic coefficients.

What 1.7.6 changes today

Gaffer 1.7.6.0 adds editor controls for lighters and technical directors. LightEditor can filter its hierarchy. LightEditor, RenderPassEditor and AttributeEditor can filter columns by search text, and the first two editors can show an All section collecting columns from every section. Tabs now size to their labels. It sounds unglamorous until a show adds enough custom columns to turn a useful lighting spreadsheet into an archaeological site.

Merge now has a Collect mode that evaluates input plugs in multiple contexts and accumulates the results. RandomPrimitiveVariable gains a BooleanSelection mode, useful for decimation alongside DeletePoints, DeleteCurves and DeleteFaces. The maintenance work fixes invisible PointInstancer prototypes that were being rendered anyway, an AttributeEditor All-section problem and an Arnold OSL-ramp issue after USD export and re-import. The fixes address scene and editor behaviour that can consume a real production afternoon.

The practical catch

The official downloads offer Linux and Windows builds. Linux requires glibc 2.28 or later, and Windows 10 or 11 needs the Microsoft Visual C++ Redistributable. Nvidia graphics are recommended. Renderer integrations require specific versions. Check the farm against the published matrix before deployment. Gaffer is open source and free to use, but the production value comes from making its graphs, Python hooks, renderer versions and review process agree with one another.

Before connecting MCP to production assets or migrating a lighting scene, test a representative graph on the target workstation and renderer farm, with backups and controlled permissions in place.

Links and sources

https://www.gafferhq.org/

https://www.gafferhq.org/download/

https://www.gafferhq.org/documentation/1.7.6.0/ReleaseNotes/1.7.6.0.html

https://www.gafferhq.org/documentation/1.7.5.0/ReleaseNotes/1.7.5.0.html

https://www.gafferhq.org/documentation/

Facts Box