- Who this is for
- Users looking for easier render priority control.
- Best fit
- Use this when client-critical frames or short test renders need to move ahead of long jobs.
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
V-Raykally includes drag-and-drop job ordering so priority changes do not require editing command files.
- Visual reordering
- Priority-friendly workflow
- Less command-line editing
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
Can I reorder V-Ray render jobs visually?
Yes. A visual queue lets you drag V-Ray jobs into the desired order before starting or continuing the local render queue.
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.