- Who this is for
- Users trying to prevent missing textures and cache files in queued renders.
- Best fit
- Use this when a render should run outside the exact workstation and folder setup where the scene was created.
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 benefits from collected assets because fewer jobs fail halfway through a batch.
- Asset collection
- Fewer missing files
- Safer render box workflow
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
Should I collect assets before adding a V-Ray job to a queue?
Collect assets when rendering from another disk, machine, or folder structure. Same-machine queues may only need validation, but a test render still matters.
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.