Page 9 of 44

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Mon Jan 18, 2016 9:29 pm
by face_off
Since after Daz 4.6 + plugin 2.x, the Daz Studio has been really really really slow for even moderate scenes. Is this a known issue? And which is it coming from? Daz 4.8 or plugin 2.(later)/3.0? Has anyone else noticed the dramatic slowdown?
What is slow? Rendering or the DAZStudio GUI? If the later, when is it slow (Octane Viewport open or closed?). Do you have a separate card as your Windows display adapter? What hardware are you running?

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Mon Jan 18, 2016 9:34 pm
by face_off
I still haven't use the Octane version because of the fireflies issue. Is this issue still present ?
There are no firefly issues specific to the DAZStudio plugin that I am aware of. Have you tried reducing the GI Clamp? The Octane Notes link in my signature contains more info.

Paul

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Mon Jan 18, 2016 11:49 pm
by AlfaseeD
face_off wrote:
I still haven't use the Octane version because of the fireflies issue. Is this issue still present ?
There are no firefly issues specific to the DAZStudio plugin that I am aware of. Have you tried reducing the GI Clamp? The Octane Notes link in my signature contains more info.

Paul
I tried the 3.0 version as soon as it was available and I got a good number of fireflies, so I was "forced" to switch back to the 2.24 (same scene, same everything, no fireflies at all).
Yes, I tried to reduce the GI clamp, but without any real success.
The best thing I can do is trying this version and in case be more precise if I still have this problem.
I will let you know!

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 3:58 am
by face_off
I tried the 3.0 version as soon as it was available and I got a good number of fireflies, so I was "forced" to switch back to the 2.24 (same scene, same everything, no fireflies at all).
Yes, I tried to reduce the GI clamp, but without any real success.
The best thing I can do is trying this version and in case be more precise if I still have this problem.
Try the latest version, and if it is still an issue post the problem in the Octane Standalone 3.0 alpha 3 thread which some samples showing the problem so that the Otoy devs can see the issue.

Paul

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 7:24 am
by SiliconAya
A small request:

Do you think we can have the extremely annoying confirmation pop up box you get, whenever you try and save, asking about saving unused materials, removed please? I don't believe I've ever used a program that has interrupted saving over halfway through, saving should just work, always, or if there's an error, like a read only file, it should instantly notify at the start.

I regularly have unassigned materials when I'm working on a scene and/or testing materials and I like to save regularly and not be asked to confirm/be punished every time I do. Maybe make it into a options in prefs with a default of yes or something, as I think I've only selected no once or twice ever and I don't think it worked anyway.

Thanks.

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 10:15 am
by face_off
I regularly have unassigned materials when I'm working on a scene and/or testing materials and I like to save regularly and not be asked to confirm/be punished every time I do. Maybe make it into a options in prefs with a default of yes or something, as I think I've only selected no once or twice ever and I don't think it worked anyway.
It probably makes sense to always save the unused materials, since you can always delete them if you don't want them saved. I will put this in the next release.

Paul

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 5:59 pm
by Spectralis
face_off wrote:
I regularly have unassigned materials when I'm working on a scene and/or testing materials and I like to save regularly and not be asked to confirm/be punished every time I do. Maybe make it into a options in prefs with a default of yes or something, as I think I've only selected no once or twice ever and I don't think it worked anyway.
It probably makes sense to always save the unused materials, since you can always delete them if you don't want them saved. I will put this in the next release.

Paul
Could you also add this to v2 as well? That would be really helpful. Save all unused materials as default just in case they are needed in future maybe with the option to switch this off for those who prefer this? Do the saved unused materials use up VRAM?

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 6:14 pm
by linvanchene
edited and removed by user

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 7:15 pm
by jimgale
Entirely the GUI. Rendering is fast. Even 'selecting' an item in Daz, or moving it, or changing a parameter takes 1-5 seconds (5 to get the yellow highlight, 5 to actually select, 5 to recognize the click on a parameter, 5 more to let me edit it, 5 to accept the change, 5 to register the change, etc). Really bad. This was a significant change from 4.5 + 2.(older x) Octane. Obviously, I don't know where the real issue is and am wondering if others are noticing it too.
face_off wrote:
Since after Daz 4.6 + plugin 2.x, the Daz Studio has been really really really slow for even moderate scenes. Is this a known issue? And which is it coming from? Daz 4.8 or plugin 2.(later)/3.0? Has anyone else noticed the dramatic slowdown?
What is slow? Rendering or the DAZStudio GUI? If the later, when is it slow (Octane Viewport open or closed?). Do you have a separate card as your Windows display adapter? What hardware are you running?

Re: OctaneRender for DAZ Studio 3.0.3 [TEST]

Posted: Tue Jan 19, 2016 10:58 pm
by face_off
Entirely the GUI. Rendering is fast. Even 'selecting' an item in Daz, or moving it, or changing a parameter takes 1-5 seconds (5 to get the yellow highlight, 5 to actually select, 5 to recognize the click on a parameter, 5 more to let me edit it, 5 to accept the change, 5 to register the change, etc). Really bad. This was a significant change from 4.5 + 2.(older x) Octane. Obviously, I don't know where the real issue is and am wondering if others are noticing it too.
Does this happen before you open the Octane Viewport, or only after? Does it happen on simple scenes, or just complex?

Paul