besha1 Show full post »
ourouk
Yep sorry, I didn't see you released a new version 2 days ago. I downloaded it, maybe 3 days ago :)

Will retry with the last version and go back to you.
Thanks a lot !
Quote 0 0
ourouk
Ok it worked, thanks a lot.


Here is some notices :

BE_VDBArnoldRender :
Loading a 24 Mo vdb take about 50 seconds ( only 1 frame vdb )
Adding a density layer take about the same.
Changing frame, idem.

Loading a 2 Mo vdb take about 5 seconds ( only 1 frame vdb )
Adding a density layer take about the same.
Changing frame, idem.

AiVolume :
Loading the same vdb : small, file size independant
Adding density grid : small, file size independant
Changing frame : small, file size independant


It's difficult to use with such "hanging" times.
Any idea ?
thx

Quote 0 0
besha1
very very strange
even considering that, I record video
I have no such results
only crawler.vdb weighing 454 mb loaded in 42 seconds
the rest of the files are loaded very quickly

https://www.sendspace.com/file/e3k3zz
watch the video at the link above
Quote 0 0
ourouk
Yeah it's strange...
Will try tomorrow again...maybe it's graphic card related...

aiVolume is just displayed as bounding box whereas BE_VDBArnoldRender is by default using "density points" preview...
Quote 0 0
ourouk
Hello,

After copying the 24Mo vdb locally, it takes about 3 seconds to load. There must be some traffic jam on the network here :)
But it's 3 seconds, where AiVolume is about 0 ( locally and on the network )

How can AiVolume load the vdb so quick ? Any Idea ?
Thanks



Quote 0 0
besha1
I don't understand why you have such problems with uploading files
I showed in the video that the file size of 50 - 100 mb downloaded instantly
and compare ArnoldVolume and BE_VDBArnoldRender not correct
ArnoldVolume only receives information from one grid about the bounding box 
BE_VDBArnoldRender  receives information from all grid about the bounding boxes,
information about names grids ,information about data grids
and most importantly displays the active voxels,tiles,leaf nodes,internal nodes, surface
and bounding boxes and so on


Quote 0 0
ourouk
Yeah, the comparison is not correct :)

But I have about 50 vdb (6 different .vdb) in a scene, timeline scrub is impossible with BE_VDBArnoldRender whereas it is realtime with AiVolume and the rendering look is exactly the same.

This is just my point : Even if BE_VDBArnoldRender read a lot more informations from the vdb, the usage feedback is too slow on my workstation (APY Supernova) . Maybe the problem is my side of course, but I don't know where.

I would have prefered to use BE_VDBArnoldRender for sure (I am a SOuP fan and I love VDB in Houdini)

Maybe you should add a "light" mode by defaut ( the same as Arnold, one grid bbox ). It's just a thought, not a demand :)

Quote 0 0
besha1
well, maybe I'll make an option to disable data
Quote 0 0
besha1
ourouk
try this version this for maya 2016
I made some changes in BE_VDBVisualize and BE_VDBArnoldRender
now in my tests 
BE_VDBVisualize and BE_VDBArnoldRender works faster than AiVolume

download and replace your BE_OpenVDB.mll

tell me about the results

Quote 0 0
ourouk
Hello, sorry for the delay. Couldn't manage to find the time to replace a .mll this week :)

I did it this morning, it's faaaar better ! 
Could you explain what you changed in this version please ?

thanks a lot :)
Quote 0 0
ruchit
@besha1
Thnx very much for update & here is my short video on openVDB Boolean operation inspired by

Boolean Denting (VDB Basics)

Thnx again for help.
Quote 0 0
besha1
ourouk wrote: Hello, sorry for the delay. Couldn't manage to find the time to replace a .mll this week :)

I did it this morning, it's faaaar better ! 
Could you explain what you changed in this version please ?

thanks a lot :)

this is a test version
changes only BE_VDBVisualize and BE_VDBArnoldRender

previously, all information was loaded regardless of whether visualized or not
now loaded only the information that is needed 
ActiveValueBoundingBox very fast
InternalNodes very fast
LeafNodes very fast
ActiveTiles very fast
Surface slowly
ActiveVoxels slowly

ActiveValueBoundingBox + LeafNodes + ActiveTiles will work faster than ArnoldVolume
Surface and ActiveVoxels slower than ArnoldVolume

if someone says that ArnoldVolume is faster he's mistaken
explain why
ArnoldVolume fast until you entered Frame = frame
while you did not Frame = frame
ArnoldVolume not updated always frame static
if you need this in BE_VDBVisualize or BE_VDBArnoldRender
just disconnect Time.


Quote 0 0
ourouk
Ok thx a lot for those informations
Quote 0 0
ourouk
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
Quote 0 0
ourouk
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.
Quote 0 0

Add a Website Forum to your website.