- Who this is for
- Users preparing long still or animation batches and trying to reduce risk.
- Best fit
- Use this when the render will run unattended, use expensive GPU/CPU time, or produce many frame outputs.
When to use this
- The scene was changed shortly before final rendering.
- The output folder is new or shared with another sequence.
- A single missing texture would make every frame wrong.
Workflow
- Render one representative frame at the final path and settings.
- Open the output file and confirm naming, resolution, and color look right.
- Review the log before adding the full frame range.
- Start the batch only after the test frame passes.
Where it fits
A local queue makes it easy to run a small test job before the longer final job.
- Small test job
- Log review
- Safer overnight render
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 render one test frame before starting a V-Ray batch?
Yes. A test frame confirms that V-Ray Standalone, assets, output naming, camera, resolution, and render settings behave correctly 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.