OcDS Setup v2.2 (last Beta)

[Notiusweb]

Was wondering if anyone with multiple GPU notices the temp and TDP of each of their graphics cards rising when merely using the Daz UI viewport (and not with Iray even). So for example, I have a Titan X as the primary display and then external Titan Z cards. At computer idle, they all sit idle. Then I load Google Chrome and the temp and TDP only goes up on the X. Then I load Daz, and all cards across the board go from a 17%TDP to like 30, and the temp up about 15 degrees or so. Then as the scene gets more complex TDP and temp raise. This is not while rendering, but strictly with the Daz viewport. And not even in the Iray render mode.

So, might this be caused by the Daz UI itself, as in it uses all cards across the board? Or maybe the OcDS is run at some level behind the scenes and taxes each card? I ran this by in the Daz forums and I pretty much got that it might be a Daz bug, in that only the main display should be the only card running a power draw. But I figured I should ask my OcDS peers.

Any thoughts would be appreciated, wondering if I should disable all the cards from the OcDS when not rendering, whether that would do anything.
-Regards!

[itou31]

Hi,

Yes I noticed that also for me on all cards. the temperature increase is only about 10°C.
Even when you deselect on the system pane of OcDs.
You can disable cards if they don't need to run all DAZ session.
On my side, I have only 3 titan on the main power supply, the other 5 boards are OFF. If I have a rendering session, I have to turn off the PC, power on the main PC and the extension.
Often we only need one card. So this post let me think that I should write a bat file to disable all unused cards.

[Notiusweb]

by itou31 » Sat Nov 07, 2015 10:36 pm

Hi,

Yes I noticed that also for me on all cards. the temperature increase is only about 10°C.
Even when you deselect on the system pane of OcDs.
You can disable cards if they don't need to run all DAZ session.
On my side, I have only 3 titan on the main power supply, the other 5 boards are OFF. If I have a rendering session, I have to turn off the PC, power on the main PC and the extension.
Often we only need one card. So this post let me think that I should write a bat file to disable all unused cards.

Hi itou31,
Thanks so much for letting me know your experience. I actually operate similarly as well, where I do not power on the external Zs, given I have them attached via external PSUs, and I just run with the primary X. Then when rendering, I power down pc, power on PSUs and load them all in, much like you described. I was curious if this was the necessary step in order to not tax all the cards, but it appears this is the case. It would be cool, like you mentioned, to have a front end which could be loaded in order to disable the cards when definitely not being used. Although, what kind of havoc might that cause with the control panel/registry. (We had to work hard to get these things running to begin with, right? )

(FYI - Itou31 and myself are involved in another forum involving non-Daz specific multi-GPU discussions.)

[birdovous]

Just an update post:

FORUM LIST FOR OcDS V2.2FORUM LIST FOR OcDS V2.2

ISSUES:
(1) Materials Conversion - problems converting materials from Daz to OcDS (Iray materials not supported, materials not converting, mesh collision causing blotches, issues related to creation of 'Mix Material', etc.)
(2) Plugin Stall - upon repeated selection/use of materials in OcDS, or when selecting 'Reload'>'Rebuild Scene' tab, sometimes plugin no longer functions, grayed out...cannot create 'New' scene in Daz, can only load 'Recent' or close down
(3) Mouse sometimes maintains priority of focus, even when it shouldn't (such as when typing information in a text field), and may lose it when it shouldn't (not actively switching to whichever section of DS is currently being moused over while not entering text). This can lead to errant interactions with both OcDS plugin and Daz UI
(4) Drop-Down Defaults to 'None' - sometimes when using a node drop-down, and you select something other than 'None", it sets itself as 'None" requiring a second drop-down entry (then it works....)
(5) Camera Motion Blur
- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created
(6) Object Motion Blur
(7) Export of Male Gens Hip Textures from plugin to full Octane not working.
(8) Network rendering does not work if the Master node has more than one network card present and active.
(9) Adding a keyframe to the White point element in the Rendersettings tab results in an instant CTD with no error message.
(10) Different Names for Projection Modes in OcDS and OR standalone.
What is called Mesh UV projection in OctaneRender standalone is called UVW projection in the OcDS plugin.
What is called XYZ to UVW Projection in OctaneRender standalone is called linear projection in the OcDS plugin.
(11) Plugin is missing the panoramic camera node
(12) Final Render Button issues - i.e. you let a render run not realizing the save button was disabled
(13) Scene Loading OcDS Data issue - if you load a scene that had OcDS data in it while the plugin was not enabled, saved it and opened later with OcDS enabled, scene does not retain the OcDS data

WORKAROUNDS:
(1) Unwanted Pixelated ‘Toonish’ Textures – Occurs because material parameter for Normal Map is set to "2" by auto-material. Set it to “0”
(2) Iray Eye Texture gives solid white eyes in OcDS - right click and select 'Eye Moisture' material, set Opacity for this material to "0"
(3) DOF - can change the settings in DAZ but there's no effect in Octane even after re-loading the scene - selecting a camera view should fix your problem.
(4) Octane doesn't save the applied materials, you have to load and apply them every time you open a scene - check your preferences in octane, make sure to read/save .duf. Also, you can save your octane mats as presets (and even templates) to save some time.
(5) Dr. Hemulen's Suggestion for material conversion problem:
Convert to a simple glossy material, but be sure to capture ALL of the textures. Include a bunch of templated materials - skin, eyes, fabric, leather and such with the release. Then just drag and drop them on the simple, auto-generated mats or use your own.

FEATURE REQUESTS:
(1) Highlight empty Image Fields in bright red, as well as the materials in the Octane Material List. If something got left out or lost in a scene would make it easier to see when something is missing. (i.e. - Recent Normal Map issues, and issues like when building a character skin with different face/lip maps ,the lips will have missing Spec or even Bump maps.)
(2) Add Out of Core support to network render Slave nodes.
(3) A button to resize all textures in the texture tab. It would be a real time save for us who render smallish images on smaller cards, instead of having to click each individual texture. A "Default texture size" drop down in Preferences/texture settings would also work
(4) Save texture size settings (i.e. 1/2,1/4 ...) with the file
(5) HDR Lightmaps - adding the functionality that the Poser version has for the HDR Lightmap Plugin.

Network rendering is still bugged and it is supposed to be on this list. Not only the slave does not go to ON mode when the master has more than one ethernet card installed, but when the nodes actually connect and start rendering the resulting render is desaturated as if the slave node was sending the result with all surfaces being flat white. So that is maybe something to add as another point as it may not be related to the two nodes not being able to see each other.

[Notiusweb]

update

FORUM LIST FOR OcDS V2.2FORUM LIST FOR OcDS V2.2

ISSUES:
(1) Materials Conversion - problems converting materials from Daz to OcDS (Iray materials not supported, materials not converting, mesh-plain collision causing artifacts and blotches, issues related to creation of 'Mix Material' (such as Normals Map defaulting to 2, which causes Toon textures in Daylight Environment), etc.)
(2) Plugin Stall - upon repeated selection/use of materials in OcDS, or when selecting 'Reload'>'Rebuild Scene' tab, sometimes plugin no longer functions, grayed out...cannot create 'New' scene in Daz, can only load 'Recent' or close down
(3) Mouse sometimes maintains priority of focus, even when it shouldn't (such as when typing information in a text field), and may lose it when it shouldn't (not actively switching to whichever section of DS is currently being moused over while not entering text). This can lead to errant interactions with both OcDS plugin and Daz UI
(4) Drop-Down Defaults to 'None' - sometimes when using a node drop-down, and you select something other than 'None", it sets itself as 'None" requiring a second drop-down entry (then it works....)
(5) Camera Motion Blur
- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created
(6) Object Motion Blur
(7) Export of Male Gens Hip Textures from plugin to full Octane not working.
(8) Network rendering does not work if the Master node has more than one network card present and active.
(9) Adding a keyframe to the White point element in the Rendersettings tab results in an instant CTD with no error message.
(10) Different Names for Projection Modes in OcDS and OR standalone.
What is called Mesh UV projection in OctaneRender standalone is called UVW projection in the OcDS plugin.
What is called XYZ to UVW Projection in OctaneRender standalone is called linear projection in the OcDS plugin.
(11) Plugin is missing the panoramic camera node
(12) Final Render Button issues - i.e. you let a render run not realizing the save button was disabled
(13) Scene Loading OcDS Data issue - if you load a scene that had OcDS data in it while the plugin was not enabled, saved it and opened later with OcDS enabled, scene does not retain the OcDS data
(14) Materials pane "Export" button exists however does not activate save file dialogue, therefore materials per-session cannot be saved
(15) Network rendering is bugged - Not only does the slave not go to ON mode when the master has more than one Ethernet card installed, but when the nodes actually connect and start rendering the resulting render is desaturated as if the slave node was sending the result with all surfaces being flat white.

WORKAROUNDS:
(1) Unwanted Pixelated ‘Toonish’ Textures – Occurs because material parameter for Normal Map is set to "2" by auto-material. Set it to “0”, or turn off the Normals Map (set to "None")
(2) Iray Eye Texture gives solid white eyes in OcDS - right click and select 'Eye Moisture' material, set Opacity for this material to "0"
(3) DOF - can change the settings in DAZ but there's no effect in Octane even after re-loading the scene - selecting a camera view should fix your problem.
(4) Octane doesn't save the applied materials, you have to load and apply them every time you open a scene - check your preferences in octane, make sure to read/save .duf. Also, you can save your octane mats as presets (and even templates) to save some time.
(5) Dr. Hemulen's Suggestion for material conversion problem:
Convert to a simple glossy material, but be sure to capture ALL of the textures. Include a bunch of templated materials - skin, eyes, fabric, leather and such with the release. Then just drag and drop them on the simple, auto-generated mats or use your own.
(6) Random black-out of rendered scene (Scene is black on OcDS) - try changing camera, and then changing back. Or, in OcDS Render Settings pane, check that Exposure is set to default of 0.6, and check that in OcDS Environment pane, drop down is either Daylight or a non-black RGB Color for the HDRI-texture

FEATURE REQUESTS:
(1) Highlight empty Image Fields in bright red, as well as the materials in the Octane Material List. If something got left out or lost in a scene would make it easier to see when something is missing. (i.e. - Recent Normal Map issues, and issues like when building a character skin with different face/lip maps ,the lips will have missing Spec or even Bump maps.)
(2) Add Out of Core support to network render Slave nodes.
(3) A button to resize all textures in the texture tab. It would be a real time save for us who render smallish images on smaller cards, instead of having to click each individual texture. A "Default texture size" drop down in Preferences/texture settings would also work
(4) Save texture size settings (i.e. 1/2,1/4 ...) with the file
(5) HDR Lightmaps - adding the functionality that the Poser version has for the HDR Lightmap Plugin.

[gaazsi]

thanks for your effort

[Notiusweb]

Look at this

viewtopic.php?f=44&t=49987&start=140

Re: Request for official statement concerning the OcDS plugin
by Goldorak » Wed Nov 18, 2015 10:53 am

OTOY purchased the OcDS source code from t_3. OTOY now owns the DAZ plug-in. This took longer than expected.

t_3 will stay on in advisory capacity going forward.

A new dev (whom we fully trust) will be leading development going forward. This transition is currently underway. We will share further details when everything has been finalized. We hope that will happen shortly now that we are at this point.

Thank you for your patience.

Goldorak
OctaneRender Team


Posts: 740
Joined: Sun Apr 22, 2012 8:09 pm

[Spectralis]

Look at this

viewtopic.php?f=44&t=49987&start=140

Re: Request for official statement concerning the OcDS plugin
by Goldorak » Wed Nov 18, 2015 10:53 am

OTOY purchased the OcDS source code from t_3. OTOY now owns the DAZ plug-in. This took longer than expected.

t_3 will stay on in advisory capacity going forward.

A new dev (whom we fully trust) will be leading development going forward. This transition is currently underway. We will share further details when everything has been finalized. We hope that will happen shortly now that we are at this point.

Thank you for your patience.

Goldorak
OctaneRender Team


Posts: 740
Joined: Sun Apr 22, 2012 8:09 pm

Great news! This is a real commitment to bringing the plugin up to date.

On the bugs side I'm having repeated DS crashes when trying out a few materials on an object. I'm also having problems sometimes entering a search word into the dialogue box of the shaders section. The box won't let me input anything. Not sure what's causing the crashes but they seem to occur after loading about 4-5 different materials in a row.

[face_off]

ISSUES:
(1) Materials Conversion - problems converting materials from Daz to OcDS (Iray materials not supported, materials not converting, mesh-plain collision causing artifacts and blotches, issues related to creation of 'Mix Material' (such as Normals Map defaulting to 2, which causes Toon textures in Daylight Environment), etc.)
(2) Plugin Stall - upon repeated selection/use of materials in OcDS, or when selecting 'Reload'>'Rebuild Scene' tab, sometimes plugin no longer functions, grayed out...cannot create 'New' scene in Daz, can only load 'Recent' or close down
(3) Mouse sometimes maintains priority of focus, even when it shouldn't (such as when typing information in a text field), and may lose it when it shouldn't (not actively switching to whichever section of DS is currently being moused over while not entering text). This can lead to errant interactions with both OcDS plugin and Daz UI
(4) Drop-Down Defaults to 'None' - sometimes when using a node drop-down, and you select something other than 'None", it sets itself as 'None" requiring a second drop-down entry (then it works....)
(5) Camera Motion Blur
- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created
(6) Object Motion Blur
(7) Export of Male Gens Hip Textures from plugin to full Octane not working.
(8) Network rendering does not work if the Master node has more than one network card present and active.
(9) Adding a keyframe to the White point element in the Rendersettings tab results in an instant CTD with no error message.
(10) Different Names for Projection Modes in OcDS and OR standalone.
What is called Mesh UV projection in OctaneRender standalone is called UVW projection in the OcDS plugin.
What is called XYZ to UVW Projection in OctaneRender standalone is called linear projection in the OcDS plugin.
(11) Plugin is missing the panoramic camera node
(12) Final Render Button issues - i.e. you let a render run not realizing the save button was disabled
(13) Scene Loading OcDS Data issue - if you load a scene that had OcDS data in it while the plugin was not enabled, saved it and opened later with OcDS enabled, scene does not retain the OcDS data
(14) Materials pane "Export" button exists however does not activate save file dialogue, therefore materials per-session cannot be saved
(15) Network rendering is bugged - Not only does the slave not go to ON mode when the master has more than one Ethernet card installed, but when the nodes actually connect and start rendering the resulting render is desaturated as if the slave node was sending the result with all surfaces being flat white.

WORKAROUNDS:
(1) Unwanted Pixelated ‘Toonish’ Textures – Occurs because material parameter for Normal Map is set to "2" by auto-material. Set it to “0”, or turn off the Normals Map (set to "None")
(2) Iray Eye Texture gives solid white eyes in OcDS - right click and select 'Eye Moisture' material, set Opacity for this material to "0"
(3) DOF - can change the settings in DAZ but there's no effect in Octane even after re-loading the scene - selecting a camera view should fix your problem.
(4) Octane doesn't save the applied materials, you have to load and apply them every time you open a scene - check your preferences in octane, make sure to read/save .duf. Also, you can save your octane mats as presets (and even templates) to save some time.
(5) Dr. Hemulen's Suggestion for material conversion problem:
Convert to a simple glossy material, but be sure to capture ALL of the textures. Include a bunch of templated materials - skin, eyes, fabric, leather and such with the release. Then just drag and drop them on the simple, auto-generated mats or use your own.
(6) Random black-out of rendered scene (Scene is black on OcDS) - try changing camera, and then changing back. Or, in OcDS Render Settings pane, check that Exposure is set to default of 0.6, and check that in OcDS Environment pane, drop down is either Daylight or a non-black RGB Color for the HDRI-texture

FEATURE REQUESTS:
(1) Highlight empty Image Fields in bright red, as well as the materials in the Octane Material List. If something got left out or lost in a scene would make it easier to see when something is missing. (i.e. - Recent Normal Map issues, and issues like when building a character skin with different face/lip maps ,the lips will have missing Spec or even Bump maps.)
(2) Add Out of Core support to network render Slave nodes.
(3) A button to resize all textures in the texture tab. It would be a real time save for us who render smallish images on smaller cards, instead of having to click each individual texture. A "Default texture size" drop down in Preferences/texture settings would also work
(4) Save texture size settings (i.e. 1/2,1/4 ...) with the file
(5) HDR Lightmaps - adding the functionality that the Poser version has for the HDR Lightmap Plugin.

Hi. I will be looking looking after DazStudio plugin updates moving forward.

The first step will be to get an Octane 2.24.2 version released. I need to know that the 2.24.2 release is as stable as previous releases, so that I know that the build process is working correctly. I will get that release out this weekend.

After that I will look to start addressing the above list. Could I ask someone (preferable ONE person) to prioritise the items in this list. I need the most serious, show-stopping problem which are easiest to fix first, and the lowest priority/hardest to fix problems last. Then I can work my way down the list. Random bugs which are hard to reproduce are going to take a long time to fix, so put them last so they don't hold up the easy fixes. Also, keep in mind that Octane 3 will be released in the near future, and one that happens work on bug fixes will slow down.

Also - if people have test scenes which demonstrate any of the above issues, please send them to me. If I receive a scene which causes an issue, together with an exact set of steps needed in DazStudio to get the error, I can track to the issue much quicker. When describing the steps taken to reproduce an issue, give me the exact keystokes, menu selections, etc.

Thanks

Paul

[gaazsi]

if that priority list is about invested money, then network rendering could be the number one for many of us