- Who this is for
- Users preparing unattended local rendering on a workstation.
- Best fit
- Use this when local hardware can finish the job but the workstation environment might interrupt the queue.
When to use this
- The machine normally sleeps after a short idle period.
- Network storage disconnects when the workstation locks or sleeps.
- Operating system updates could restart the machine overnight.
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 only run reliably when the machine remains available, so environment checks matter.
- Unattended render prep
- Power setting awareness
- Storage and network checks
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 keep my computer ready for overnight V-Ray renders?
Before starting the queue, check power settings, sleep behavior, storage space, network drives, and any update prompts that could interrupt V-Ray Standalone.
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.