- Who this is for
- Users considering open source render management for V-Ray.
- Best fit
- Use this when OpenCue is attractive but the setup is more infrastructure than the current render workload needs.
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 avoids database, scheduler, and worker setup by staying local and V-Ray-specific.
- Local desktop workflow
- No farm services
- Focused V-Ray Standalone jobs
It is not open source and does not provide OpenCue's farm architecture.
FAQ
Should I use OpenCue or a local V-Ray queue?
Use OpenCue for a real render farm with central scheduling. Use V-Raykally when you only need a local V-Ray Standalone queue.
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.