- Who this is for
- Users unsure how to run partial animation ranges through V-Ray Standalone.
- Best fit
- Use this when a full animation does not need to be rendered all at once, or when only a section failed.
When to use this
- Only frames 120-180 changed after a revision.
- Every fifth frame is enough for a motion or lighting check.
- A failed overnight render needs only the unfinished section.
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 frame-range jobs visible instead of hiding them inside one long command string.
- Frame range clarity
- Partial reruns
- Test and final passes
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 set a V-Ray frame range before queueing renders?
Use the exact frame range needed for the job, keep output names consistent, and split tests, finals, and recovery passes into separate queue items when that is easier to review.
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.