- Who this is for
- Users trying to make V-Ray logs useful during local batch rendering.
- Best fit
- Use this when logs are either too sparse to diagnose failures or too noisy to scan after an overnight run.
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
A local queue makes logs accessible, but useful verbosity keeps them readable.
- Readable logs
- Debug mode when needed
- Faster triage
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 V-Ray verbose level should I use for queue logs?
Use normal warning and error output for routine queues, and increase verbosity only when debugging a specific failure or slow render.
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.