- Who this is for
- Users considering a render farm but needing a simpler local option.
- Best fit
- Use this before building a farm when your bottleneck is manual job launching, not lack of render nodes.
Workflow
- Export or collect the V-Ray Standalone scene files you want to render, usually .vrscene or .vrs files.
- Confirm that the V-Ray Standalone executable path is configured and valid on the machine that will render.
- Add the scene files to the queue, check output settings, and put jobs in the order they should run.
- Choose the useful safeguards for the job, such as frame range, skip existing frames, resumable rendering, output format, and log review.
- Start the local queue and monitor status, logs, and completed outputs from one dashboard.
Where it fits
V-Raykally keeps the setup local and lightweight while still cutting down on manual render supervision.
- No server setup
- No worker fleet required
- Simple local scheduling
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 avoid setting up a V-Ray render farm?
If all jobs can run on one local machine, you may not need a farm. A local queue manager can solve the immediate problem of ordering and monitoring V-Ray jobs.
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.