- Who this is for
- Users optimizing slow scenes before committing a long local queue.
- Best fit
- Use this when a single test frame is slow enough that a full sequence could waste a day or more.
When to use this
- One material, light, or shader appears to dominate render time.
- A sequence is too slow to brute force locally.
- The queue should run only after the scene is understood.
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 helps execute the final jobs, but profiling should happen before committing many frames.
- Representative frame profiling
- Slow scene diagnosis
- Better queue planning
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 find what makes my V-Ray scene slow before rendering many frames?
Profile representative frames or test renders, then adjust the scene before queueing hundreds of expensive outputs.
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.