Production-minded Nuke tools and selected VFX work
The main focus here is practical Nuke/Python tooling: small workflow improvements designed around artist trust,
safe behavior, and repeatable production habits.
The VFX work is included as context for how I understand shots, reviews, handoffs, and technical decisions from the artist side.
Artist-facing Nuke Python tool to bulk disable, enable, or toggle user-defined heavy node classes across a script.
It is designed to be safe and predictable: it only modifies each node’s disable knob and does not rewire the script.
Nuke PythonDisable-knob onlyArtist-facing
Built from a common comp problem: keeping scripts responsive without manually hunting for heavy nodes.
Problem
Artists manually disable heavy nodes to keep scripts responsive, then risk forgetting to re-enable something before final render.
What I built
A low-risk Nuke Python tool that toggles user-defined heavy node classes while only modifying each node’s disable knob.
Why it matters
It turns a repetitive and error-prone artist habit into a predictable action with clear safety boundaries.
Nuke-integrated Qt browser for reusable disk-based .nk and .py toolsets.
It is designed for artists who want to find, insert, create, and manage reusable setups without digging through old scripts.
Qt browser.nk / .py toolsetsMetadata
A small shared-library concept for reusable Nuke setups and Python toolsets.
Problem
Artists often search old scripts to copy reusable setups, which is slow, inconsistent, and difficult to keep organized.
What I built
A Nuke-integrated browser for reusable .nk and .py toolsets stored in shared and personal libraries.
Why it matters
It helps turn useful setups into a browsable workflow that artists can reuse without digging through old scripts.
I include compositing work here because it explains how I approach tools and support: from the artist side,
with attention to image quality, review notes, handoffs, and practical constraints.