Quickstart: your first render
This walkthrough renders a Blender scene on one Arc G1 node and brings the frames back. Other applications follow the same four steps; only the plugin command differs.
1. Create an account and log in
Sign up at the signup page. Your trial includes 200 core-hours or 5 GPU-hours, enough for a couple of hundred test frames. Then install the sync client and sign in from your terminal:
cgsync login
Opening browser to confirm code QXPT-4480 ...
Logged in as dana@studio.test (plan: Spark, region: eu-north)
2. Check the scene before it travels
From the project folder, run a dry run. It lists every file the scene references and its size, flags absolute paths and tells you which files the farm already has.
cgsync scene check kitchen_v12.blend
files 214
total size 38.6 GB
already on farm 31.2 GB (81%)
to upload 7.4 GB
warnings 2 absolute paths (D:/tex/oak_*.exr) will be remapped
3. Submit
cgsync submit kitchen_v12.blend \
--frames 1-240 --class g1 --region eu-north \
--within 2h --cost-cap 40 --tag kitchen-promo
job_8f2a1c queued estimate $18.40 - $23.10 (14 nodes, ~1h 50m)
The job page opens in your browser. Frames show up as they finish. If the estimate looks wrong, cancel from the page; you pay only for the three sample frames.
4. Download
cgsync pull job_8f2a1c --to ./renders/kitchen
240 / 240 frames, 41.2 GB, verified
Jobs keep frames for 14 days. Run cgsync pull --watch to download frames as they finish while you work on something else.
Where to go next
- Uploading scenes covers caches, relative paths and very large projects.
- Node classes explains how to pick between CPU and GPU.
- Renderer licences shows what is metered and what you bring.