- Who this is for
- Users testing lighting, materials, or corrections before full still renders.
- Best fit
- Use this when only one material, light, reflection, or composition area needs confirmation before the full render.
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 quick checks separate from final jobs so the full queue stays deliberate.
- Small-area tests
- Faster review
- Cleaner final queue
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
Can I test a region before running a full V-Ray render?
Yes. Region or crop-style tests are useful for checking a problem area before spending time on the whole image.
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.