Post by TRRazor » Sun Nov 15, 2015 10:42 am
like create a bypass of the need to reduce the Normals power from 2 to 0 in certain cases, like the 3Delight mats on G3F
We've actually never supported the DAZ3D figure normal maps (although it would be fairly easy, to accommodate for them in the shader layout).
We've mostly tweaked them in order to be used with a subD of 3, instead of the standard "0" value + normal maps, as this gets you the same geometry detail, without having to worry about the issue.
It's a mere drag and drop and your figure is ready to be rendered within seconds.
Goldorak, I do not believe TRRazor would ever dismiss his user audience like we have seen in our experience. In fact, TRRazor went out of the way to add perspective on an issue not under his control, expressing his viewpoint. So a 3rd party developer's involvement should not inherently be something which slows a process down, or makes it more ambiguous. The users here are victim to a uniquely frustrating dynamic (...and deserve a 1/2 off another plugin

).
Not just that, but TRRazor has identified mechanics of a process, at minimum, which bypasses a conversion issue of OcDS. If somethings along these lines could be automated into the plugin, a major conversion issue could be resolved (Normals map issue...).
(TRRazor, I am checking out the Redspec products as we speak, not because they bypass an issue, but because the results do look great

)
Post by Spectralis » Mon Nov 16, 2015 1:48 am
This is exactly the kind of information I would like to see regarding planned updates in the future.
Spectralis, I appreciate the concurrence. I consistently concur with your sentiments as well.
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise