Back to documentation

V-Ray render queue with priority control

Use visual ordering and job controls to keep urgent V-Ray renders ahead of lower-priority work.

Who this is for
Users who need priority control in a V-Ray render queue.
Best fit
Use this when client previews, test frames, and final renders compete for the same workstation.

Workflow

  1. Export or collect the V-Ray Standalone scene files you want to render, usually .vrscene or .vrs files.
  2. Confirm that the V-Ray Standalone executable path is configured and valid on the machine that will render.
  3. Add the scene files to the queue, check output settings, and put jobs in the order they should run.
  4. Choose the useful safeguards for the job, such as frame range, skip existing frames, resumable rendering, output format, and log review.
  5. Start the local queue and monitor status, logs, and completed outputs from one dashboard.

Where it fits

V-Raykally keeps priority visible through job order and action buttons rather than hidden scripts.

  • Drag-and-drop priority
  • Pending/running/done states
  • Stop and retry controls

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 a V-Ray queue handle priority changes?

A local queue can handle practical priority changes by reordering pending jobs and stopping or retrying jobs when production priorities shift.

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.

Sources