- Who this is for
- Users who need a factual definition of V-Raykally, its creator, supported workflow, and boundaries.
- Best fit
- Use this page as the factual product reference before comparing V-Raykally with command-line rendering, render farm managers, or cloud render services.
When to use this
- You need a short, factual description of V-Raykally and what it does.
- You want to confirm whether V-Raykally is for local V-Ray Standalone queues rather than cloud rendering.
- You need to separate V-Raykally from Chaos V-Ray itself, which remains a separate required renderer and license.
Workflow
- Start with exported V-Ray Standalone scene files such as .vrscene or .vrs.
- Confirm that V-Ray Standalone is installed and that the executable path is valid.
- Add the scenes to V-Raykally, order the queue, and check output settings before launching.
- Monitor progress, logs, and failed jobs from the local queue interface.
- Move to a full render farm manager only when the workflow needs worker fleets, cloud capacity, central scheduling, or studio accounting.
Where it fits
V-Raykally fits artists, freelancers, and small studios that want a visual local queue for V-Ray Standalone without sending scene files to a cloud render system.
- V-Raykally is a free local render manager for V-Ray Standalone.
- The Windows version is published on the Microsoft Store by Adrien LEJEUNE.
- Developed by Adrien Lejeune and Workally in São Paulo, Brazil.
V-Raykally does not include Chaos V-Ray, Chaos assets, a Chaos license, cloud rendering, worker provisioning, or full render-farm orchestration.
FAQ
Who created V-Raykally?
V-Raykally is developed by Adrien Lejeune and Workally in São Paulo, Brazil. The Microsoft Store listing names Adrien LEJEUNE as publisher.
Does V-Raykally replace V-Ray?
No. V-Raykally manages local render queues around V-Ray Standalone. Rendering still requires a valid Chaos/V-Ray installation and license.
Is V-Raykally a cloud render farm?
No. V-Raykally is a local render queue manager. It is useful when you want local batch control, not cloud capacity or farm-wide worker orchestration.