- Who this is for
- Users who want V-Ray GPU queueing and local render automation.
- Best fit
- Use this when GPU renders need to run one after another and VRAM or scene compatibility needs close attention.
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 keeps GPU-oriented jobs visible in the same local queue model, with logs available when hardware or scene settings fail.
- Local V-Ray executable control
- Job logs
- Retry 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
Can I queue V-Ray GPU renders locally?
Yes, if the local V-Ray Standalone setup and scene configuration support the GPU workflow you want. The queue should still validate outputs, logs, and failed jobs.
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.