- Who this is for
- Users planning a local queue before starting a long render session.
- Best fit
- Use this when the queue includes a mix of test frames, client previews, final stills, and animation ranges.
When to use this
- A quick preview can catch a mistake before a long final starts.
- A client-critical camera needs to finish before less urgent views.
- Long animations should not block small checks that could be done first.
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 priority order visible and easy to adjust before starting.
- Visible priority
- Drag-and-drop order
- Less waiting for quick checks
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 order V-Ray jobs in a render queue?
Put quick checks and urgent previews first, keep long final renders later, and group related jobs so output review stays simple.
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.