Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
ruchit

Cooking networks
Registered:
Posts: 156
Reply with quote  #1 
Hi,
here is quick solution to export mayaFluid as VDB using openVDB plugin by Evgeny.

vdbExport.png 

    Usage:
    -----------------------------------------------------
    1). Put vdbExport.py in C:\Users\xxxxxxxx\Documents\maya\xxxx\scripts

    2). Inside maya script editor(python TAB). Run this

       
Code:

import sys
        sys.path.append('C:\Users\xxxxxxx\Documents\maya\xxxx\scripts')
        import vdbExport
        reload(vdbExport)
        vexprt = vdbExport.vdbExportUI()
        vexprt.show()


    3). Select Fluid container and hit load.
    4). Add element name.
    5). Set start/End Frame.
    6). On/Off fluid channel to export.
    7). Done

 
Attached Files
zip vdbExport.zip (2.18 KB, 92 views)

0
omento

Asking for seconds
Registered:
Posts: 23
Reply with quote  #2 
Hi Ruchit! Thanks for the script, although I seem to be getting an error that's preventing runtime. I've tried this multiple times, even using the actual script in the editor, but no dice, always this error:

Code:
# Error: line 1: unexpected indent


I've gone through the script with Sublime Text, and the only place that uses non-spaced indents or tabs is in a commented section where you tell us what to do.


Update:
I've tried just about every variation of Windows / Unix characters ('\' and '/') and indents throughout the initiation script to now avail. Any help would be appreciated.
0
ruchit

Cooking networks
Registered:
Posts: 156
Reply with quote  #3 
Due to extra space added in post, you r gettin error, Try this.

Code:

import sys
sys.path.append('C:\Users\xxxxxxx\Documents\maya\xxxx\scripts')
import vdbExport
reload(vdbExport)
vexprt = vdbExport.vdbExportUI()
vexprt.show()
0
omento

Asking for seconds
Registered:
Posts: 23
Reply with quote  #4 
Still nothing. Here's the output:
  
vdbExportError.PNG

vdbExportErrorP2.PNG 

0
omento

Asking for seconds
Registered:
Posts: 23
Reply with quote  #5 
I've also shared this on the Redshift forums, and a question was brought up:

Quote:
Wonder if it still works if you add some other nodes in between like remap.


Any input on this?
0
ruchit

Cooking networks
Registered:
Posts: 156
Reply with quote  #6 
Try this,

 
Attached Files
zip vdbExport.zip (2.17 KB, 62 views)

0
userv28

First taste
Registered:
Posts: 2
Reply with quote  #7 
for maya 2017 doesn't work, has new python bindings, pyside2, has to be rewritten :(
0
ruchit

Cooking networks
Registered:
Posts: 156
Reply with quote  #8 
Try this for 2017

 
Attached Files
zip vdbExport_2017.zip (2.17 KB, 141 views)

0
userv28

First taste
Registered:
Posts: 2
Reply with quote  #9 
awesome, thank you so much!
0
omento

Asking for seconds
Registered:
Posts: 23
Reply with quote  #10 
That fix worked beautifully Ruchit. Redshift users also reported success with this non-indented version.

I've also found the just starting at `import vdbExport` in the initiation script works as long as the script is in a known place for Maya, like 201X\scripts, prefs\scripts, or maya\scripts, etc
0
ruchit

Cooking networks
Registered:
Posts: 156
Reply with quote  #11 
Good to know that it's working. Enjoy
Use sys.path.append if script is not @ proper place.
0
omento

Asking for seconds
Registered:
Posts: 23
Reply with quote  #12 
Got it. I haven't gotten the chance to test it fully yet, but does your script support nodes past the fluidshape? Like if I pipe the FluidShape into a VDBfromFluid then into a remap node (or other configuration) then to a Write node/Visualize node, will it retain all of that info? Or does it go straight from FluidShape > Export?

Thanks for the script!
0
djx

Node Bending
Registered:
Posts: 221
Reply with quote  #13 
Since no one mentioned it... This will not work in python due to the \ used in the path.
sys.path.append('C:\Users\xxxxxxx\Documents\maya\xxxx\scripts')
Use / instead and you should be ok.

David
0
ruchit

Cooking networks
Registered:
Posts: 156
Reply with quote  #14 
@omento

I would like to suggest you, use my script to export maya fluid (without cache) as VDB & then do whatever VDB operation you like to add on top of it.

Mostly i avoid simultaneous calculation Bcz it makes workflow slow :( may be i have superstitious.
0
theartofsaul

First taste
Registered:
Posts: 8
Reply with quote  #15 
Can someone update this for Maya 2017?
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation: