- Who this is for
- Users preparing scene exports from V-Ray-compatible DCC tools.
- Best fit
- Use this when the render should run outside the host DCC app through V-Ray Standalone.
When to use this
- You want to close the original DCC scene while renders continue.
- Several camera variants need to become separate queued jobs.
- A render machine should run exported scene files without manual app setup.
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
A local queue is most useful once the scene exports are ready and repeatable.
- .vrscene handoff
- DCC-independent rendering
- Test before queue
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 should I export .vrscene files for queue rendering?
Export scene files with the camera, frame range, assets, and render settings needed for V-Ray Standalone, then test one output before adding many files to the 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.