- Who this is for
- Archviz users who need multiple views from one scene export.
- Best fit
- Use this when one project scene contains several cameras and each camera should become a reviewable output.
When to use this
- Interior, exterior, and detail views share the same scene.
- One camera is a quick preview and another is a final image.
- Each camera needs a different output 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 keeps those camera jobs visible and reorderable.
- Camera-specific jobs
- Clear output names
- View-set queueing
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 queue different cameras from the same V-Ray scene?
Yes. If the exported scene contains the cameras, create separate jobs for the camera outputs and make the camera choice explicit for each job.
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.