SnowyPlover

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.

The t hub. Use the slider or Duration Counter while you build, and switch the hub to master Time to export. Connect only one source at a time.

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.

Get Camera From Viewport: Get Camera Parameter From Current Viewport. Click Update to read the viewport again after it has changed.Get Camera From Viewportactivate (On) Boolean · item default false Toggle to runactivatecamera (C) Camera · item Camera object containing [Name, Location, Target, Lens, Up].cameraUpdatet0.4Orbit Camera: Set Camera on a circular path to create a orbit shotOrbit Cameracamera (C) Camera · item Camera object containing [Name, Location, Target, Lens, Up].camerat Number · item Normalized time parameter in [0,1]tradius (R) Number · item optional Customed path radius, if no input, using the current camera parameter radiusheightScaler (H) Number · item optional Customed camera heigth, if no input, using the current camera locationheightScalercamera (C) Camera · item Camera object containing [Name, Location, Target, Lens, Up].cameraApply Camera: Apply a Camera object to the active Rhino viewport. Click the button to switch applying on or off; right-click the component (or the mode input) to pick the projection.Apply Cameracamera (C) Camera · item Camera object containing [Name, Location, Target, Lens, Up].cameramode (M) Integer · item Optional. Projection mode: -1=use camera projection (perspective if absent), 0=Perspective, 1=Two-Point, 2=Parallel. Leave unconnected and right-click to pick it instead.modeInactive
Read a starting camera, move it, apply it.

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.

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:

  1. set master Time to i / (n − 1),
  2. let the whole definition recompute and the viewport redraw,
  3. save the viewport as {baseName}_000000.jpg, _000001.jpg … (PNG when transparent is on),
  4. 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.