- Who this is for
- Users comparing V-Ray Swarm, DR, and render queue workflows.
- Best fit
- Use this when Swarm is an option but the immediate problem is still launching scenes one after another.
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 focuses on job ordering, status, logs, and local execution instead of distributed bucket management.
- Sequential local queue
- Visible logs
- No Swarm setup required
It is not a Swarm controller and does not coordinate distributed rendering servers.
FAQ
Should I use V-Ray Swarm or a local render queue?
Use V-Ray Swarm when you want distributed rendering support across machines. Use a local queue when you mainly need to run several V-Ray Standalone jobs in order on local hardware.
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.