OTOY Forums

Do you mean - rename this files or another option? Where should I paste this value - "Default_$F.vdb"?
Thanks.

promity wrote:Do you mean - rename this files or another option? Where should I paste this value - "Default_$F.vdb"?
Thanks.

In the filename. Put this expression in the OpenVDB file parameter and the plugin will replace the $F token by the current frame. BTW. there is an additional parameter to set a frame offset for this token.

Thanks,
-Juanjo

Thank you.

I do not understand anything - I create a scene in which there is a null object and a sequence of VDB files. I make the settings, everything works well, Octane sees the sequence. Then I load the object with VDB stquence from this scene into the scene with my character etc - nothing happens. Octane does not display these volumetrics. But if I load the same object from the VDB sequence into an empty scene, everything works well. What's the secret?





Buuut! If I load only one frame of VDB from a sequence, everything works as it should:

Hmm, do you have other Null objects in the scene with this same name? The volume null should have a unique name in the scene to avoid problems with the "Instance LW clones" feature.

Thanks,
-Juanjo

Thank you. I checked - I made a new null object, I gave it the original name, I loaded the sequence of the VDB files - no result. I loaded a separate file - everything is fine.

Can you share the scene with this problem to take a look at it here?

Thanks,
-Juanjo

Yes, I will try.
I am currently working with the 4th version of Octane - can it be that this problem will not happen when upgrading to version 2018?

Hmm, sorry, but I can't find any problem in this scene. If I add a null including the Octane volumetrics, the OpenVDB sequence is loaded without problems. Are you sure that you don't have a problem with the OpenVDB files paths in your scene? Perhaps the relative path is not working or something like that. In the Octane log file you should get a message about what file is trying to load the plugin, and perhaps a warning about a not found file ... something like " - Volume object from the OpenVDB file xxxxxxxxxxxxxxxxxxxx"

Thanks,
-Juanjo

Thanks. I found my problems with the VDB sequence. In the wrong path to the files.