OctaneRender for DAZ Studio 3.02 [OBSOLETE]

[gaazsi]

mh latest update caused a bunch of network render problems again, often loosing the connection to slaves during the render itself... and the message heartbeat stopped, stopping slave.
and slaves cant be seen in that new network window, sometimes un- and rechecking network rendering helps, sometimes not. same problem as it was some versions ago

[face_off]

mh latest update caused a bunch of network render problems again, often loosing the connection to slaves during the render itself... and the message heartbeat stopped, stopping slave.
and slaves cant be seen in that new network window, sometimes un- and rechecking network rendering helps, sometimes not. same problem as it was some versions ago

Make sure your network slaves are using Octane Standalone alpha 3. What Nvidia drivers do you have installed your master and slaves?

Paul

[gaazsi]

alpha 3 running on both slaves and on main rig driver version is 359 on all 3 rigs as well, had some crash problems with 361 so i moved back to 359. that issue happened since the last ocds update.

all 3 rigs are running win7 64bit, 3x 2 gtx 980 ti cards used

sometimes its running fine, sometimes he finds just 1 of 2 slaves, then i have to restart the demon on the other one and everything is fine again, sometimes that rechecking of network rendering helps and sometimes (but very rare) it happens that one slave drops during renderprocess itself. not able to reproduce it atm, seems pretty random

any other information that i could provide on log files or something? elsewhere i could move back to the last version and octane alpha2 meanwhile maybe, just as note that something seems going weird, at least for me.

[face_off]

alpha 3 running on both slaves and on main rig driver version is 359 on all 3 rigs as well, had some crash problems with 361 so i moved back to 359. that issue happened since the last ocds update.

all 3 rigs are running win7 64bit, 3x 2 gtx 980 ti cards used

sometimes its running fine, sometimes he finds just 1 of 2 slaves, then i have to restart the demon on the other one and everything is fine again, sometimes that rechecking of network rendering helps and sometimes (but very rare) it happens that one slave drops during renderprocess itself. not able to reproduce it atm, seems pretty random

any other information that i could provide on log files or something? elsewhere i could move back to the last version and octane alpha2 meanwhile maybe, just as note that something seems going weird, at least for me.

All sees to be in order. I will post an alpha 4 build in a few hours - perhaps see if that fixes the issue, and if not, report the problem to Otoy on the Octane Standalone 3 alpha 4 thread.

Paul

[Notiusweb]

Al-pha-4!
Al-pha-4!
Al-pha-4!

May the Fourth-ce be with us all

[gaazsi]

alpha 3 running on both slaves and on main rig driver version is 359 on all 3 rigs as well, had some crash problems with 361 so i moved back to 359. that issue happened since the last ocds update.

all 3 rigs are running win7 64bit, 3x 2 gtx 980 ti cards used

sometimes its running fine, sometimes he finds just 1 of 2 slaves, then i have to restart the demon on the other one and everything is fine again, sometimes that rechecking of network rendering helps and sometimes (but very rare) it happens that one slave drops during renderprocess itself. not able to reproduce it atm, seems pretty random

any other information that i could provide on log files or something? elsewhere i could move back to the last version and octane alpha2 meanwhile maybe, just as note that something seems going weird, at least for me.

All sees to be in order. I will post an alpha 4 build in a few hours - perhaps see if that fixes the issue, and if not, report the problem to Otoy on the Octane Standalone 3 alpha 4 thread.

Paul

problem solved, everything running flawless again after updating to alpha4 edit: and i noticed that the live view update is automatically disabled now when closing the viewport, makes things a loooot easier... this plugin is going to be more and more top notch meanwhile

[itou31]

Thanks Paul for the alpha4.
I can now switch back to the plugin V3, as the last alpha 3 freeze due to my system PCIe X1. The alpha4 Standalone and plugin are more stable.
I can see that you have not fixed the resize issue --> still increase geometry memory even the textures memory decrease, so at the final, the scene takes more VRAM than if not resized !
Else, the speed of the V3 is great compared to V2 (for ex : 1min55 on V2 --> 1min22 on V3 with parallel sample =12 / tiles = 32)

[face_off]

I can see that you have not fixed the resize issue --> still increase geometry memory even the textures memory decrease, so at the final, the scene takes more VRAM than if not resized !

On which panel is the memory being incorrectly reported? The Textures panel or the System panel?

Paul

[Notiusweb]

Postby itou31 » Thu Feb 04, 2016 10:39 pm
Thanks Paul for the alpha4.
I can now switch back to the plugin V3, as the last alpha 3 freeze due to my system PCIe X1. The alpha4 Standalone and plugin are more stable.

Hi itou31, are you seeing that scenes that froze upon using OcDS 3.1 - 3.3 are now not freezing on 3.4? I actually am testing now more myself, and I am finding that there are freezes whenever the scene has any resolution-challenging elements, namely hair, at high res rendering. This is an anecdotal statement, I realize, however I am in a nutshell still seeing the freezing. It is not relegated to camera baking on standalone, it involves high res renders across the board. I am interested to what degree you feel you are are seeing less. For example, you had a scene that repeatedly froze on 3.1 - 3.3, but never on 3.4. Maybe I could share a freeze-scene with you via PM (ocs or orbx) and you could run and see if freezes?

Paul, FYI - I am posting on the main development build regarding this issue, as it extends beyond this plugin. I have found I can actually reproduce the freeze with any 1 of my Titan Z cores (1x) alone, as in only 1 is needed to cause crash. I have 2 scenes with demanding hair texture that cause this issue. I noted these scenes, as expected, slow the render down, as opposed to a simpler scene with less demanding textures. What do you think, or know, it is that makes high res hair scenes more demanding in general, vs let's say a simple geometry primitive. Is it displacement, like a greater surface area of geometry that needs to be computed? I think the more I understand what it is that makes such scenes more demanding, the more I can drill down what 'provokes' the freezing, and reproduce a simplified scene for Marcus. Thanks so much, for everything!

[Hydra]

I'm getting a Daz crash on Octane Export.

I'm using 3.0.4.10 in Daz 4.8.0.59. Full Octane is 2.23.2 (Am I supposed to update this to something newer?). Nvidia drivers are 347.09.

I'm able to render in Daz, but I often export images and variants and crunch them outside of daz.