Before you start: the
voyager CLI (quickstart) and a leased machine (m=$(voyager cloud lease render-lite --wait --yes)). Searching the library needs no sign-in and no machine.Find, lock, sync
1
Search the library
vy.model.telescope-on-tripod-05@1), score, size in metres, triangles, texture sizes, licence and the command that adds it. --kind is model, material or hdri. “No good matches” means the library has none; it names the closest.2
Record the assets you want
In the folder you will push:
--lock-only writes voyager-assets.lock.json with the exact versions and downloads nothing here. Options after : are that asset’s own: here the HDRI at 1k, the model at its only size (2k).3
Push the lock
4
Sync on the machine
scene/assets/<id>@<version>/: the model as glTF with its textures, the HDRI as one EXR. This took 12 seconds for both. The machine image ships the CLI as voyager-cloud, so on the machine you run voyager-cloud assets …, not voyager cloud assets ….assets/… like any others. Run voyager-cloud assets sync again on any other machine to get the same versions there.
Know what you’re using
Licences differ by asset, and some require a credit: check
assets show before you deliver, and add the assets credits file to anything you hand over.
Models are glTF in metres, Y up, with the pivot at the bottom centre. Materials are PBR maps with a .material.json giving their real-world tile size. HDRIs are equirectangular; assets show gives an HDRI’s sun direction and the matching Blender sun rotation.
Keep asset files out of pushes
Never push library asset folders from your computer: a sync on the machine is faster. Addassets/vy.* to a .voyagerignore in the folder you push, or pass --exclude 'assets/vy.*'. push warns when it sees library asset files.
Next
Render with Blender
Scene templates that build a shot from library assets in one command.
Render with Vork
The Vork render loop on cloud GPUs.