- Who this is for
- Users who know V-Ray Standalone and are looking for a queue interface.
- Best fit
- Use this when V-Ray Standalone is already part of your pipeline but job launching and progress tracking are still manual.
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 wraps the local V-Ray executable with queue management, job ordering, and a dashboard built for V-Ray scenes.
- Designed around V-Ray Standalone
- Supports local-first rendering
- Works on macOS and Windows
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 a V-Ray Standalone queue manager?
It is a tool that organizes multiple V-Ray Standalone render jobs, launches them in order, and shows status without requiring manual terminal commands for each scene.
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.