Rendering Animation, Saving time increases with every frame...

[aleksandar.kasabov]

Hello haniel1107,

We do not have any additional information to share with you at this point. I will make sure to let you know as soon as we have any updates on the matter. Thank you for your patience.

[haniel1107]

Hi, I know you would mention progress on this issue.

But, is there something you can say on this issue?
How does such research look like, is it on a to do list or...

As this issue costs a lot of time... I know you at CG have a lot of it, but others and our paying clients not...
Thanks

[aleksandar.kasabov]

Hello haniel1107,

There is nothing I can share with you at this point. I have additionally boosted the priority of this issue and will update you as soon as we have any news. Thanks for your understanding.

[haniel1107]

Thank you!

[haniel1107]

Hello,
long time ago we discussed this problem... I am still experiencing this issue, even with the actual builds...

So there is no progress and this problem is literally a real time and cost killer...
Couldn't this become more attention?

[aleksandar.kasabov]

Hello haniel1107,

I apologize for the delay. This issue is on our high priority list but has not yet been fixed. I will let you know as soon as we have more information. I appreciate your patience.

[imdb]

This issue might be the same as the one that's related to the Textures. If you are using any textures that have multiple resolutions in 1 file. At some point frames begin to slow down. The solution is to stop using that feature and bake your textures to a static file like jpg or png.

I'll open another issue just incase it's not related. Essentially all of the Cosmos objects utilize that multi resolution textures, So none of the Cosmos objects are usable (as is) if you're going to do anything beyond 4+ frames.

[imdb]

Try changing GI engine from Light Cache to Brute Force. So you'll have Brute Force + Brute Force. It seems to be solving the issue from my limited test.

[haniel1107]

Try changing GI engine from Light Cache to Brute Force. So you'll have Brute Force + Brute Force. It seems to be solving the issue from my limited test.

I will test it,, would be great if this works... as it is a real time killer... thanks

[sirio76]

Essentially all of the Cosmos objects utilize that multi resolution textures, So none of the Cosmos objects are usable (as is) if you're going to do anything beyond 4+ frames.

Hi, I've rendered 90 frames over night using Cosmos Assets and .tx texture files, I've not experienced any slowdown. If this can help to isolate the problem I've rendered locally on MacOS, R21, latest Vray build.

[imdb]

Great, haven't tested it on Mac. I send it to a distributed rendered running on Windows w/ GPU card. So the issue I run into is with GPU + Light Cache on Windows latest nightly (stable) build.

Here's a test project link. By frame #6 is when it all starts, typically its 1 minute render / frame on the 1st 5 frames. Then it goes to 2 then 3 minutes and then 12+.

Project:
https://drive.google.com/file/d/1lHm...ew?usp=sharing

BF render:
https://drive.google.com/file/d/1Krq...ew?usp=sharing

Nothing too fancy going on in there, except # of these textures.