jennblake opened this issue on Jun 20, 2019 ยท 654 posts
ironsoul posted Fri, 28 June 2019 at 12:34 AM
wolf359 posted at 6:02AM Fri, 28 June 2019 - #4355004
If the DS conversion was from Delight to Cycles it be interesting to know how
reliable the results were.
@ironsoul I am not sure what you mean by"from Delight to cycles".
I dont Use IRay or 3Delight -technically because I never render from Daz studio however any image based materials are converted to cycles nodes referencing the
texture maps used in the DS Scene. Most Iray procedural shaders do not convert to cycles nodes properly (no surprise there)
Of course you can replace any Daz converted node with a principled shader as I
have done for the Clothing in the image I posted the Characters skin is an Old Mike 4 "Sole elite" set being used on the G2 Male.
Of course nodes will need adjusting in blender particularly the gloss nodes which are always much too shiny by default.
Thanks Wolf, I was interested to understand if we had the same idea of how a conversion process works, we use a script or program to create the basics and then tweak to fix any issues. My concern about FF compatibility is that there are many users who have no interest in tweaking mats and whose criteria for a successful conversion is to load FF model in to SF press the render button and the result meets their expectation. I'm the same with cars, don't care how an engine works just want it to start and get me to and from work. SM did a great job with compatibility that almost but not quite worked, unfortunately the failure was with the eyes not being rendered correctly which is the first place people look so p11 SF got a bad rep for not working correctly IMO. To move forward I think we need an upgrade path that allows old FF content to still be used in poser reliably.