- Who this is for
- Users deciding between DR, network rendering, and a simpler local queue.
- Best fit
- Use this when stills, animation sequences, and local batches each seem to call for different rendering infrastructure.
Workflow
- Use distributed rendering when one heavy still image needs help from several machines.
- Use network rendering or a farm manager when different frames or jobs should run on different render nodes.
- Use V-Raykally when the immediate need is ordering and monitoring local V-Ray Standalone jobs.
- Revisit a farm manager only when worker pools, dispatching, and central policies become real requirements.
Where it fits
V-Raykally covers the local queue case: it orders and monitors jobs on one machine and does not handle DR or farm dispatching.
- Local single-machine queue
- Clear DR/network distinction
- V-Ray Standalone 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
What is the difference between V-Ray distributed rendering and network rendering?
Distributed rendering splits one frame across multiple machines. Network rendering usually assigns whole frames or jobs to render nodes. A local queue is different again: it organizes jobs on one local machine.
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.