- Who this is for
- Users deciding between cloud rendering and local rendering.
- Best fit
- Use this decision path for client-sensitive scenes, smaller batches, or jobs that fit on one machine.
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 supports the local side of the decision: controlled, private, workstation-based rendering.
- Local assets
- No upload workflow
- Queue automation on owned hardware
It will not add cloud compute capacity when local hardware is the bottleneck.
FAQ
Should I use cloud rendering or a local V-Ray queue?
Use cloud rendering when you need extra compute. Use a local queue when you have enough local hardware and want direct control over assets and outputs.
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.