What the Rendercow is, in essence, is the Vue rendering engine, minus the GUI and library management systems, and with a simplified file system and a TCP/IP interface. When you install Mover 5 (or have the Pro version of Vue), HyperVue is installed; this is the distributed network manager. How it works is that it uses the actual Vue application as the controller; each Cow is sent the scene data (geometry, etc), then the textures, so that they have no need of accessing the main system for resources (it's a good idea to have the swap file set to 2 or 3 gigabytes, just so you have enough room for textures -and- processing space). The next bit of data sent is the frame parameters (which frame it is, pixel ratio, size, screen format, some other things). The HyperVue manager works on a polling basis (Vue itself does not render when it acts as the controller; you need to have a Cow installed on the system Vue is on). Whichever Cow is listed first on the list of detected Cows will render frame 0, and on down the list in descending order. When a Cow is done with a frame, it sends it back to the controller with a flag that it is ready for a new job, and the controller sends it the next available frame that isn't being actively rendered. The rendered frames are saved in a temp format until the whole batch is done, then are converted -after- the animation sequence is finished (HyperVue is sensitive to packet collision, and apparently memory fragmentation can play havoc as well, so the conversion and saving has to wait until there's no active rendering going on) As for animation.... has anyone pointed you at Phoul's site yet...? O:)