OcDS Setup v2.2 (last Beta)

[Hydra]

Also... did you try smoothing? I do that sometimes with accordioned hip or arm bends.

With this 'issue' increasing the subd level as linvanchene suggested is legit method. A bit 'brute force' thou Smoothing cannot help here as bad things happen after all modifiers got applied - when triangulation is performed. Studio uses naive method of triangulation, it just split quad in two triangles and no care is taken about mesh curvature at this point so with low-poly meshes such issues are inevitable.

Well, I have found smoothing hit or miss, but again with all things rendering, you can use what ever method suits your render. I have noticed that smoothing has improved from way back, namely it doesn't turn your character into a marsh-mellow anymore. I often use it with sub-D.

For instance, in the provided example we are looking at a close up of a nude arm pit while the arm is straight out. Most arms aren't naturally in that position for a close up. Most arms are down in some way, and often clothing is worn.

I'm not trying to rain on anyone's parade here, I'm just saying use whatever you can get away with for the render.

[asennov]

For instance, in the provided example we are looking at a close up of a nude arm pit while the arm is straight out. Most arms aren't naturally in that position for a close up. Most arms are down in some way, and often clothing is worn.

I've just used the same mesh and close enough lighting and pose to show that effect is not Octane-specific and it's not a bug. It actually can be seen on almost any low-poly mesh, even sphere:

I'm not trying to rain on anyone's parade here, I'm just saying use whatever you can get away with for the render.

True.

[Notiusweb]

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) Key Entry - while using in OcDS, typed keyboard characters interact with DS UI, which is unwanted
(3) 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
(4) Non-responsive node to keyboard - sometimes you can't type a numeric figure for a node parameter, you have to use a mouse on the parameter slider
(5) 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....)
(6) Camera Motion Blur
(7) Object Motion Blur

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

Just adding ideas brought by you guys, 'Workarounds' and 'Feature Requests' would probably work well in list form too.
It will allow anyone in the forum to look at the latest list and query status of things, or get a resolution which has been discovered without having to search for it. A user can always read up on earlier in this forum or another for further info, but here just get a status instantaneously. I made it blue just so it can be seen easier.

[sikotik13]

I am open to the possibility I'm just doing something horribly, stupidly wrong, and welcome any constructive illustration of such. Random image because it made me think of summer:

If your scene and animation work in Studio viewport there is nothing wrong with them. Are you animating on Studio timeline directly or using animate2 ?

I built the animation (for the character) in animate 2 and baked to studio keyframes, then manually verified them before rendering. I can render each frame just fine by sliding the timeline slider to each, but that's a bit ridiculous for 266 frames. I suppose there is (probably) an issue with keyframes baked by animate2? Seems silly, since once baked, they are indistinguishable from native keyframes, but I'll give that a shot, thanks.

Anyone else having the random liveDb issue, or is that just a me thing?

[bmosalt]

Anyone else having the random liveDb issue, or is that just a me thing?

Yes, I've been having random issues with the LiveDB sometimes not loading properly. For example, in the below images the LiveDB has loaded some ungrouped material files (first pic) but if you click on a group (second pic is Wood group) then it doesn't have any materials loaded.

first pic

second pic

If I close DAZ and restart it sometimes the LiveDB will work again.

[linvanchene]

Anyone else having the random liveDb issue, or is that just a me thing?

Yes, I've been having random issues with the LiveDB sometimes not loading properly. For example, in the below images the LiveDB has loaded some ungrouped material files (first pic) but if you click on a group (second pic is Wood group) then it doesn't have any materials loaded.


If I close DAZ and restart it sometimes the LiveDB will work again.

Did you allready try to clear the live db cache?

compare:

RECOMMENDATIONS:

+ you should clear the live db cache (in the preferences tab) after installing this version

[bmosalt]

Did you allready try to clear the live db cache?

Yes I did that when I first installed v2.2. I've also done it a couple of times since to see if it would fix the error. Using the clear cache button under preferences.

[sikotik13]

Did you allready try to clear the live db cache?

compare:

RECOMMENDATIONS:

+ you should clear the live db cache (in the preferences tab) after installing this version

For what it's worth, I cleared it using the preferences panel, and by deleting the files manually (as steps 1 and 2, respectively, step 2 done repeatedly since).

*Decided since this seems to be a solo issue, I'll try a new thread to bounce around ideas for what I may have screwed up somewhere, instead of filling this thread with it. IF it get's figured out to be an actual OcDS issue, I'll come back here to add it to the list.*

[Spectralis]

I think I might have encountered an animation bug. The scene has an HDRI for background lighting and I set up a plane and applied an emissive material set to blackbody, added an IES spot file and then turned down the opacity of the plane. In the viewport the spot appears as it should do so I adjusted it to what I needed. The scene looked fine in the viewport so I rendered a still which came out fine. Unfortunately when I tried to render animation the spotlight does not appear in any of the frames. I'm sure I've set up animation correctly, including the correct camera and lighting setting in the animation pane - not much has changed since 1.2. Anyone else experiencing this or know where I'm going wrong?

UPDATE: I've worked out what the problem was: "Surface Brightness" was set to ON. When I switched it off the spotlight appeared in the animation renders.

I discovered that there is a discrepancy between the HDRI power setting in the Viewport and the final render. The final render is about 0.5 lighter than the image in the viewport. Maybe I'm not setting up the HDRI correctly but the viewport seems to always be darker than the final render for some reason.

OcDS is so frustrating! I've spent over a day trying to set up the lighting for this scene in Octane that took about an hour to do in iRAY and produced better results. Even the animation render times appear to be pretty close. I'm not buying this tweakers paradise line about OcDS when iRAY can produce better results with only a few tweaks in a fraction of the time. If it takes five hours to master iRAY and five years to master OcDS then I don't think I've got the patience. Productivity wise it's not viable for me either - I'd rather not spend more time troubleshooting than rendering a scene.

[DrHemulen]

Daz3d seemed to have optimized G3F for Iray which applies some subdivision by default when rendering.

G3F has by default LESS points, vertices, polygons than G2F.

Also note that some G3F V7 morphs are HD.


Basic recommendation:

Raise subdivision level to 3 so you are working with 1'000'000 points and not less than 100'000.

Yup, that was it, thanks. Looking at the base mesh with no subdivs, it's a LOT rougher than gen1 og gen2. This really is a bit of a different paradigm.