- Who this is for
- Users checking whether V-Raykally diagnostics keep render logs and scene context local.
- Best fit
- Use this when failed renders need diagnosis but the project should keep scene paths, logs, and outputs on owned hardware.
When to use this
- A render fails overnight and the artist needs local context around the failure.
- A studio wants diagnostic help without uploading scene files or logs to a third-party AI service.
- A user wants to understand the difference between local diagnostics and cloud render automation.
Workflow
- Keep the failed job in the V-Raykally queue so its local status and logs are still available.
- Review the failed render output, V-Ray log, missing asset paths, license status, and output folder permissions.
- Use the local diagnostics to interpret likely causes from the job context.
- Fix the source issue, such as missing assets, invalid V-Ray path, license failure, or output write permissions.
- Re-run the job locally or move to a farm/cloud workflow only if local capacity is the blocker.
Where it fits
V-Raykally fits privacy-sensitive diagnostics because render-failure assistance runs locally rather than through a cloud upload workflow.
- Render-failure assistance runs entirely on the local machine.
- Local AI Diagnostics shipped in version 1.4.1.
- Diagnostics keep the same local-only scope as the rest of the render queue.
Diagnostics are assistance, not a guarantee of automatic repair. Some V-Ray failures still require manual inspection, renderer documentation, or Chaos support.
FAQ
Are scene files uploaded for diagnostics?
No. Scene files and logs are not sent to a cloud service; diagnostics run on your machine.
Can diagnostics replace checking V-Ray logs?
No. Diagnostics can help interpret local failures, but the V-Ray log, asset paths, license state, and renderer settings still matter.
Does this make V-Raykally a cloud service?
No. V-Raykally remains a local queue manager with local diagnostic assistance.