OTOY Forums

I'm trying to use VDBs created with FumeFX for Maya rendered within Octane for Maya and I am unable to select different grid mappings on the octane Volume node, or I cannot find the button to press to allow this to happen. I can change the grid mapping in octane standalone without any dramas.

It appears to be rendering the FireFuel channel.

Is this another feature that hasn't been implemented? It'd be really great to have some form of documentation for Octane for Maya.

Hiya,

Are you still having the issue selecting the grid mappings? Please try importing from File menu> Import > set the files of type OctaneRender-VDB then select the .vdb file.

Here are few documentation links of Octane for Maya plugins:

https://docs.otoy.com/Maya_Plugin_Manua ... Manual.htm

https://help.otoy.com/hc/en-us/sections ... 79486-Maya

I hope you will find the information useful.

Thank you for the quick response. Importing the VDB into freshly opened maya scene works and gives me access to the volume channels.

There is still a bug that occurs if you create the volume node through the hypershade in a new maya instance, Then point it to the VDB those channels are not selectable even if you the go and try to import a vdb through the import menu afterwards.

steps to reproduce.

1. Open a fresh maya
2. open hypershade and create a volume node
3. select a vdb sequence

No drop down menus will be present on each of the channels.

Workaround: Do not use the hypershade to create volume Nodes, use the import menu from the Maya File dialog.

if you import a VDB through the import menu it appears to fill all the channels available from the selected vdb and keeps that information in Maya i.e if you create a new scene in a Maya session that has already had a vdb imported into it and create a volume node through the hypershade the dropdown menus are available from the previously imported vdb. I would assume that the octane volume node is not re-reading the available channels from the VDB when you select the file in the browse dialog of the volume node, hence once the node is created it doesn't re-read any channel data from the selected vdb not updating the available channels. I can see this causing issues in the future if you were to select a different vdb from another source with different channel data (a vdb from houdini for example) I dont have such a vdb to test my assumption unfortunately.

Also thank you for the link to the documentation I didn't know that existed.

Thanks Again!
Juri

Hi Juri,

Thank you so much for your kind response and detailed steps to reproduce the issue.

We will start investigating on this and hope to get it fixed in our next release.