Back to documentation

Local V-Ray render box workflow

Use a spare local machine as a simple V-Ray Standalone render box before building a full farm.

Who this is for
Users with one extra machine who are not ready for a farm manager.
Best fit
Use this when you have one owned machine for renders but do not need worker pools or central farm scheduling.

Workflow

  1. Install and validate V-Ray Standalone on the render box.
  2. Make project assets and output folders accessible to that machine.
  3. Run one test scene through V-Ray Standalone.
  4. Queue local jobs only after paths and outputs are verified.

Where it fits

A local queue can turn a single render box into a predictable job runner without adding farm infrastructure.

  • One-machine render setup
  • Local job list
  • No farm server requirement

This is for local V-Ray Standalone queues. It does not provide worker provisioning, central asset sync, accounting, cloud bursting, or facility-wide scheduling.

FAQ

Can I use a local computer as a V-Ray render box?

Yes, if V-Ray Standalone, licensing, assets, and output paths are configured correctly on that machine. A local queue can organize the jobs it should run.

Is this a cloud render farm?

No. V-Raykally is designed for local V-Ray Standalone queues on the artist workstation or a local render machine.

What kind of V-Ray files does this workflow target?

The workflow targets V-Ray Standalone scene files such as .vrscene and .vrs, with output and frame options handled around the local V-Ray executable.

Sources