- Who this is for
- Users tired of checking terminals or output folders to know render state.
- Best fit
- Use this during overnight or multi-job local rendering where status should be visible at a glance.
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 provides live queue status and a log-focused dashboard for local V-Ray jobs.
- Live status labels
- Console output panel
- Job details view
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
How can I monitor V-Ray render progress?
Use a queue dashboard that shows pending, running, completed, stopped, and failed jobs, with log details available when a render needs investigation.
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.