OcDS Setup v2.2 (last Beta)

[birdovous]

yes confirmed, same behavior also here.
ciao beppe

Thank you

By the way, do you have any idea (or guess), why the network render (in my case) gets so desaturated?

It actually looks that all that gets transferred to the slave node is just geometry and the node is rendering a grayscale 'clay' image which then gets mixed with the output of the master node.

[bmosalt]

Tue Jun 09, 2015 6:53pm
PS: i'm going to be present in the forum during the next two weeks (means after i had added some details about this release),
so whatever you have to say or ask - this will be the time.

Sat Jun 06, 2015 12:13am
We will make sure communication regarding the road map is more frequent and consistent - at least every few weeks, if not more often, until it is out of beta.

So it's been about 7 weeks. When do the "details" get added and when does t3's two week presence begin? And by my calculations we're due two or three "road map" communications.

[birdovous]

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.

Here is one more confirmed bug:

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

[linvanchene]

minor stuff that I reported a while ago and confirmed by t_3:

@ Different Names for Projection Modes in OcDS and OR standalone.

It seems 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.

The functionality seems to be the same but the different naming has confused users trying to follow the OctaneRender standalone manual instructions for IES lights that suggests to use Mesh UV projection.

- - -

Not reported because more feedback by other users is needed:

@ Camera Motion Blur.

- HDR background has no camera motion blur at all
- When the camera is rotating no camera motion blur is created

Camera Motion Blur is allready on the list but at least to me it is not quite clear if those specific observations are bugs or working as intended.
Working as intended would mean that it is the same in OR standalone and OR simply is not supporting such functionality in the current version.


compare:

http://render.otoy.com/forum/viewtopic.php?f=44&t=49118

Other users please experiment with this and add your results.

- - -

@ Exporting scenes with animated camera data to OctaneRender standalone

I noticed that when trying to export a test scene as ORBX from OcDS to OR standalone all animated camera data was not included.

I was under the impression when we use ORBX to export scenes from OcDS to OR standalone all animated data should be included.
As far as I understood it for all animated objects alembic files are created and included in the ORBX.
From that point of view it would seem odd if animated camera data would not be included in the ORBX file?!

compare:

http://render.otoy.com/forum/viewtopic.php?f=44&t=49315

Other users please experiment with this and add your results.
Did you notice other animated OcDS parameters that are not included when exporting animated OcDS scenes to OR standalone?

- - -

[MyRho]

Sorry - I didn't read this whole thread so some problems I've found maybe reported earlier...:

1: DOF doesn't work at all (path tracing, HDRI) - I can change the settings in DAZ but nevertheless there's no effect in Octane even after re-loading the scene.

2: Octane very often (almoset EVERY) time doesn't save the applied materials so I have to load and apply them every time I open the scene...

3: Octane crashes when I try to edit the camera settings (and DAZ is crashing in that case also)

4: Very often I can't change the size of the viewport or the dimensions of the render: I'm testing in 800 x 600 and when I try to change to a higher resolution (e.g. 2.400 x 1.800) I can't edit those settings; After a whil I get a message like "...octane configuration is invalid"


MyRho

[cyprine]

1: DOF doesn't work at all (path tracing, HDRI) - I can change the settings in DAZ but nevertheless there's no effect in Octane even after re-loading the scene.

are you using a camera or simply trying to render from perspective viewport ? selecting a camera view should fix your problem.

2: Octane very often (almoset EVERY) time doesn't save the applied materials so I have to load and apply them every time I open the 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.

dunno about the 2 last points

[abayliss]

I'm experiencing an issue where any movement of an object or figure in Daz causes Daz to freeze for a few seconds before updating the figure position. This can make figure posing adjustments painfully slow.

I originally thought the issue happened with any figure posing adjustments as well as object movement, but this was only because the figures had objects parented to their hands. So when I adjusted the pose of the figure, it would then move the object, causing the freeze. If a limb does not have a parented object, then it can be bent and twisted without any problems.

The length of the freeze depends on the complexity of the scene, with a single figure scene, the freeze is barley noticeable. Which a complex scene, such as one with six clothed figures the freeze is a couple of seconds.

This does not start happening until I open the OctaneRender Viewport.

Pausing the render does not fix the issue.

Disabling Live Geometry Updates does not fix the issue.

Closing the OctaneRender Viewport does not fix the issue.

Clearing and re-opening the scene does fix the issue until I open the OctaneRender Viewport., at which point it happens again.

Hiding multiple figures in the scene can reduce the length of the freeze.

*** I've edited my post with corrections after extensive testing ***

[MyRho]

1: DOF doesn't work at all (path tracing, HDRI) - I can change the settings in DAZ but nevertheless there's no effect in Octane even after re-loading the scene.

are you using a camera or simply trying to render from perspective viewport ? selecting a camera view should fix your problem.

2: Octane very often (almoset EVERY) time doesn't save the applied materials so I have to load and apply them every time I open the 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.

dunno about the 2 last points

Thank you...
But I'm not using the perspective camera; When I start a new scene I always create a new one and call it "octane" camera (or camera 1) - but that doesn't help...
And the material presets won't work for me in most cases. Ween I try to apply a material loaded from the presets list octane doesn't use it and the material won't change. Tried to unlink it from the octane material, let it generate a new marerial (auto and blank) and then re-apply it from the presets list (or form the local db) but then it's all white.
But I can apply the materials to other props in the scene so the materials are ok - they are working fine.

[Squirtle]

Tue Jun 09, 2015 6:53pm
PS: i'm going to be present in the forum during the next two weeks (means after i had added some details about this release),
so whatever you have to say or ask - this will be the time.

Sat Jun 06, 2015 12:13am
We will make sure communication regarding the road map is more frequent and consistent - at least every few weeks, if not more often, until it is out of beta.

So it's been about 7 weeks. When do the "details" get added and when does t3's two week presence begin? And by my calculations we're due two or three "road map" communications.

I've mentioned this some weeks ago as my own passive aggressive way of trying to call attention to the fact that nobody responsible for this plugin seems terribly interested in it anymore, or following through on their promises. It's the elephant in the room here, isn't it?

Octane standalone is good software, but the company completely flaked out on supporting this plugin. It still baffles me how poorly they've dealt with t_3's broken promises and sheer lack of respect for us, and how Otoy doesn't even pretend to care. I get that Otoy has their sights set on other more lucrative projects, but I'd think that leaving paying customers out in the cold with never-finished software and no communication puts their company in a very bad light. Is anyone actually surprised that we haven't seen even a hint of the "road map" yet?

There are only so many possible reasons why they haven't followed through on this promise of a road map. One or more of these:

• 1 - It doesn't exist
  2 - It's something the customers wouldn't accept
  3 - Gross incompetence and indifference

What a total embarrassment.

If t_3 ever does make a release taking OcDS out of beta, it will be completely irrelevant, broken, and redundant when DAZ releases DS 5.0. (assuming OcDS is out of beta before that happens) And it's perfectly clear there will never be another OcDS update after 2.x is "finished". Everyone in this forum has given Otoy more than a fair chance to right wrongs, while Otoy decided that it isn't worth their time to even communicate some BS road map every few weeks as promised. This project is obviously abandoned.

[bepeg4d]

hi,
please, don't be so negative, a constructive criticism is always the best approach, in my opinion.
Otoy is hearing and my presence here in the DAZ section it's an example, but Otoy is also super busy for creating new features that will be useful for DAZ users as well in a near future
Stay tuned,
ciao beppe