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) 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.)
Ciao Notiusweb
(Am I doing that right?
)
Looks good. Numbers 2 and 4 are likely related, and probably have to do with the way the interface fails to grab or keep focus. If the cursor does not remain precisely over the field one desires to enter, focus may or may not switch to wherever the cursor is at that moment, which could lead to the Daz Studio interaction and/or failure to register keys pressed in fields, even though the cursor may still be flashing in said field and field may still be highlighted. I think this was addressed by t_3 at one point (the last post of the second page in this thread), though I don't know if anything conclusive was stated regarding it. If I had to summarize it, it would likely be something along the lines of the 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).
Secondary assist for anyone not using the keys to navigate in Daz Studio is to turn off keyboard navigation within Daz Studio itself (Shift-K for the hotkey, I believe). Does make it harder to notice if text is failing to register in some cases, but eliminates unwanted camera movement for me, at least.
