- Who this is for
- Privacy-conscious users who need offline V-Ray rendering.
- Best fit
- Use this for client-sensitive assets, private archviz work, or locations with unreliable connectivity.
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 designed as a local app, so render files, assets, and outputs stay under the user's local control.
- No cloud render dependency
- No analytics or tracking stated in privacy policy
- Local file workflow
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 render manager work offline?
Yes. A local manager can launch V-Ray Standalone jobs on the same machine without uploading scenes or relying on a cloud render service.
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.