- Who this is for
- Users preparing animation output and denoising strategy before rendering.
- Best fit
- Use this when denoising could affect flicker, compositing, or the way final frames are processed after rendering.
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 can create the image sequence; denoising should be planned as part of the output workflow.
- Animation sequence planning
- Denoise after render
- Output channel awareness
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
Should I denoise during render or after the V-Ray queue finishes?
For animation sequences, post-denoising can be useful when the required channels are saved and the workflow is planned before the full queue starts.
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.