The Pulse

Voyager Releases vork 0.1.0 as a Research Preview Where AI Agents Write 3D Scenes as Code

vork 0.1.0 is a source-available, headless 3D and VFX engine from Voyager that lets AI agents create scenes as code and render them without a graphical editor. The research preview supports recent NVIDIA GPUs and Apple Silicon but ignores f

AI.info Team · Written with AI · fact-checked · 2026-11-07

Voyager released vork 0.1.0, its headless 3D and VFX engine for AI agents, as a research preview on 6 November 2026. vork is written in Rust and Slang and renders on GPUs through Vulkan and Metal. An agent writes a scene as code, runs a render command, examines the image and revises the code. The engine has no editor, timeline or window.

Scenes are JSON documents

A vork scene is a JSON document containing meshes, lights, cameras, materials and animation tracks. Python and TypeScript SDKs can write that document, and a single command renders it. On Voyager’s figures, a fresh install on an M5 Max took 86 seconds for shader setup; the first render in each profile took 5 to 6 seconds, and each std/final render after that took about 0.43 seconds.

The standard profiles cover different render settings: std/previs is for iteration, std/draft uses four samples with denoising, std/final uses eight samples with denoising, and std/path is the path tracer. vork scenes can also carry Slang programs that define materials, cameras, light propagation, film response, simulation and compositing through public hooks. The project's black-hole example uses a Schwarzschild light-propagation program in the scene, which the README describes as a numerical approximation rather than an exact relativistic solver.

vork's getting-started help is about 2,500 tokens and includes a complete first scene; root, topic and command help total about 19,500 tokens, and detailed field lookups add more. The help also lists what does not work, while unknown fields produce errors naming the nearest valid fields.

Voyager’s benchmarks against Blender

Voyager measured vork on an NVIDIA L4 using one frozen build, while the Blender 5.2.1 comparison times came from earlier runs under different settings. For 1080p stills across 10 scenes with a baseline, vork's std/final profile took 1.58 to 2.25 seconds, compared with 2.41 to 3.27 seconds for EEVEE; the project reports vork as 1.15 to 1.90 times faster, but not at equal quality.

Across seven 240-frame, 1080p movie tests, vork took 35 to 92 seconds and EEVEE took 48 to 213 seconds, a reported speed advantage of 1.14 to 2.32 times that also does not compare equal-quality output. In two named 1080p still comparisons, vork's path tracer took 26.9 and 31.9 seconds, while Cycles took 4.6 and 16.0 seconds; vork was 5.81 and 1.99 times slower, respectively.

For an eight-second, 1080p24 render of a million birds at four samples, vork took 97 seconds. The project estimates EEVEE would take 13 to 18 minutes, or 8 to 11 times longer, but labels that comparison projected rather than measured. The estimate uses eight warm frames at the same sample count, excludes simulation, startup and encoding, and gives Blender the finished flock as geometry; Voyager also notes differences in quality, material translation and motion.

What does not work yet

This release ignores fog and participating volumes, with a warning. Large scenes and dense transparency can fail, including on Mac, and lowering resolution does not necessarily fix the problem. In the project's frozen sweep on Linux and NVIDIA, 583 of 585 images were delivered; the million-stars stress scene ran out of GPU memory in both profiles, and Mac reliability was not revalidated in that run.

New programs can take minutes to compile on a scene's first render, with no output while compilation runs; the README reports about three to four minutes for custom programs on NVIDIA and under 20 seconds on a Mac. Later renders take seconds. At four and eight samples, fine facades and hair can lose detail, defocus can produce stepped or grainy edges, and sparse sparks or spectral highlights can change brightness and colour.

The water example is, in Voyager’s words, an experiment with finite particle budgets, unresolved thin features and no two-way rigid-body coupling, and is not a replacement for a mature simulation package. The engine supports a recent NVIDIA GPU with hardware ray tracing on Linux or Windows, or Apple Silicon; AMD, Intel and older GPUs, and CPU or software rendering are unsupported.

Free to use, restricted to redistribute

vork is source-available under the vork Preview License, not open source. It is free during the research preview, including for commercial work inside a company of any size. Users may modify the code for their own use and share unmodified copies, but may not sell it, distribute a modified version or offer it as a hosted service where other people submit scenes or jobs without written permission.

The licence permits rendering for a user's own organisation and delivering finished media to a client. It covers this version only, and later versions may have different terms, including paid ones. The optional Blender bridge is a separate component under the GPL.