hello
I have got a problem here with using an empty volume grid (y value 0.01 in smoke graph) to make depth haze alongside some VDB clouds loaded into volume grids and when I introduce geometry I get weird cut outs. I have transparency on 1000 and ray depth on 10.
using vray NEXT
any ideas here?
image attached
It works in volumetric geometry mode for the clouds but is so so so slow its not viable for me and needed to increase transperancy to like 4000 …
Hmm, this sounds like quite a lot. Can you send over the scene so we can profile it?
Thank you,
Yep cool here it is - https://www.dropbox.com/s/ulrwngauy0…_test.rar?dl=0
Just need to relink the cloud VDB with the volume grid
In your scene you’re using Phoenix FD along with Volume Grid and that’s why you need to use Volumetric Geometry mode.
If you stick to only Volume Grid or only Phoenix nodes you can render only in Volumetric mode which should be quite a lot faster.
Note that if you do need render elements you will have to use Volumetric Geomery mode unfortunately.
Thanks Georgi - to confirm you cannot have a scene that uses a combination of Phoenix and Volume Grids in volumetric mode? Ill test again today and see if I can get it rendering quicker.
Yes, mixing Volume Grid and Phoenix FD requires Volumetric Geometry mode.
I’m getting undhandled exceptions on this when trying to render at 1920 x 1080 at production settings.
The VDBs arent that big (500mb) and there is only one of them instanced around 12 times but the memory use is insane (but still fits within my 128gb - leveling out at about 90gb)
is this expected behaviour? Seems to be the combinations of Volume Grid fog and Volume Grid VDBs that are doing weird things
Im hoping to get this on render farm by tomorrow night to render over weekend!
Hey,
Can you try running the scene with the latest V-Ray version? Yesterday we have released an update.
If the issues are still reproducible, please send over the scene as I couldn’t reproduce them both in here.
Thank you,
I cant upgrade the entire farm, will take a while to get the IT systems to upgrade it. Sending over another project with the same issues…
Ok here is another one with this issue…
I have phoenix smoke sims loaded into Volume Grids but they seem to reveal lights behind occluded objects. This is a new scene has no overall haze like the last one either…stuck for ideas Am I doing something stupid here? Have tried on 2 computers, one older dual xeon and this newer threaddripper using Vray Next update 1.1
There are 2 cameras in this file both doing the same thing, you need to relink that .AUR file into the grid. Can anyone else reproduce it or have trouble with these?
Scene files (should be uploaded in 15 mins)
https://www.dropbox.com/s/n1u1iukzbc…olume.rar?dl=0
resetting the renderer doenst fix it, nor does upping transperancy levels to 5000
interestingly when i switch to GPU it works, but is super slow (2 x 2080 using NVLINK) and I only have a CPU farm to render this one…
I installed the new ‘vray_adv_41003’ on my home workstation to see if helped but same issues persist on both scenes.
double post
Hey, looks like you hit a bug when you have more than a few instances of VolumeGrid or Phoenix in the scene.
I’ve logged it in our bug tracker and I’ll update the thread when we have something on that.
Thank you,
Great thanks, I use a lot of volume grids and phoenix in my work so would be great to get fixed - I have moved these 2 over to Redshift for the time being where its working OK with the same scene.
any update on this? have another smoke / fog heavy job coming up and would like to try and do it on vray GPU / chaos cloud.
thanks
Hey,
Can you try to update your V-Ray to the latest version. The fix should be in V-Ray Next, Update 2. If you wish to use Phoenix instead - you will need to get a latest nightly build of it as well.
Cheers,
