- Who this is for
- Archviz and product visualization users with many camera outputs.
- Best fit
- Use this for archviz camera sets, client options, product views, or any scene with repeated camera outputs.
When to use this
- A project has interior, exterior, and detail cameras for the same delivery.
- Some cameras are urgent previews while others are final overnight renders.
- Each camera needs a separate output folder or filename.
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 makes camera order and output review easier than launching each render manually.
- Camera job ordering
- Output clarity
- Overnight camera batches
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
How do I render multiple V-Ray cameras in a queue?
Export each camera or view as a clear render job, confirm output naming, then order the jobs so previews, finals, and revisions run in the right sequence.
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.