OcDS Setup v2.2 (last Beta)

[larsmidnatt]

yeah I tried the OBJ method with LAMH and GH a few years ago, too painful for most projects.

[itou31]

Hi t_3,

Feature request or bug fix : save texture size settings (ie 1/2,1/4 ...) with the file. OOC feature is great but doesn't work very well with PCIe riser (1X). So need to resize many textures each time. Thanks.

[Notiusweb]

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.

[DrHemulen]

Feature request: Use the "Render SubD level" setting in Paramers/Mesh Resolution.

You can also maybe change my autoconversion suggestion, as a converted material isn't nessecary when using templated materials. A bunch of basic templates would be nice though

[linvanchene]

@ autoconversion workaround

Thank you for sharing. Especially the "rename from linked surface" may be an option many have overlooked.

But to make it very clear: A workaround is not a solution. Auto conversion had been working flawlessly with a simple system in the past.

At least basic detection of diffuse and glossy materials was working.

A hotfix should have been released that reintroduced the simple version we had. THEN AFTER THAT HOTFIX t_3 could have taken all the time he wanted to search for more advanced solutions to implement more options to control how auto conversion works.. (IF that is what he is doing right now.)

And that is what makes me really angry. Instead of quickly providing

HOTFIXES

nothing happens for months.

This was the same with that mouse wheel scroll instead of zoom bug in the NGE and the OcDS viewport.

An annoying issue that should have been fixed a week after prerelease 5th was introduced.

Why is it not possible for those in charge at Otoy to teach their plugin developers some basic PRIORITIES?

FIRST provide a SIMPLE working solution.
THEN try to implement advanced features that may or may not work.

- - -

In that spirit a most basic feature not many seem to be talking about is not even on the list:

Save OctaneRender materials for individual surfaces as .duf presets.

Both the 3Delight and Iray nodes are directly integrated into the DAZ Studio surface tab.
Because of that it is possible to actually save those materials as .duf presets for the surfaces selected in the surface tab of DS.

IF anyone actually wants to see products with OctaneRender material options created this needs to be implemented one way or the other. That probably should have been one of the first features to be implemented so people finally can start creating licensed 3D content with material options for OctaneRender and distribute them through the DAZ 3D store.

- - -

[DrHemulen]

IF anyone actually wants to see products with OctaneRender material options created this needs to be implemented one way or the other.

- - -

But isn't this already in?`
I want to to try to hack a solution, so as a test I saved a material in the normal DAZ file dialog. Much to my surprise, I was able to rebuild the octane materials "from embedded data" after applying it to fresh model. Looking at the .duf material file in a text editor, the crazy OCDs material strings are in there. So it should work? Maybe it's just not transferable from one PC to another?

[sikotik13]

Yes, it is technically there. The issue would be for anything that requires a particular mat file, and possibly for that mat file to be in a particular location. Probably why the RedSpec shaders are set up such as they are. I would presume that OcDS does not read relative strings, or at least not the same way that Daz Studio does, since I gathered those particular mat files get installed in a particular location outside of the Daz Studio library. Similarly, I would guess that the issue linvanchene is presenting is a problem of path-reading, forcing the mentioned forced install location outside of the usual library, not the saving of materials as .duf presets in general, as that is, indeed, currently present, and has been for quite some time. Since 1.2, at least, if I'm not mistaken.

[DrHemulen]

Maybe the trick is to make a normal DAZ material first, as that can be save and distributed? You can get DAZ materials at renderocity, and there you just copy the dufs and maps into the relevant folders in the runtime. I think it may work, it's just very badly documented, which is another issue.

It's certainly worth trying out?

[swipswap]

Feature request: Use the "Render SubD level" setting in Paramers/Mesh Resolution.

This would be a killer feature. Maybe it could make use of Octane's subdivision.

[Neuroheaven99]

Anyone else having trouble typing exact values into the NGE? Or the LDB when searching for a material? More often than not I am unable to type exact values; only the sliders work.

It happened to me some times too.
I also had : I am in a field select value (overselected in yellow) start taping a new value and it do nothing or even sometimes input the value in another field oo !