Smarter RAM and VRAM Recovery for Blender Renders
Renderjuice now detects RAM and VRAM issues during renders, shows them clearly, and automatically retries on machines with more memory when needed.
Large Blender scenes can fail for a simple reason: the render needs more RAM or VRAM than the current machine has available. That should not leave you guessing.
Renderjuice now detects RAM and VRAM pressure during renders, reports the issue more clearly, and can automatically recover by moving the job to a machine with more memory when required.
RAM and VRAM Issues Are Now Visible
When a render hits a memory-related problem, Renderjuice can surface that issue during the render instead of hiding it behind a generic crash or failure state.
That makes it easier to understand whether a scene is running into system memory, GPU memory, or another render issue. For memory-heavy projects, this gives you a clearer answer without digging through raw Blender logs.
Automatic Recovery on Larger Machines
When Renderjuice detects that a job needs more RAM or VRAM, it can update the job’s memory requirement and boot a better-suited machine for the next attempt.
For example, a render that runs out of GPU memory can be retried on a machine with higher VRAM. A render that needs more system memory can be retried on a machine with more RAM.
Fewer Manual Retries
The goal is to reduce the back-and-forth that normally happens with large scenes: submit, fail, inspect logs, choose a bigger machine, then submit again.
Renderjuice now handles more of that recovery automatically. If a scene needs more memory and a supported machine is available, the render can continue with a better match. If the scene requires more memory than Renderjuice can currently provide, the job can fail faster with a clearer reason.