besha1 Show full post »
limeforce
Hm, still cannot load the plugin on my Win10 laptop & Maya 2016, getting 

"The specified procedure could not be found. (BE_OpenVDB)"

like I did a couple of months back. Similar installation has been working just fine on a Win 8.1 machine. Anyone using this successfully on Win10? If I can get a confirmation it should work I can shift my troubleshooting elsewhere :)

Quote 0 0
besha1
ourouk wrote: Hello besha1,

Would it be possible to be able to use maya env variables in BE_VDBArnoldRender.volumePath ?

Something like : 
$PATH\vdb\blablabla.vdb

instead of 
D:\user\project\asset\publish\vdb\blablabla.vdb

with 
$PATH = 'D:\user\project\asset\publish'

Trying to do that leads me to an ERROR : 
// Error: file: D:/openVdbForMaya/scripts/AEBE_VDBArnoldRenderTemplate.mel line 327: Item not found: density


It works with AiVolume :/
Thanks again


already did
and now you can render directly from the scene


replace BE_OpenVDB.mll
replace AEBE_VDBArnoldRenderTemplate.mel

for mtoa
replace BE_VDBArnoldRenderTranslator.dll in C:\solidangle\mtoadeploy\2016\extensions

replace aiBE_VDBArnoldRender.dll
in C:\solidangle\mtoadeploy\2016\shaders

rename original volume_openvdb.dll to volume_openvdb_ORIG.dl and put my volume_openvdb.dll 
in C:\solidangle\mtoadeploy\2016\procedurals

only for maya 2016 win for now





Quote 0 0
besha1
ourouk wrote: Re,

Here is some kind of a bug with BE_VDBArnoldRender.

I want to remap the density.

So in the smoke section I check the remap checkbox and play with the BE_VDBArnoldRenderShape1.DensityRamp[1].DensityRamp_FloatValue
It works fine.

Adding a key or a connection to that value is correctly updated in Arnold renderView ( IPR or not )

BUT when I remove the key, the value seems broken.
The render is no more updated when I change DensityRamp[1].DensityRamp_FloatValue manually.

Adding a key again, make the ramp works again.

Any idea ? evalution bug ? Maya ? Arnold ? BE_VDBArnoldRender ?

Thx

PS : I can create a "open vdb bugs" threads in the bug section if you want or stick with that thread.

in arnold render View
to version 1.2.7.3 had problems right now, no
check in maya render View

Quote 0 0
besha1
limeforce wrote: Hm, still cannot load the plugin on my Win10 laptop & Maya 2016, getting 

"The specified procedure could not be found. (BE_OpenVDB)"

like I did a couple of months back. Similar installation has been working just fine on a Win 8.1 machine. Anyone using this successfully on Win10? If I can get a confirmation it should work I can shift my troubleshooting elsewhere :)



I'm still on Windows seven
check
in system variables PATH= C:\Program Files\Autodesk\Maya2016\bin;C:\solidangle\mtoadeploy\2016\bin;

and install microsoft visual c++ redistributable 2012 x64
https://www.microsoft.com/ru-RU/download/details.aspx?id=30679 

today, I checked on Windows 10 is working fine
Quote 0 0
ourouk
Thx a lot besha1 for the update !
Everything works perfectly ;)
Quote 0 0
plars
In maya 2016 SP5, after a bit of experimenting with the various nodes, the dropdowns for grid name selection unexpectedly stops responding to changes. For example, I have a VDBFromPolygons outputting density and surface grids. In the following nodes it was previously set to surface. Now when I select density and refresh the AE, it's back to surface. I'm wondering if this is normal, and if so, what the best way to avoid it is.
Quote 0 0
besha1
plars wrote: In maya 2016 SP5, after a bit of experimenting with the various nodes, the dropdowns for grid name selection unexpectedly stops responding to changes. For example, I have a VDBFromPolygons outputting density and surface grids. In the following nodes it was previously set to surface. Now when I select density and refresh the AE, it's back to surface. I'm wondering if this is normal, and if so, what the best way to avoid it is.
in what are the nodes this happens?
or give me the scene 
I'll see


Quote 0 0
plars
besha1 wrote:
in what are the nodes this happens?
or give me the scene 
I'll see


I open this scene ( mb openVDB_adv_1.1.mb      ) and try to change BE_VDBActivate1's Source to density. When I refresh the AE, it's still on *. I noticed that saving the scene and re-selecting the node seems to fix it. Maybe it's just a problem with my installation of Maya.
Quote 0 0
besha1
Quote 0 0
AlexRideout
Great to see a bifrostToArray node! Finally may be able to mesh bifrost with VDB instead of the internal mesher.
Quote 0 0
oktawu
Having a strange issue with the tools on maya 2016 sp6. Everything loads fine, but nothing shows up on screen, not even with the default legacy mode. The weird part is that after loading a vdb file using the BE_VDBRead node, the outliner remains empty and the node "OpenVDBVisualize" is missing. And there are no errors that i have seen in the command line or in the script editor.

Does anyone have any idea what could be the problem?
Quote 0 0
rolfcoppter
Is this out in the newest release? This is amazing news because the internal mesher is brutal.
Quote 0 0
besha1
Quote 0 0
besha1
rolfcoppter wrote: Is this out in the newest release? This is amazing news because the internal mesher is brutal.
Quote 0 0
plars
Very interesting Besha! In the Soup to Mtoa video you are rendering the Soup displayComponents in Arnold as if it were a particleShape by adding a series of attributes? How/why does that work? Arnold is looking for those specific attribute names?

One other question if you don't mind. When it comes to activating voxels with the activate node. What purpose does activating/deactivating voxels have? I notice you use it quite a bit in your videos. Say you are advecting with a velocity grid. Should it be done before or after advection, and if before, should it be done to the source and velocity grids? I've been going through the official Openvdb docs, but have had some trouble understanding specific applications in Maya.
Quote 0 0

Add a Website Forum to your website.