OTOY Forums

Yambo wrote:Also, what is the problem on mix materials that been fixed?

Yes it should be stable on plugin side. Because i'm using same core of 2.25 build. Difference is the Renderer side.
Btw, there was a problem that mix materials has not been not updated when you changed the linked materials.

Fun time with the fog volume object and some emission

Lovely test Yambo,

I can't believe how fast volumes render, it's amazing.
I'm running into an issue though, I'm getting a position wobble in these new versions with Houdini VDB's, I thought this was fixed in previous versions?
Clip:
https://www.dropbox.com/s/0ob8ztb00t7d4 ... e.mov?dl=0

Thanks

ryzej wrote:Lovely test Yambo,

I can't believe how fast volumes render, it's amazing.
I'm running into an issue though, I'm getting a position wobble in these new versions with Houdini VDB's, I thought this was fixed in previous versions?
Clip:
https://www.dropbox.com/s/0ob8ztb00t7d4 ... e.mov?dl=0

Thanks

I'm not sure that's fixable. It's blackbox the loading VDBs by Octane SDK. Just disable sub domain optimisations in Houdini. It limites the Voxel volume to minimum bounding boxes. So this may cause shaking effect. I have fixed same issue for TFD conversions.

Just disable sub domain optimisations in Houdini. Where would I find this option? I will test.
Thanks aoktar,

Ahmet i'm not familiar also with this option in Houdini. If you could point us that could be great.

It is about the resize nodes, e.g. Gas Resize Fluid Dynamics etc. This containers go with the real size of the sim, not the domain size. This is to minimize the massive simulation tasks, RAM usage and others. You can delete these nodes but with the assurance of massive RAM usage.

Since it already worked in older Octane versions, I'm sure Otoy will reimplement it so no deletion of these nodes will be necessary in the future with release of v3.
Right, Ahmet?
Edit: I probably should ask the standalone core team ^^

ryzej wrote:Lovely test Yambo,

I can't believe how fast volumes render, it's amazing.
I'm running into an issue though, I'm getting a position wobble in these new versions with Houdini VDB's, I thought this was fixed in previous versions?
Clip:
https://www.dropbox.com/s/0ob8ztb00t7d4 ... e.mov?dl=0

Thanks

This is most likely due to a bug that has just been fixed in Octane - there was an issue when importing VDBs with origins very far from the origin. Bear with us while we make the next release ready.

Hi Guys,

Really nice progress on V3 thanks!

I seem to be stuck with something that I don't remember happening before- When I render to the picture viewer the first time in a session it loads and renders fine. However I have found that the next time I render to picture viewer it always fails. The only workaround I have found is to load to the the live viewer before each time I render to picture viewer. It also happens when I render using the render queue- the first scene/job renders fine then the second always fails. This is quite frustrating when rendering multiple scenes as I have to check back and set each render manually.

Sorry I can't upload a file as its under NDA, I will try and replicate a simple file however it seems to happen on any scene. Any ideas would be greatly appreciated!

C4D R17 Mac os x 10.11.2 / Alpha 6.1 / standalone alpha 6 / CUDA Driver Version: 7.5.26

Here is the log report -

FRAME 25 fps:30 camMb:0 objMb:0
Triangles:900k Disp.triangles:0 Hair count:0 Mesh count:143
VRAM used/free/max:784Mb/3.015Gb/4Gb Movable:143 Nodes:312
device 0: can't bind to render thread (0x0) in scope of other thread (0x7ff461a9c9b0)
device 1: can't bind to render thread (0x0) in scope of other thread (0x7ff449409b80)
<<< Render Failure >>>
--------------------------- EXPORT LOG ---------------------------
Export materials time= 11635.875 ms
Collect objects time= 0.861 ms
Mesh creation time = 2583.227 ms.
device 0: can't bind to render thread (0x0) in scope of other thread (0x7ff44f810f30)
<<< Render Failure >>>
device 1: can't bind to render thread (0x0) in scope of other thread (0x7ff44f811130)
Triangles:6.313m Disp.triangles:0 Hair count:0 Mesh count:145
VRAM used/free/max:2Kb/3.826Gb/4Gb
Total export Time = 183619.462 ms

joecurrie wrote: Export materials time= 11635.875 ms
Collect objects time= 0.861 ms
Mesh creation time = 2583.227 ms.
device 0: can't bind to render thread (0x0) in scope of other thread (0x7ff44f810f30)
<<< Render Failure >>>
device 1: can't bind to render thread (0x0) in scope of other thread (0x7ff44f811130)
Triangles:6.313m Disp.triangles:0 Hair count:0 Mesh count:145
VRAM used/free/max:2Kb/3.826Gb/4Gb
Total export Time = 183619.462 ms

So that's the way. See export times. 183sec is too long. That's clear something is big and you should find what's that.