VDB doesn't update after missing frame

[ptunstall]

I'm offsetting VDB caches with `padzero(4,$F-32)` so if a cache is from 1 TO 84 it won't reach frame 1 till frame 31. Obviously it won't find frames to render till then but this seems to cause it to never update again even once it gets to these frames or past. I've since re-cached the VDBs to be offset on the disk so I'm dumping a bunch of dummy VDBs. Is this a glitch/bug or is this just the nature of the beast that is Octane?

[juanjgon]

I suppose that the problem is that if a volume object is missing in the first frame, the node is never created, so it can't be updated. In this case, configuring the rendering to "Full scene reload" mode should fix the problem.

Thanks,
-Juanjo

[ptunstall]

Yea I'm working with a unique scene that has no texture or geometry updates that renders in ~1:30 a frame. Setting it to full scene reload would shoot the render time up to about ~7 mins a frame with all the reloading of 69 2k textures and heavy geo.

[juanjgon]

Hmm, yep, sorry, in this case, you are going to need a dummy volume for the first frame, or render the sequence using two frame ranges (perhaps configuring two ROPs?). I'll try to find a solution to this issue, but I'm not sure how easy it is going to be ...

Thanks,
-Juanjo

[ptunstall]

I gotcha, no worries this is a low priority situation and there's an easy userside workaround to it.