Voro arrives as one folder. Keep it together, keep it where you put it, run its installer once, and load its package into TouchDesigner. Every area is in that one folder; the packs decide what is inside.

Voro needs Windows and a compatible NVIDIA GPU and driver. TouchDesigner is installed and licensed separately.

What you receive

The folder holds the engine, the plugins, one package tox, and one tox per operator:

Folder	What it is
bin/	The engine and its contract data. Everything in Voro runs through this one engine.
plugins/	The operators’ native code, model runners and the kernel, script, rig, geometry and Warp runtimes.
tox/voro_package_<version>.tox	The package, the one tox in tox/. Load this one.
operators/	One tox per operator, for placing a single operator without the whole package.
models/	The model store, with the models the shipped operators use.
lab/	Voro Lab, for making graphs with a coding agent. Start at lab/START_HERE.md.
packs/	One folder per pack, each listing the operators that pack holds.
LICENSES/	The licence texts for the third-party software, fonts and models in the package.

The other folders hold data the package reads. Leave them where they are.

A pack is one area’s operators and runtime. The base is the engine with Rig and Audio. The Image packs are Kernel FX, Script FX and ONNX FX. Geometry and Warp are their own packs. Bundles named voro and voro-cuda group them; the names may change before the packs are final.

Install

1. Extract the whole package into a folder you intend to keep.
2. Run install_voro_tensor.bat. It checks the engine, asks for your Voro code, registers this folder for TouchDesigner and prepares the renderer for your GPU. The first run takes about ten minutes. Leave the window open until it ends.

Your Voro code comes with your invitation, and Voro runs graphs only on a signed-in computer. You can also enter it later with Enter Voro Code on the package’s Key page or in Voro Studio’s settings. Signing in needs the internet once; Voro then keeps a 30-day lease on the computer and renews it by itself whenever you are online. The lease stays on this computer, never in a project, so your .toe and graph files stay shareable. Voro beta has the details.

The installer uses the Python that ships inside the package, so you do not need to install Python.

If you move the folder, run the installer again. If TouchDesigner picks up an older release, close TouchDesigner, run this folder’s installer again and reopen. To move to a new drop, follow How updates work.

Open it in TouchDesigner

1. Load tox/voro_package_<version>.tox into a network. The installer prints its full path. The package COMP appears.
2. Start the engine from the package. The VOP family appears in the OP Create dialog, with a Voro column on the left whose view buttons switch the menu between Audio, Image, Geometry and Rig.
3. Place an operator from any view.

To open a graph file, place voro_import_graph, set Graph File to a .voro file and press Import. The graph arrives as one COMP of ordinary operators you can edit. The COMP shows the graph’s picture. Its Graph page picks which output it shows and holds any controls the graph promotes. Save your .toe as usual.

After a driver update

When you update your graphics driver, the renderer prepares itself again on the next render. That can take about ten minutes. The node’s Status shows the progress. Wait for it to finish before you judge a blank picture.

Runtimes for authoring

Kernel FX compiles through a pinned Python runtime that is not in the download, because it is large and its CUDA pairing is specific to your machine. bootstrap_voro_kernel_fx_runtime.ps1 in the folder builds it once, into %LOCALAPPDATA%\dotsimulate\voro\runtimes\kernel_fx outside the drop (so it survives updates), and records where it went so a fresh TouchDesigner session finds it. It needs the internet and about 600 MB. Run it again any time; the install is idempotent.

The models/ folder ships with the models the shipped operators use, such as Depth Anything, RF-DETR, Real-ESRGAN for Upscale, NeuFlow for Optical Flow and LivePortrait for Portrait Rig. Stream Diffusion wraps an existing StreamDiffusionTD install and is the one that needs its own. A node that needs a model you have to supply says so in its Status.

Make something with an agent

Voro Lab ships in lab/. Give lab/START_HERE.md to your coding agent with your idea and a folder to work in. The Lab writes, runs and renders graphs as ordinary files and needs nothing else installed. Bring the result into TouchDesigner with voro_import_graph.

Studio, the standalone graph application, is supplied separately.

First things to place

• Audio: First patches
• Image: First pipelines
• Geometry: First scene
• Rig: Serve a surface

Reporting a problem

Write to support@dotsimulate.com, or post in the voro-support forum on the dotsimulate Discord. Send these with your report:

• the release name from release.manifest.json in the folder
• your GPU and driver version
• your TouchDesigner version
• the node’s Status or error
• the smallest project that shows the problem

Leave out credentials and private assets.

License

This is a commercial beta. Paid work and public demos are allowed. Your original work stays yours. Read Licensing & Usage and the LICENSE_VORO_BETA.txt file in the package. The file in the package controls if they differ. Third-party notices and Privacy sit beside it.