OTOY Forums

FORUM 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 entering 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
(6) Object Motion Blur
(7) Export of Male Gens Hip Textures from plugin to full Octane not working.

WORKAROUNDS:
(1) Unwanted Pixelated ‘Toonish’ Textures – Occurs because material parameter for Normal Map is set to "2" by auto-material. Set it to “0”

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.)

Good posts for updating this list!
Since we are seeing other OTOY members viewing and posting in this forum, any additions or comments should in some way also help us platform what we'd like to have improved/changed. If you want to see something, comment away!

Thanks for this very concise list. It provides a systematic way to identify problems and deserves a sticky in the OcDS forum until these issues have been addressed.

bepeg4d wrote:weird behavior, I need to do some more tests
ciao beppe

Also, if it helps, the DAZ Studio version I'm running is 4.8.0.59 Pro 64bit

Also I tried to reinstall the OS on the slave from scratch but the situation is still the same - standalone works immediately, OcDS can see the slave but it is still in the "OFF" state

Moar animation test for those interested:

http://render.otoy.com/forum/viewtopic. ... 40#p243446

This time testing camera focus and instances.

Cheers!

Hi birdovous,
I have done some more tests and I am in the opposite situation, I can't stop the slave in any way, clicking on the "ON" button the slave stops just for a couple of seconds and then restart rendering. The only way is to quit the slave app
I have also installed the standalone demon for checking that it was not this to blocking you, but it works perfectly, even too much in my case
ciao beppe

bepeg4d wrote:Hi birdovous,
I have done some more tests and I am in the opposite situation, I can't stop the slave in any way, clicking on the "ON" button the slave stops just for a couple of seconds and then restart rendering. The only way is to quit the slave app
I have also installed the standalone demon for checking that it was not this to blocking you, but it works perfectly, even too much in my case
ciao beppe

OK... It looks like it is a bug after all. I mean - I finally made it work and it looks like there is a problem with the net code of the plugin (since standalone works fine).

My Slave node has single network card, my Master workstation however, has several network cards connected to different segments. All the time the master and Slave are in the same broadcast domain but during 'normal' configuration all the plugin can see is the temperature of the Slave cards and the slave is listed as "OFF". When I disable all the network cards on the Master except the one connected to the slave network the Slave flips to "ON" and the plugin starts using the GPUs in the Slave machine.

Since this does not happen with the Standalone, which simply works, I think the plugin has a bug in the netcode which has problem with exotic network configurations (multiple enabled network cards).

So hooray the plugin can see the slave and can use the cards there to boost the rendering speed.

The bad news is, that it looks like the master sends only geometry (probably with diffuse color data) to the slave and no textures so as the render starts and the slave starts sending data, the resulting image in the OcDS viewport starts to get very washed out.

So with a workaround to one issue I'm now facing another one


1000 s/px, PMC, Master node only


1000 s/px, PMC, Master and Slave

Notiusweb wrote:FORUM 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 entering 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
(6) Object Motion Blur
(7) Export of Male Gens Hip Textures from plugin to full Octane not working.

WORKAROUNDS:
(1) Unwanted Pixelated ‘Toonish’ Textures – Occurs because material parameter for Normal Map is set to "2" by auto-material. Set it to “0”

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.)

Personally I would add:
ISSUES:
(8) Network rendering does not work if the Master node has more than one network card present and active.

FEATURE REQUESTS:
(2) Add Out of Core support to network render Slave nodes.

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
(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.

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"

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.

Thanks to Birdovous for testing and adding to list.

Everyone, when you get a chance, type out any Workarounds you have so we can consolidate them to our list. All I can think of is the material ones with the normal map, and setting eye moisture's opacity to 0 when using Iray texture eyes.

Looks like I have found another bug:

Adding a keyframe to the White point element in the Rendersettings tab results in an instant CTD with no error message.

Can anyone else please try it and confirm the above? Thanks.

birdovous wrote:Looks like I have found another bug:

Adding a keyframe to the White point element in the Rendersettings tab results in an instant CTD with no error message.

Can anyone else please try it and confirm the above? Thanks.

yes confirmed, same behavior also here.
ciao beppe