Cubric Vision - Install

Installation

Download the portable release, extract it to a folder you control, and launch from there. No installer wizard, no package manager.

Portable release

Cubric Vision releases are portable. Download the compressed release file from the official GitHub releases page, extract it to a folder you control, then launch the app from the extracted folder. There is no separate installer wizard.

Open the README first if you want the short file-by-file explanation. What you launch depends on your platform:

File Platform Use it for
CubricVision.exe Windows Launches Cubric Vision. It sits at the top of the extracted folder and is the only thing you need to double-click.
start macOS, Linux Launches Cubric Vision normally.
start-with-terminal Linux Launches Cubric Vision with a separate terminal window so you can see background logs while the app runs.

The launch files carry a platform extension in the folder — start.command on macOS, start.sh on Linux. The rest of what you see beside them is the app itself, plus the update scripts covered below.

Cubric Vision runs on Windows, macOS, and Linux. Linux launches directly from the extracted folder. Windows and macOS each need one extra step the first time, described below.

Updating Cubric Vision

Cubric Vision updates itself — you should never need to touch a file in the folder to stay current.

  • The update prompt. When your installed version is behind the latest release, Cubric Vision shows a pop-up on launch asking whether to update. Accept and it closes, downloads the new version, applies it, and reopens on its own. The prompt appears each time you start the app while you are out of date; dismiss it three times and it stays quiet until the next release, then asks again.
  • The update scripts, if you ever need them. update pulls the latest version from GitHub and update-from-zip applies an update package ZIP you already have — useful offline, or if an update ever fails. On Windows they are script files, and a clean Windows 11 install blocks them outright, so update from inside the app there.
  • If an update fails, the reason is written to update/update.log beside the app, and the app tells you why on the next launch instead of vanishing silently.

Coming from 1.2.0 or earlier on Windows?

Download the full ZIP from the releases page rather than updating in place. The updater in those builds is a .bat file, and Smart App Control blocks it outright, so an in-place update cannot reach you. From 1.3.0 onwards the app checks for updates on startup and offers them in-app on all three platforms.

Your projects live in your Documents folder and are untouched either way.

Reopening after an update was a 1.4 fix, and it applies to updates run from 1.4 onwards — the updater that runs is the one already installed, so updating to 1.4 still needs you to reopen the app yourself.

On Windows, updating in place from a version before 1.3.0 leaves an old app folder behind in your Cubric Vision folder. Nothing uses it any more and it is safe to delete — about a gigabyte back.

Windows - first launch

Windows - one-time step

Extract the ZIP anywhere and run CubricVision.exe from the extracted folder. Windows may show a blue box titled "Windows protected your PC" instead of starting the app. If it does:

  1. Click More info.
  2. Click Run anyway.

Cubric Vision then launches normally. On many machines no warning appears at all and the app simply opens — both are normal. If you do see it, you only do it once per version.

Why does this happen?

Cubric Vision is open-source and is not code-signed, so Windows may not recognise the download and can warn you before running it. A code-signing certificate costs money and, unlike Apple's notarization, would not remove this warning — it only starts the clock on the reputation Windows is waiting for. Linux has no equivalent step; macOS has its own, described below.

Already have Cubric Vision and it will not start?

If you are on a version before 1.3.0 and the app does nothing at all when you launch it, updating cannot fix it. The updater is a script file, and a clean Windows 11 install blocks script files outright — the same reason the app itself will not start. Download the full build fresh from the releases page and extract it. Your projects live in your Documents folder and are untouched; point the new folder at your existing engine and models, or set them up again.

macOS - first launch

macOS - one-time setup

Cubric Vision for macOS is open-source and runs in place, so it is not signed or notarized by Apple. macOS marks the download as quarantined and blocks it on first launch with a message like:

"start.command" Not Opened - Apple could not verify "start.command" is free of malware that may harm your Mac.

macOS showing the unzipped Cubric Vision folder in Finder with start.command, the quarantine 'Not Opened' block dialog, and a Terminal window open
macOS blocks the unsigned launch file on first run. One Terminal command clears the quarantine for the whole folder.

This is expected. You only need to clear it once, from Terminal. Right-clicking and choosing Open produces the same block, so it does not help here.

Clear the quarantine in Terminal

  1. Unzip the download.
  2. Open Terminal (Applications → Utilities, or Spotlight search for "Terminal").
  3. Type xattr -dr com.apple.quarantine followed by a space, then drag the unzipped Cubric Vision folder onto the Terminal window to fill in its path. The full command looks like this (the folder name varies by version): 
    xattr -dr com.apple.quarantine "/path/to/CubricVision-macos-arm64"
  4. Press Return to run it, then double-click start.command to launch Cubric Vision normally.

Why is this needed?

Notarizing a macOS app requires a paid Apple Developer account. Until Cubric Vision is notarized, this one-time step is how macOS lets you run unsigned open-source software you trust. Linux has no equivalent step - it runs directly. Windows has its own one-time step, described above.

This applies to fresh installs only. After an online update (update.command), there is no re-quarantine: the updater runs locally and the files are not re-downloaded by the browser.

Once the app launches for the first time, continue with Getting Started to choose where models live and finish setup.