Core concepts
Five ideas explain almost every SnowyPlover definition.
1. Time is a number from 0 to 1
SnowyPlover never deals in seconds or frames while you build the animation. Every animated component has a t input that expects a number from 0 (the start) to 1 (the end). A camera move at t = 0.5 is halfway along its path; a section cut at t = 0.5 has cut halfway through the building.
Seconds only matter at the very end, when
View Capture Driver turns totalDuration × fps into a number of frames.
2. Feed every t from one place
Put a single Number parameter on the canvas, name it t, and wire every t input from it. While you work, feed it from a Number Slider (0 to 1) or from
Duration Counter to play the animation in real time. When you export, feed it from the master Time output of
View Capture Driver instead. Only that one wire changes between previewing and exporting.
To give different parts of the animation their own timing, put an
Event Timeline between the hub and the components. It splits one t into several events, each with its own 0 to 1. See Timing with Event Timeline.
3. Cameras travel as one value
Camera components pass around a Camera: one value that holds a name, location, target, lens length and up direction. Camera moves take a camera and a t, and give back a camera. You can chain them, and only
Apply Camera actually changes the Rhino viewport.
To make a camera from points, use
Construct Camera. To read its parts back out, use
Deconstruct Camera.
4. Buttons switch things on
Some components have a button under them. The button replaces a Boolean Toggle and remembers its state in the file.
- Inactive / Active on
Apply Camera and
Apply Design Option. Nothing in the Rhino document changes until you click it to Active. Apply Design Option restores the original layer visibility when you switch it off again. - Update on
Get Camera From Viewport and
Get Camera From Named Views. Click it after you change the view or the Named Views, because Grasshopper cannot see those changes by itself. - Play and Reset on
Duration Counter. - Export Frames on
View Capture Driver, and Make Video, Make GIF and Join Clips on the video components. Click again while they run to stop. - Live on
Mesh Outline Preview, and Bake on the Utility components that write to the Rhino document.
Many components also have options in their right-click menu, for example the easing of
Event Timeline or the projection of
Apply Camera. The component descriptions on the reference pages mention them.
5. Export goes frame by frame
When you click Export Frames,
View Capture Driver runs this loop for every frame i from 0 to n − 1:
- set
master Timetoi / (n − 1), - let the whole definition recompute and the viewport redraw,
- save the viewport as
{baseName}_000000.jpg,_000001.jpg… (PNG whentransparentis on), - move on to the next frame.
Because it waits for each frame, a slow definition only makes the export slower, never choppy. The video components then read that folder. See Export frames and video.
Reading the diagrams
The diagrams on this site are drawn like the Grasshopper canvas, in a simpler style.
- Inputs are on the left of a component and outputs on the right. Grey input names are optional.
- A thin wire carries one value, a double wire carries a list, and a dashed wire carries a data tree, as in Grasshopper.
- Orange wires carry t.
- Hover over a port to see its type, default and description, and click a component's name to open its reference page.
- Diagrams usually show only the ports that are wired. The reference page of each component lists all of them.