- Who this is for
- Users queueing renders on a workstation they still need to use.
- Best fit
- Use this when local rendering should not make the workstation unusable for email, review, or light production work.
When to use this
- The queue runs during the workday.
- A workstation must stay responsive while rendering previews.
- One render should not consume every CPU thread.
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 can keep the render process organized while V-Ray thread settings control workstation impact.
- Workstation responsiveness
- CPU control
- Local render comfort
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 can I keep working while V-Ray renders locally?
Limit the number of V-Ray CPU threads or set the related environment variable so the workstation keeps some CPU capacity free.
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.