- Who this is for
- Users trying to run V-Ray GPU through Standalone instead of the host DCC.
- Best fit
- Use this when the scene should render on GPU, but the queue must be explicit about which engine is used.
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 can keep CPU and GPU jobs separate so results and failures are easier to compare.
- GPU engine check
- Platform-specific setup
- Test before batch
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
Which V-Ray Standalone option chooses GPU rendering?
V-Ray Standalone exposes render engine options for CPU and GPU modes. Choose the mode that matches the scene, platform, and hardware, then test before queueing.
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.