- Who this is for
- Users with messy V-Ray outputs from batch rendering.
- Best fit
- Use this when many renders produce files into shared project folders and naming mistakes waste time.
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 keeps output options close to the queued job so artists can check them before starting a long render run.
- Output path visibility
- Format selection workflow
- Folder opening from job context
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 should I manage V-Ray output folders?
Use predictable output folders and filenames per job, especially when rerunning frames, skipping existing files, or reviewing logs after a long 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.