Back to documentation

V-Ray render manager FAQ

Frequently asked questions about V-Ray render queues, local render managers, V-Ray Standalone, and V-Raykally.

Who this is for
Users looking for a consolidated FAQ before downloading a V-Ray queue manager.
Best fit
Use this when deciding between manual commands, V-Raykally, and full farm software.

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 is the free local option for users whose main need is queueing V-Ray Standalone jobs.

  • Clear local/farm distinction
  • Plain-language answers
  • Links to deeper pages

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

Is V-Raykally a render farm manager?

No. It is a local V-Ray Standalone queue manager. That distinction matters when choosing between a simple workstation workflow and a full farm scheduler.

Can it batch render V-Ray scenes?

Yes, it is designed to queue exported V-Ray scenes and run them locally in order.

Does it replace OpenCue, Qube, Royal Render, RenderFlow, or other farm managers?

No. It can replace the lightweight local queue need, but not a full farm scheduler.

Which platforms does V-Raykally support?

V-Raykally runs on macOS (Apple Silicon and Intel, delivered as a signed and notarized DMG) and on Windows x64 (Windows 10 build 19041.0 or later) via the Microsoft Store.

Sources