- Who this is for
- Users recovering from interrupted V-Ray render batches.
- Best fit
- Use this after power loss, application crash, workstation restart, or a failed overnight queue.
When to use this
- Some frames are complete and should not be rendered again.
- The last job stopped in the middle of a still render.
- Logs need to show whether the failure was assets, memory, paths, or interruption.
Workflow
- Inspect completed outputs before restarting anything.
- Read the failed job log.
- Use skip-existing or resumable settings only where they apply.
- Retry the smallest useful set of jobs or frames.
Where it fits
A local queue keeps failed and completed states visible, which makes recovery less manual.
- Crash recovery
- Skip completed outputs
- Failed job retry
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 do I continue a V-Ray queue after a crash?
Check which outputs completed, review logs, decide whether resumable rendering or skip-existing behavior applies, then rerun only the jobs or frames that still need work.
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.