Skip to content
Twozero Docs
Sign in
Download
Twozero Docs

START

Install on Windows

Install twozero on Windows in about two minutes: double-click one file and confirm one permission prompt. On a Mac? See Install on macOS.

On this page 4
GET STARTED, then confirm the Windows permission prompt.

Install

  1. Download the plugin: DOWNLOAD TWOZERO on twozero.ai. You get one .tox file, named like twozero_install_3_468.tox.
  2. Close your project, then double-click the downloaded .tox. TouchDesigner opens it as its own project.
  3. Click GET STARTED.
  4. Confirm the Windows permission prompt (UAC). twozero writes a small loader into the TouchDesigner installation folder, and Windows asks once for that (why?).
  5. Open your own project again. The twozero buttons are in TD's top bar, in every project.

When the install is done, the Connect your agent wizard opens by itself, then a short tour. See Connect your agent and First run.

If GET STARTED seems to do nothing

The permission prompt can open behind the TouchDesigner window. Look for it in the taskbar and confirm it there.

Dropping it into an open project

Dragging the .tox into the network editor of an open project also installs it. TouchDesigner then opens a second window for a few seconds to write its interface file, and the permission prompt comes from that window. Let it finish. Double-clicking the .tox skips the second window, which is why it is the recommended route.

Good to know

  • Reinstalling a version that is already in place does not ask for permission again.
  • On an older TouchDesigner build the installer shows Older TouchDesigner with CONTINUE ANYWAY and CANCEL. You can go on, but plugin updates stop arriving until you update TouchDesigner.
  • A new TouchDesigner build needs a fresh install: the plugin is stored per TD build. Settings and your local folder load automatically.
  • The installer writes a log to pisangVersions/install_debug.log in TouchDesigner's preferences folder. Attach it when you ask for help.
  • A few Windows 11 problems are still open and tracked on GitHub. See Troubleshooting.