- Who this is for
- Users whose batch outputs become hard to track after several renders.
- Best fit
- Use this before animation batches, camera variants, or any queue where multiple jobs write image sequences.
When to use this
- Two jobs could accidentally write to the same folder.
- A compositor expects a specific frame padding pattern.
- Skip-existing behavior depends on predictable completed output files.
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 helps expose output choices before the render starts.
- Output naming review
- Cleaner recovery
- Less accidental overwrite
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 should I name V-Ray outputs for queued frame renders?
Use a stable folder, a clear base filename, and consistent frame padding so finished frames are easy to review, skip, retry, and assemble.
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.