HHbomb wrote:Hi, I have a problem with this version and some before.
I have already reported it.
When I have instanced proxies, when I set one ( for eg ) not visible to camera, sometimes it works, sometimes no. Specially when you re-open your file or clear objects in globel settings.
see pict. Very very annoying, when you mix seen and unseen trees in a render.
Please, it is important.
coilbook wrote:When will be this vdb bug fixed? Thanks
I mentioned here viewtopic.php?f=80&t=74816&start=40
paride4331 wrote:coilbook wrote:When will be this vdb bug fixed? Thanks
I mentioned here viewtopic.php?f=80&t=74816&start=40
Hi coilbook,
SDK developers made changes on the step length of the medium node.
I had some test with bunny.vdb I got good results multiplied by two.
So the solution is to have the Step length value higher then before.
I hope it helps.
OctaneRender Enterprise 2020.1.3 (8010300)
Can't connect node 'oDiff_07 - Default' (NT_MAT_DIFFUSE, 00000194C78AC5A0) to static pin 'layer' (P_LAYER, type PT_MATERIAL_LAYER) of node 'Universal material' (NT_MAT_UNIVERSAL, 00000194C78A5640)
CUDA error 2 on device 0: out of memory
-> failed to allocate device memory
mbetke wrote:I still have problems with NVLINK. Latest drivers...all latest WIN10
Using 512MB Head Room, 64GB out of Core. 2/4 Parallel Samples/Max tile samp.
Scene would need around 24GB of VRAM. With two Titan RTX it should work.
- Code: Select all
OctaneRender Enterprise 2020.1.3 (8010300)
Can't connect node 'oDiff_07 - Default' (NT_MAT_DIFFUSE, 00000194C78AC5A0) to static pin 'layer' (P_LAYER, type PT_MATERIAL_LAYER) of node 'Universal material' (NT_MAT_UNIVERSAL, 00000194C78A5640)
CUDA error 2 on device 0: out of memory
-> failed to allocate device memory
Users browsing this forum: No registered users and 4 guests