- Who this is for
- Users preparing unattended V-Ray render sessions.
- Best fit
- Use this when the workstation should stay productive after hours with multiple renders lined up.
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
V-Raykally is built for exactly this local queue pattern: prepare the list, start it, and review job states later.
- Unattended local queue
- Clear completed and failed states
- Output and log review
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 render V-Ray jobs overnight?
Build the queue before leaving the machine: validate V-Ray, confirm outputs, order jobs by priority, enable useful retry or skip settings, and monitor results in the morning.
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.