brainspoon
Hi,

I'd like to export my Maya fluid simulation as OpenVDB sequence to render it with Redshift renderer. I installed BE_OpenVDB and it seems to be running, but when adding a BE_VDBFromMayaFluid node to the scene where I set the correct fluid shape name and connecting it to a BE_VDBWrite node, nothing gets saved.

Do I miss something to make it work?

Many thanks in advance.

Andreas
Quote 0 0
brainspoon
Seems like the write node does not work. Connecting the BE_VDBFromMayaFluid to a visualizing node shows that it gets the data from the maya fluid. Just no file gets written.
Quote 0 0
ourouk
Try that : 

BE_VDBFromMayaFluid -> BE_VDBWrite -> BE_VDBVisualize

Should write some vdb somewhere :)
Quote 0 0
brainspoon
Thanks. Seems the BE_VDBVisualize was the missing part.
Quote 0 0
AlexRideout
From a scripting standpoint, you can force evaluation to get it to write too. I usually use pymel

from pymel.core import *
write=PyNode('BE_VDBWrite1')
write.VdbOutput.evaluate()

You might be able to also force it with a getAttr command for the VdbOutput attribute. Basically the Visualize node forces the output to evaluate, and these are just ways to do it without needing to connect another node.
Quote 0 0
ourouk
Good to know.
thx AlexRideout
Quote 0 0
manusito

hi!

right now this is overwriting the same file every frame, even though the time node is connected to it. When I set the file name to something like "test_####.vdb" it doesn´t even write the file. Is there any workaround for this?

edit: if I press "next frame" it will evaluate it and save it correctly, the problem is just when I press play for the whole duration.

edit2: I am retarded, as AlexRideout´s code will solve this. Thanks!!!!

Quote 0 0
doodlerboy
I'm having issues with my fluid sim. 

I keep getting this error. 

// Error: There is no fluid node with the given name. // 

here's my connection link up
I'm in Maya 2016 SP6 Click image for larger version - Name: vdb.jpg, Views: 46, Size: 295.90 KB
Quote 0 0
manusito
Make sure in the vdbfromMayaFluid you type exactly the name of the fluid you are trying to export (attribute editor). By default it would miss a 1 at the end.
Quote 0 0
glasseyevfx
Is there any problem with doing an upresFluid and using it in the BE_VDBFromMayaFluid ? I'm having some problems getting it to write out. Also does the vdb hold onto the upresFluid nodes info that is created?
Quote 0 0
pshipkov
There shouldn't be a problem with that. Will check and clarify tomorrow (getting late here).
Try to turn-off the PE evaluation mode. That usually helps.

Not sure what do you mean with "VDB hold onto the upresFluid info".
Can you elaborate please ?
Thanks.
Quote 0 0
pshipkov
Also, which version of Maya and which OS ?
Quote 0 0
glasseyevfx
I used AlexRideout's script I that enabled me to step one frame at a time to get a file out but it didn't update correctly - the first half of the seq was like 3kb and the second half 45mb with a frozen caches.

"VDB hold onto the upresFluid info" I mean that the upres system creates an extra node of data that includes the 'resolution multiplier' as well as duplicating the original maya fluid. I'm curious as to if that extra data is updating a standard node so the information is used in the export or if it ignores the extra data or if it might be causing a problem with the export.

I'm using maya 2018 on a windows 7 box - thanks for the quick reply
Quote 0 0
pshipkov
Can you share that script you are using, so i can have your starting point ?

Did you cache the original fluid container ?
Quote 0 0
glasseyevfx
not really - Its for an active project.

Basically I'm using maya nParticles to emit fluids which I'm then soup upresing before exporting to vdb for rendering in redshift.
If I cannot get the vdb I'll have to maya render or drop the upres.
I should also say that with the upres I also cached it out for quick playback (which seems fine)
Quote 0 0

Add a Website Forum to your website.