Does your VRam usage "build up" doing image sequences

surv0101

I have recently been having a heck of a time rendering animations. This is a new problem for me. I am using a 4090 and haven't had this problem until recently. When I render a animation (image series), I run out of VRam around 400-600 images. So my question is after each render, does some memory get stored somehow so it builds up over a large number of renders, like when you render an image series. I have found a Purge Memory utility in my scrips file, but I don't know what it is, how it works, or if it can help. I don't know how to get around this problem. If all I can make is 3 or 4 second videos, I may have to move to another program. I don't want to do that, as it would take a long time to learn starting fresh.  I forgot to mention, I can stop the rendering process every 400 renders, shut down Daz Studio, start it up again and do another 400 and repeat the process, but then rendering overnight or after I go to work does not work out. 

WendyLuvsCatz

this happened to me a while back after updating my Nvidia driver

 I rolled back to an earlier one and haven't updated since 

been a few since

Richard Haseltine

In general it is not a good idea to render a full aniamtion to a movie format, rather render to a sequence of images and asemble them in a video editor - this has many advanatges, one of which is that you can render as many as you consider safe and then restart Daz Studio before doing another batch of frames (it also allows for editing frames, saving in a format such as PNG that supports an alpha, adding an audi track in the editing, redoing problem areas and just rerendering those, etc.)

You driver may well be an issue here, though older drivers have security issues so roling back may not be viable.

crosswind

Purge Memory script deals with the undo stack in RAM rather than anything related to VRAM consumption. And as Wendy mentioned, in general, rendering with newer drivers consumes more VRAM, it was proved by various testing, i.e. Iray engine reserves more VRAM with newer drivers, scene related used VRAM cannot be 100% released after each render is saved, etc. So especially when you render numerous images with an animated range, you're approaching the "critical point" of running out of VRAM.

There might be no 100% perfect solution except for optimizing your scene, rendering by batch, etc... I'm afraid.