OctaneRender 4 for DAZ Studio [TEST and STABLE] [OBSOLETE]

[rajib]

Similar to this can I ask an option to clean up the environment setting and render settings list drop down ? I have scene files with way too many render setting and environment setting listed as i experimented with the settings and saved them.

Can't you just select the Environment and click the X button to delete it?

Paul

Thanks Paul for pointing it out ! I think I must have gone blind !!! Never noticed it ! I just opened DAZ Studio to check and lo and behold it was there. My bad !

[larsmidnatt]

I just did a test. For me the Final mode was very slightly faster than the normal render.

thanks for trying. i'm still getting about half the Ms with final render as opposed to regular, and this is with totally different characters and environment and all of that. might have to spend more time tinkering to see if i can figure it out.

[larsmidnatt]

Regular(non-final) rendering with both cards is always faster than with one, but final render is slower with two cards depending on my settings. I have discovered by lowering the OOC memory setting it has increased the final rendering speed.

I think the issue I am having with final render is related to the new OOC changes. Speculation. But in the past I never adjusted my 8GB OOC memory or overhead setting and final render with my two cards was always faster. I reduced to OOC memory setting from the 8 gb I've had it set to for years, down to what I really use, around 4gb.

Anyway simplified numbers (total render time is estimated time to hit 4k)

8GB OOC tested to 500 samples
1070 alone 4.8
1070 Final 8.4 (7:57 render time)
1070+1060 6.5
Both Final 7.3 (8:34)

4GB OOC tested to 500 samples
1070 alone 4.9 (12:35)
1070 Final 7.2 (8:44)
1070+1060 6.5 (9:43)
Both Final 9.15 (6:58)

BTW, I'm not really worried about the small fluctuations between tests. for example the 1070 solo final times in both tests are just directional and meant to compare against the other settings. I know the exact moment you hit 500 may have different speed numbers, but I think the estimate times are usually a decent judge of time (even though they aren't 100% either)

The only times I would really look at are the final render speeds when both cards are enabled.

also using the texture reduction feature within OCDS seems to greatly help render speeds in final render now. So I definitely think the OOC memory + final render are what is causing the slowdown for me with my two gpu. though, yuck the results aren't what i want

[face_off]

Regular(non-final) rendering with both cards is always faster than with one, but final render is slower with two cards depending on my settings. I have discovered by lowering the OOC memory setting it has increased the final rendering speed.

I think the issue I am having with final render is related to the new OOC changes. Speculation. But in the past I never adjusted my 8GB OOC memory or overhead setting and final render with my two cards was always faster. I reduced to OOC memory setting from the 8 gb I've had it set to for years, down to what I really use, around 4gb.

Anyway simplified numbers (total render time is estimated time to hit 4k)

8GB OOC tested to 500 samples
1070 alone 4.8
1070 Final 8.4 (7:57 render time)
1070+1060 6.5
Both Final 7.3 (8:34)

4GB OOC tested to 500 samples
1070 alone 4.9 (12:35)
1070 Final 7.2 (8:44)
1070+1060 6.5 (9:43)
Both Final 9.15 (6:58)

BTW, I'm not really worried about the small fluctuations between tests. for example the 1070 solo final times in both tests are just directional and meant to compare against the other settings. I know the exact moment you hit 500 may have different speed numbers, but I think the estimate times are usually a decent judge of time (even though they aren't 100% either)

The only times I would really look at are the final render speeds when both cards are enabled.

also using the texture reduction feature within OCDS seems to greatly help render speeds in final render now. So I definitely think the OOC memory + final render are what is causing the slowdown for me with my two gpu. though, yuck the results aren't what i want

I don't think this is related to the plugin - it is more an Octane Standalone issue - so I suggest posting in the Octane Standalone 4.01.1 release thread.

Paul

[larsmidnatt]

Makes sense. I'm noticing other weirdness too, like rendering at 6ms one frame and then the next frame of the animation is 0.45. but if i restart the animation on that frame it will run at 6 again.

but yeah a octane issue. oh wells.

[larsmidnatt]

more testing. seems like restarting daz studio fixes the issue. at least sometimes. (i haven't gone back to retest all prior scenes that ran into this)

ill keep an eye on this going forward.

EDIT: Even more testing. sometimes the Ms just tanks after a while even without final render. restarting fixes it. this is def new to the 4.x version. never had my Ms just dive on me in prior releases.

as painful as it is to restart (and wait for all those darn textures to reload) at least there is a workaround.

historically i would be able to keep daz open for several hours, render out dozens of different renders and not have to relaunch. but I guess those days are over.

[face_off]

more testing. seems like restarting daz studio fixes the issue. at least sometimes. (i haven't gone back to retest all prior scenes that ran into this)

ill keep an eye on this going forward.

EDIT: Even more testing. sometimes the Ms just tanks after a while even without final render. restarting fixes it. this is def new to the 4.x version. never had my Ms just dive on me in prior releases.

as painful as it is to restart (and wait for all those darn textures to reload) at least there is a workaround.

historically i would be able to keep daz open for several hours, render out dozens of different renders and not have to relaunch. but I guess those days are over.

Have you checked the Octane Log when this happens?

Paul

[larsmidnatt]

Have you checked the Octane Log when this happens?

Paul

I thought I had something for you, but I don't. I ran into the issue again, and saw this in the log...but its the same message i see when I relaunch daz actually. (attached) Notce the double scroll bars ^_^

Was rendering around 17Ms, then after i rotated a figure it tanked to 2.5Ms. Had been working for an hour or two I guess.

Relaunched daz and it went back to 17.4Ms

Daz Studio Pro 4.10.123 | OCDS 4.0.0.41| NVIDIA Driver 417.35
cards listed in my sig

I guess no one else is having the issue. Which is fine. I'll work through it. too many configs out there. I was initially posting just in case others had the issue to help get more info.

It tanking when rendering an animation is painful though. I'm not working on an animation for this project, but my next one was going to need it. I may report more then if needed cause I could see it being a project killer if it continues then.

[face_off]

I thought I had something for you, but I don't. I ran into the issue again, and saw this in the log...but its the same message i see when I relaunch daz actually. (attached) Notce the double scroll bars ^_^

Make sure you scroll the window to ensure you are seeing all the log messages. I'm not sure if the "Invalid data count..." error is coming from the plugin or Octane, but my guess is it is the later, so if you delete your Octane preferences, that may resolve it (there are in one of the folders under C:\Users\[username]\AppData\Roaming\OctaneRender).

Paul

[larsmidnatt]

Make sure you scroll the window to ensure you are seeing all the log messages. I'm not sure if the "Invalid data count..." error is coming from the plugin or Octane, but my guess is it is the later, so if you delete your Octane preferences, that may resolve it (there are in one of the folders under C:\Users\[username]\AppData\Roaming\OctaneRender).

Paul

thanks. yeah I did show you the entire log. i deleted the preferences and that didn't change anything. I tried to science the hell out of the issue but its not getting me anywhere. While i can replicate the issue pretty easily, its not 100% of the time. the final render and insane reduction in rendering speeds seem unrelated too.

I moved back to 3.07 and it is fine, so its not hardware related. I'll stick with that for now.