- Who this is for
- Users learning how V-Ray scene files are used outside the host DCC.
- Best fit
- Use this when you want to render without reopening the original DCC scene for each output.
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 is built around this scene-file handoff and helps manage many exported files in one queue.
- .vrscene-oriented queue
- Host-app independent rendering
- Local output control
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
What is a .vrscene workflow?
A .vrscene workflow exports render-ready scene data from a DCC tool, then renders it through V-Ray Standalone, often from the command line or a queue manager.
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.