FX, crowds
& the systems
behind them.

The control centre of the whole job: 40 pages in one window, grouped like a film is made — shots, intake, plate, finish, production, system. Every module opens as a set of guided paths that report first and act only when you confirm.

Live demo of version 4.63 · open a shot in Workflow · draw on a frame in Review · every project, shot and person is fictional

Every render of the shot in one window, checked before it costs an hour. It finds every Karma pass of the scene and reads the settings Karma will really use, then guards what usually goes wrong: camera vs resolution, CPU vs XPU, the shot the hip belongs to. It counts the frames already on disk, renders only the missing ones, predicts when it will be done, and sends the passes to the farm with one button — every frame and hour lands in the project's ledger.

Live demo · fix the red guard · try ½ resolution · press SUBMIT TO FARM · works on a phone · every name is fictional

Press Submit to Farm in Houdini or Nuke. The scene is checked, the first and last frames come back in a minute, every machine in the studio shares the rest and your phone tells you when it is done. Every job says why it waits, a sleeping machine is woken when work is waiting, a chunk that fails goes back in the queue. The queue is a shared folder: no database, no server to look after.

Live demo · tap a job · wake RENDER-C · + Test job jumps the queue · open ACTIVITY · send your own passes from the Render Manager demo · every name is fictional

A client note at 8 pm: "+20% pscale on BIGGERHERO, relaunch WINTER". The Runner turns it into one chain per shot — prep the hip, render the passes, rebuild the comp, mail you — without opening a scene. Each stage waits for the one before, on FRANK FARM or on this machine. A pass that fails the Render Manager’s check is skipped and written in the log; the rest of the chain goes on.

Live demo · edit the client note · pick shots · farm or local · LAUNCH and watch the chains · every name is fictional

Instead of nudging forces until the dust happens to land on the logo, you say where the particles must be, and when. Every particle gets its own point and its own frame — oldest first, the word written left to right — and its own flight, leaving along its birth velocity and curving in. The GPU polishes all the flights together: smooth, spaced, flowing, nobody crossing a letter already written. In Houdini the real POPs follow them with their own physics and land on their points — any particle count, the artist's own setup.

Live demo · drag the points of the dashed ROUTE to change how the stream reaches the word · click a frame of the strip to stop on it · FLIGHTS draws the paths

Magical dust trails art-directed from a single curve. A family of layers — fine dust, foils, hero sparks — shares one animation through a leader, while each layer keeps its own size, look and Karma render stream. A guided path takes you from curve to render: animate, foils, pixie dust, forces, simulate.

Live demo · click the paths or HOME · data is fictional

Turns a finished project into a VFX breakdown, end to end. It knows what the reel needs and finds it in the project, cleans screen recordings (dead time cut, speed ramps), conforms everything to spec, builds the story on a beat-snapped timeline with build-ups and AOV grids, writes the Vimeo texts and exports Vimeo, IG 9:16, 4:5 and 1:1 at -14 LUFS — or hands Premiere a ready XML.

Live demo · click the guided steps · project and credits are fictional

Dresses a whole set in minutes. It reads the network, turns every branch into a named unit, tidies the SOPs with backdrops and builds the LOP network on its own. Then you drag materials onto the stage tree — or let it guess: project memory, context rules and an AI fallback propose a look for every mesh. Emitters become Karma geometry lights, lanterns get point lights, and the look ships as a versioned USD.

Try it · drag a sphere onto a row, or press ACCEPT GUESSES · scene is fictional