- Who this is for
- Users trying to render only selected frames rather than a full animation.
- Best fit
- Use this when only a few frames need review, repair, or replacement after a longer render.
When to use this
- Only a few frames have visible artifacts.
- A client asks for selected animation stills.
- You want a stepped preview before rendering every frame.
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 selected-frame jobs separate from full animation jobs.
- Partial frame work
- Repair passes
- Preview ranges
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 V-Ray Standalone render specific frames like 1, 3, 5-10, and 100?
Yes. V-Ray Standalone supports frame lists, ranges, and steps through its frame range option, which is useful for tests, fixes, and partial rerenders.
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.