Arnold refusing to render cached VDB after specific frame

[just_bob_2nd]

Hello,

I'm distributing my pyro sim across 4 machines and caching it afterwards to be rendered in Arnold. I'm using object merge to load the slices directly from the splicer, convertvdb SOP to convert the volume to VDB (would like a confirmation if it's really needed with the new volume sourcing workflow), vdbvectormerge SOP to merge all 3 velocity volumes into a single one and then the primitive SOP to write the vdb as a 16bit float, after which comes my file cache sop. Everything works fine for the first 24 frames, but for some reason arnold won't render any vdb after frame 1104. Arnold appears to load in the files, only to hang on me at Generating scene for an eternity. All the vdbs appear fine in the viewport for the entirety of the frame range (1080-1150). Size-wise, files look fine aswell (2gb for frame 1104 and 2.1gb for frame 1105). I am not hitting the memory limit or any warnings/errors either. It doesn't seem to be scene dependent either as I've tried loading it in a new simple scene and getting the same issues and I'm kinda out of troubleshooting ideas.

Thanks in advance

[just_bob_2nd]

Apparently the issue was in the velocity fields themselves and deleting them made arnold happy, so we settled on camera motion blur. As to why he didn't mind those same fields in any previous frames remains a mistery to us. 

[Lucy Coleclough]

It's probably autodesk's fault

[lawrencen]

Hot Damn we have been banging our head on the wall trying to figure out why our renders are stopping at a certain frame and hanging. This thread solved it for us. Thanks!

and yes, 100% AD fault.