- Who this is for
- Archviz users who want V-Ray workflow automation.
- Best fit
- Use this for client option sets, interior and exterior cameras, resolution variations, and overnight final image runs.
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 fits archviz workflows where the artist needs reliable local queueing more than a studio farm.
- Camera variant queueing
- Overnight still batches
- Free local 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
Why do archviz artists need a V-Ray render manager?
Archviz work often includes many cameras and revisions. A local queue lets the artist order those renders and let them run without manual relaunching.
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.