I have saved out a volume sequence using the USD Export SOP. When I go to the folder that contains the VDBs for this USD file, I notice that they only consist of even numbers. This is causing issues in other software, as it expects the filename and the current frame to correspond, so now my VDB is skipping in and out of existence on every frame.

Did I mess something up when exporting? How can I fix this issue? Thanks in advance.

Hey, did you found any solution to that ?

I'm going crazy with it, USD export in SOP is doing it, USD rop in LOP is doing it, and geometryclipsequence in LOP is doing it (even worst, it put each frame in a subfolder).

For now the only way I found is to do it in two seperate "job", first cache as usual as a .vdb sequence, and THEN create an USD from that sequence, but it's not optimal in our pipeline.

Olivier_Antignac
Hey, did you found any solution to that ?

I'm going crazy with it, USD export in SOP is doing it, USD rop in LOP is doing it, and geometryclipsequence in LOP is doing it (even worst, it put each frame in a subfolder).

For now the only way I found is to do it in two seperate "job", first cache as usual as a .vdb sequence, and THEN create an USD from that sequence, but it's not optimal in our pipeline.

No solution, I have RFE'd it and SideFX are aware of the issue. For now I'm doing the same thing as you are, caching a regular VDB sequence through the File Cache SOP instead.

khomatech

Olivier_Antignac
Hey, did you found any solution to that ?

I'm going crazy with it, USD export in SOP is doing it, USD rop in LOP is doing it, and geometryclipsequence in LOP is doing it (even worst, it put each frame in a subfolder).

For now the only way I found is to do it in two seperate "job", first cache as usual as a .vdb sequence, and THEN create an USD from that sequence, but it's not optimal in our pipeline.

No solution, I have RFE'd it and SideFX are aware of the issue. For now I'm doing the same thing as you are, caching a regular VDB sequence through the File Cache SOP instead.

Alright, I'll do that extra step then, it's a bit annoying so it need to send two jobs with dependencies in the farm but at least it works like that. Thanks for the quick answer !

Olivier_Antignac

khomatech

Olivier_Antignac
Hey, did you found any solution to that ?

I'm going crazy with it, USD export in SOP is doing it, USD rop in LOP is doing it, and geometryclipsequence in LOP is doing it (even worst, it put each frame in a subfolder).

For now the only way I found is to do it in two seperate "job", first cache as usual as a .vdb sequence, and THEN create an USD from that sequence, but it's not optimal in our pipeline.

No solution, I have RFE'd it and SideFX are aware of the issue. For now I'm doing the same thing as you are, caching a regular VDB sequence through the File Cache SOP instead.

Alright, I'll do that extra step then, it's a bit annoying so it need to send two jobs with dependencies in the farm but at least it works like that. Thanks for the quick answer !

No problem. Maybe you can also send them an RFE to draw a bit more attention to this issue.

You could try adding the usdvolumesavepath attribute in SOPs to specify the output path for the VDBs.

https://www.sidefx.com/docs/houdini/solaris/sop_import.html#vols [www.sidefx.com]