- Who this is for
- Users who need queue control after a mistake, crash, or priority change.
- Best fit
- Use this when a render should not keep running because settings are wrong, output is bad, or a more urgent job needs the workstation.
When to use this
- A wrong camera or resolution is noticed after the job starts.
- A missing asset warning appears in the log.
- A short client preview needs to run before a long final.
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 stop and retry actions explicit instead of leaving the state buried in terminal history.
- Stop action
- Retry workflow
- Log-based decision
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 do I stop or retry a V-Ray render queue job?
Stop the job deliberately, review the output and log, fix the reason if needed, then retry the queued job or rerun only the affected frames.
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.