- Who this is for
- Users troubleshooting visual differences between queued renders and expected V-Ray output.
- Best fit
- Use this when a queued output looks wrong even though the scene looked correct in the interactive viewer.
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 output review repeatable, but color settings still need to be confirmed before a long batch.
- Saved output review
- Display transform awareness
- Consistent final frames
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
Why does my V-Ray Standalone output look different from the VFB?
Saved output and displayed output can differ because of color management, display transforms, LUTs, or environment settings. Compare the saved file, not only the viewer.
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.