Hi Chris

Thank you for your answer!

To give you more context, we try to read volumetric files from OpenVDB via texture3D(), so we need to provide it some arguments like:

- The name of the VDB file, which can hold many grids

- The name of the grid we want to read: "Density", "Heat", "LevelSet", ...

- Some lookup options, like using multi-resolution or not, some multiplicative scale on the filter size, access to the min/max grid useful for the tracking algorithm...

- Eventually the name of some metadata we would like to retrieve from the file

Actually it's ok, because as you said it, there is always an argument of texture3D we can use to provide additional informations, even if this could lead to several call to texture3D() for the same file.
We just wanted to know if there was a better way to do it, but we can deal with that.

Thank you again for your time.

Kind regards,

Zab