Problems rendering an animation (image sequence)

surv0101

I'm at a loss. Every day, a new issue is popping up. Today I tried rendering a 600 frame animation and the render gets to about 400 frames and then stops, or slows down to a crawl. 1 frame at the start takes about 30 seconds, after 400 frames, a single frame takes about 8 minutes. I have never seen Daz act this way. The render times have always been the same the first frame of an image sequence to the last. I have rendered 1200 frame animations for two years now, no problem. Just to make sure it wasn't the scene itself, I rendered out an old animation, and sure enough, when I past around the 400 frame mark, everything slows down. My first thoughts were, it is acting like I am running out of memory, but why? It has never been an issue before, and this is a very light scene, with just 2 G8 characters. So I thought of what is new about my Daz program. I joined the Premier subscription service, so now I have the included plug-ins, some of the Toon stuff is new, and the auto save feature. The auto save was the only thing that really had anything to do with memory, so I turned it off(I think), but it made no difference. That is the only thing that has changed other than the updates I do all the time. I am on the latest Beta build. The only thing that looks out of place in the log file is a error or warning that says Progressive_Aux_Canvasas should be turned on when using a post denoiser.  I'm not sure what that is, or how to tell if it is turned on or not.  I would have to look at the specs for my PC but it has never been a problem before. I went crazy on the memory, RTX 4090, Thread Ripper...etc. It should handle everything just fine. Any thoughts or ideas where to start to troubleshoot this problem? I do have the latest N-vidia studio driver.

felis

Have you tried looking in the log: Help > Troubleshooting > View Log?

And how you tried monitoring VRAM usage?

mikael-aronsson

If it does not stop rendering, just slows down it might be switching to CPU rendering, anything about that in the log ? as far as I understand there has been(are ?) memory leaks in iRAY when it renders, if so it might be eating up VRAM for each frame and after 400 frames it runs out of memory and switch to CPU, just an idea, but if that is the case there should be something about this in the log, you could have a look in the task manager and let it render for a while and look at the curve for VRAM..

RenderSP

surv0101 said:

I'm at a loss. Every day, a new issue is popping up. Today I tried rendering a 600 frame animation and the render gets to about 400 frames and then stops, or slows down to a crawl. 1 frame at the start takes about 30 seconds, after 400 frames, a single frame takes about 8 minutes. I have never seen Daz act this way. The render times have always been the same the first frame of an image sequence to the last. I have rendered 1200 frame animations for two years now, no problem. Just to make sure it wasn't the scene itself, I rendered out an old animation, and sure enough, when I past around the 400 frame mark, everything slows down. My first thoughts were, it is acting like I am running out of memory, but why? It has never been an issue before, and this is a very light scene, with just 2 G8 characters. So I thought of what is new about my Daz program. I joined the Premier subscription service, so now I have the included plug-ins, some of the Toon stuff is new, and the auto save feature. The auto save was the only thing that really had anything to do with memory, so I turned it off(I think), but it made no difference. That is the only thing that has changed other than the updates I do all the time. I am on the latest Beta build. The only thing that looks out of place in the log file is a error or warning that says Progressive_Aux_Canvasas should be turned on when using a post denoiser.  I'm not sure what that is, or how to tell if it is turned on or not.  I would have to look at the specs for my PC but it has never been a problem before. I went crazy on the memory, RTX 4090, Thread Ripper...etc. It should handle everything just fine. Any thoughts or ideas where to start to troubleshoot this problem? I do have the latest N-vidia studio driver.

I have the same issue, but only just started to notice it on a new computer I bought over Christmas. 

I went with the 4090RTX too and 128gb of system Ram, 
WHen it's processing the first images in the series, it's getting through 2-3 per minute, but after a while, it starts to slow down to 1 every 2 minutes, then 3 minutes.  A restart of the machine seems to do the trick.  It's a simple scene with 2 characters, an enviroment and 4 or 5 spotlights - around 3mb in size. 

I have checked the log and I can't see any additional errors that start when things begin to slow down.  
Now I know I am not the only one, I will keep a closer eye on the log-file, but happy to receive any ideas.