alembic taking longer and longer to render with every frame
-
Not sure whats happening here, but scenes in which I have these alembic models are taking progressively longer to render with every frame in the sequence. Ive optimized the scene to render out at about 2mins a frame. This being anywhere in the sequence if I randomly render any frame by itself. about 2 mins.
But when I put it in the queue, redshift slowly creeps the time up as the sequence goes on, only about 30 frames in each frame had jumped to almost 10mins. Unrendarable.
The alembic is a tree model. The leaves have a jiggle deformer affected by a turbulent field to give them some slight movement. That is the reason I have exported it out as alembic.
Is there something I am missing here?
-
Hi c4disstanky,
This is clearly a case for tech support, sorry, I really can't reproduce this.
The only thing that comes to mind is that when each frame by itself renders fine, something triggers the memory load in a way that is not favorable at all. Tech-support might have a quick answer to that.
https://www.maxon.net/en/support-centerI'm sure you have checked the Redshift Forum already
https://redshift.maxon.net/search?term=each%20frame%20longer&in=titles
or
https://redshift.maxon.net/topic/23436/rendering-longer-and-longer-random-time?_=1760424847003
I haven't found any direct match.All the best
-
Tech support got back to me with the solution it seems.
In Alembic properties there is a 'History Depth' option. This seems to be the cause of the memory leak. Think this is always useful if you want a trail effect or something that would require data from the previous 10 frames (I think by default). I turned History Depth down to 1 and the frames are now all rendering for the same amount of time.
-
Thank you very much for updating this, c4disstanky.
Very nice of you to take the time.
Yes, that makes sense, … memory.
My best wishes
