OctaneRender for DAZ Studio 3.02 [OBSOLETE]

Mon Dec 28, 2015 11:22 am

Hi,
form beta version 2 of the Octane for DAZ plugin through stable version 2 till test 3 version I encounter same problem which makes this plugin completly usless in my case. The thing is when I open viewport popups with warning keep showing up one after another with exactly same message "One ore more GPU(s) seem to be degraded; probably because of a Nv Driver crash!". The funniest part is that rendering process is running with no issues even if this popups show up. This messages keep showing up even after I close the viewport and make using DAZ studio impossible because stack of popups blocks the interface.

Here is sample debug entry from log file with message from popup:
2015-06-10 20:56:11.922 8228 b4850 One ore more GPU(s) seem to be degraded; probably because of a Nv Driver crash!

I have two GPUs GeForce GTX 650Ti and GeForce GTX 750Ti. Previously used Win 7 Home 64-bit now have Win 10 Home 64 bit. The issue has occured on both systems.

I also have a licesne for Poser plugin and I have no issues with Poser version of the plugin used on same computer.

Please help me to resolve this issue.

Mon Dec 28, 2015 11:31 am

One ore more GPU(s) seem to be degraded; probably because of a Nv Driver crash!

I will see if I can suppress that warning message in the next release.

Paul

Mon Dec 28, 2015 11:35 am

Thank You, that would be great! Could it be done also in stable version 2 of the plugin?

Mon Dec 28, 2015 11:48 am

Thank You, that would be great! Could it be done also in stable version 2 of the plugin?

It can....however I'd prefer to release stable 2.24.2 versions of the plugin on perhaps a quarterly basis - since it is a lot of work developing the Octane 3 version and also releasing Octane 2 versions.

Paul

Mon Dec 28, 2015 11:53 am

Thank You Paul, I understand. I waited so long, so waiting couple of months more makes no difference for me

Mon Dec 28, 2015 12:02 pm

I waited so long, so waiting couple of months more makes no difference for me

May I suggest you use the Octane 3 version of the plugin. It is quite robust.

Paul

Mon Dec 28, 2015 10:40 pm

When I started using 3.0 I started to get driver crashes from rendering really simple things (and I seem to get a lot more noise then before for some reason). I thought it might be driver related, even though mine are up to date. I switched back to version 2 and have not had problems since. I'll give the next V3 release a try.

Tue Dec 29, 2015 9:19 pm

Paul, this is pretty wild stuff we're able to do with the Medium sliders!!! Love it.
My only hope is that the 3.0 engine itself gets better speed and UI performance as it undergoes development. The (1) render speed and (2) smoothness of pan, rotate, and zoom in the standalone UI with multiple GPU was better in V2, and the sliders offered to adjust performance to memory never get it to the V2 performance level...But granted this is a standalone engine thing, not an OcDS thing. (I haven't tried OcDS 3.0 with 12 GPU yet....)
The software may be outgrowing the hardware, just V2 did it so fast, so we're spoiled now.

Although, in V2 I couldn't do this! :

: I am Goddess of the light... now how do I shut myself off...

: I AM the Christmas Tree

Wed Dec 30, 2015 5:20 am

Paul, this figure's skin maps aren't coming over properly, please fix...

: The render looks like hell...

: Wait, never mind...figured it out...Perfect ! ! !

Wed Dec 30, 2015 6:14 am

Just FYI - tested with the 12 GPU and can confirm the greater UI viewport lag (pan, zoom, rotate) is there in V3 OcDS, same as V3 standalone. And likewise, the lag was not there in V2 of standalone or OcDS.
When active count of GPUs is reduced to just 1 GPU, it is very smooth and responsive. The lag is linearly increased as you add up to 12, and linearly decreased as you bring down to 1. Worst I've seen is like a 2 second lag, but in V2 it wasn't there and was always almost instantaneous.

Also just FYI - I asked Abstrax in the main developmental build forum if they can't match the UI responsiveness of V2 (matching the way GPUs spoke to the app), if they could create a workflow improvement of having a hotkey which would instantly allow us to toggle between 2 or more active GPU profiles. In my case I would set one having 1 GPU (for posing), and a second for 12 GPU (for rendering), instead of having to go back and forth checking and unchecking the little GPU boxes.