OctaneRender 3 for DAZ Studio [TEST and STABLE] Tweet

[thricegift]

Paul,
The delay is about a second or so, as you said. But note, no other GPU render engine I use has this delay in the viewport (including Iray and the standalone Octane); they all update instantaneously on my dual 1080 Ti's. It is only the Octane plugin that has this delay, which seems to suggest that there is a communication bottlenck between DS and Octane.

If you want, I can do a screen capture for you and post the recording comparing the two. It is enough of a delay to discourage one from using Octane, as live feedback is important to workflow (and Octane has long been known to deliver live feedback in the viewport... so I don't know how this can be described as normal). For the amount of money one pays to obtain this plugin, I don't think this should be happening.

Thanks again for all your hard work,

-P

[vortex3d]

This is a general Octane question - so you might get a more accurate answer in the Octane Standalone release forum. However my understanding is that the transmission will remove the color you define, so the resulting light emitted form the other side of the surface wilwl be the opposite color. You might be better using a Specular material with a Scatter node, which will give more control over how light is dispersed whilst it travels through a body.

Paul

I will play with the Specular material's Scatter node. As always great work on the plugin, and thank you for the prompt reply.

[face_off]

The delay is about a second or so, as you said. But note, no other GPU render engine I use has this delay in the viewport (including Iray and the standalone Octane); they all update instantaneously on my dual 1080 Ti's. It is only the Octane plugin that has this delay, which seems to suggest that there is a communication bottlenck between DS and Octane.

If you want, I can do a screen capture for you and post the recording comparing the two. It is enough of a delay to discourage one from using Octane, as live feedback is important to workflow (and Octane has long been known to deliver live feedback in the viewport... so I don't know how this can be described as normal). For the amount of money one pays to obtain this plugin, I don't think this should be happening.

A one second delay is to be expected for some operations, since the plugin may need to be re-loading a Genesis mesh into your graphics card.

Paul

[thricegift]

A one second delay is to be expected for some operations, since the plugin may need to be re-loading a Genesis mesh into your graphics card.

Paul

Perhaps I was not clear. I am referring to simple viewport operations, like Pan, Zoom, Orbit, etc. I assume this does not require re-load of geometry, since the geometry did not move. Octane Standalone does not have a 1 second delay, nor does Iray. So I assume they do not have to re-load meshes into the GPU memory for simple viewport operations like this. Could not OcDS also be programmed to do the same? Or perhaps this is a limitation of being a plugin (i.e., more steps to calculate)?

I should note, one of the reasons why I bought Octane in the first place was because of its long-time reputation of fast viewport feedback. This has always been one of the hallmark features of Octane---something that made it stand out from other GPU render engines through the years. It therefore seems very important that the plugin performs the same way.


-P

[face_off]

Perhaps I was not clear. I am referring to simple viewport operations, like Pan, Zoom, Orbit, etc. I assume this does not require re-load of geometry, since the geometry did not move. Octane Standalone does not have a 1 second delay, nor does Iray. So I assume they do not have to re-load meshes into the GPU memory for simple viewport operations like this. Could not OcDS also be programmed to do the same? Or perhaps this is a limitation of being a plugin (i.e., more steps to calculate)?

I can see NO delay when rotating, panning or zooming the camera, EXCEPT when the DAZStudio viewport is rendering via Iray - which is to be expected.

Paul

[thricegift]

I can see NO delay when rotating, panning or zooming the camera, EXCEPT when the DAZStudio viewport is rendering via Iray - which is to be expected.

Paul

Hmmm... I wonder if I am the only one experiencing this latency. Even with a blank scene with no objects in the scene, there is a slight delay between camera movement and OcDS viewport feedback (thus preventing OcDS from being realtime). With a large scene, this delay is exacerbated.

In the version of OcDS I have, there is an option for "Plugin Latency."---the smallest value available is 100ms. I wonder if this is causing the delay I am experiencing.
Can this value not be set to 0?

-P

[thricegift]

Paul,
I made a quick video to demonstrate the latency I am referring to. Hopefully this clarifies what I wrote above. Thanks again for looking into this.

https://youtu.be/R34B0gWF-qU

[itou31]

Hi,
Just check this issue.
My latency is not slow as yours, showed in the video. not as fast as standalone but about less than one second at the first move and then it get faster. If I move slowly the daz viewport, the octane viewport refresh more smoothly (but still a delay as expected (100ms or 200ms).
Same behaviour with one or more GPU.
Bigger scene has more delay at the beginning (as said Paul) but then the refresh "seems good enough"

[thricegift]

Hi,
Just check this issue.
My latency is not slow as yours, showed in the video. not as fast as standalone but about less than one second at the first move and then it get faster. If I move slowly the daz viewport, the octane viewport refresh more smoothly (but still a delay as expected (100ms or 200ms).
Same behaviour with one or more GPU.
Bigger scene has more delay at the beginning (as said Paul) but then the refresh "seems good enough"

It seems that mouse movement affects the delay. Try continuing to orbit your mouse like I did in the video. Notice how the viewport does not update until you stop moving the mouse, after which the 100ms delay seems to initiate. Can you confirm this?

Something seems to be wrong, as this is not expected behavior on dual 1080 Ti's----especially not Octane. It should be buttery smooth like with Iray.

-P

[face_off]

Something seems to be wrong, as this is not expected behavior on dual 1080 Ti's

I cannot reproduce the problem you are having. If the camera is not immediately updating, it is because DAZStudio is not immediately sending camera update events to the Octane plugin. Sorry I cannot offer a better explanation. Pls keep in mind that the host app is free, so will not be as refined as more expensive higher-end 3d apps.

Paul