Hi Tyson,
I've already reported this bug but the support mailbox seems to have a problem...
This bug occurs only after creating a first tyFlow node or when reloading a scene file.
When the event is the first one initializing a VDB grid with a birthVDB operator set on "initialize new vdb",
the VDBCopyOut operator causes max to crash. (at least for v0.16088/89 on max2018 win7)
So to prevent this I first have to initialize a new VDB grid in a "dummy" event evaluated prior to the rest of my flow.
this flow crashes
this one doesn't
I've already reported this bug but the support mailbox seems to have a problem...
This bug occurs only after creating a first tyFlow node or when reloading a scene file.
When the event is the first one initializing a VDB grid with a birthVDB operator set on "initialize new vdb",
the VDBCopyOut operator causes max to crash. (at least for v0.16088/89 on max2018 win7)
So to prevent this I first have to initialize a new VDB grid in a "dummy" event evaluated prior to the rest of my flow.
this flow crashes
this one doesn't