- Who this is for
- Users deciding between command-line automation and a local queue interface.
- Best fit
- Use this when command-line rendering works but editing scripts for every production change becomes annoying.
When to use this
- A client asks for one urgent camera to move ahead of the rest.
- A script fails and nobody remembers which command produced the output.
- Artists need a repeatable workflow without owning the shell script.
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
A local queue keeps the benefits of V-Ray Standalone while reducing script maintenance for everyday batches.
- Visual job order
- Visible logs
- Less script editing
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
Should I use a V-Ray queue or a batch script?
Use a script when the workflow is stable and technical. Use a visual queue when jobs change often, artists need to reorder renders, or logs and retries should stay easy to see.
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.