jwiest opened this issue on Mar 19, 2018 ยท 11 posts
jwiest posted Mon, 19 March 2018 at 12:32 PM
So I've recently started getting back into using Poser after being away from it for a few years, picked up P11 on sale last year (know DAZ is free, but I still remember how to use Poser better...)
Anywho...I'm having issues with eyes being much more sensitive to light/reflections/settings/whatever. The below image has the left eye rendered in Superfly (default settings) and the right in Firefly (again default)...area renders for each and then screen captured for this post.
What on earth do I have to do to get the Superfly version to come out looking more like the Firefly. It almost always comes out looking so washed out/glare filled/whatever and is driving me nuts.
I've seen other threads suggest it was the intensity of the lighting, but I've tried dialing that back pretty drastically (from 1 to .25 or .8 to .2) and it still does it. Any suggestions would be awesome. Tried poking around in the Materials room (which was something I wasn't terribly good with back when I was rendering more) to no avial.
Any and all suggestions greatly appreciated.
Thanks John
John
bagginsbill posted Mon, 19 March 2018 at 2:40 PM
FireFly uses pre-ray-tracing techniques for reflecting light sources, and so it is common to add two nodes for reflections - one for light sources (from the "Specular" family of nodes) and one for actual raytraced reflections (i.e. the Reflect node). These two nodes do separate and essentially unrelated things, and they get added together. Some older eye shaders don't even bother with the Reflect node and just use one of the specular family of nodes, such as Blinn, Glossy, Specular, etc. As well, people making shaders here often told the specular node to use ridiculous settings, mostly to achieve some exaggerated highlight effect but often because they had no clue what they were doing.
Conversely, SuperFly uses nothing BUT ray tracing, and your specular node (if you have it) is basically a reflect node. So you either have a massively overpowered specular-family node, or a specular + reflect doubling up, or both.
The solution is to assemble a proper eye shader. Guessing from your question you don't know how.
Therefore I'd suggest you get and use EZSkin 2 which will do all the work for you.
Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)
jwiest posted Fri, 23 March 2018 at 10:20 PM
I've downloaded that and will give it a shot.
Had been thinking/hoping that just turning a few settings up/down in the Material room would be the solution (or at least A solution), but oh well.
Thanks :)
John
hborre posted Sat, 24 March 2018 at 2:20 PM Online Now!
Actually, it's EZSkin 3 that has both settings for Firefly and Superfly.
Azpir8king posted Tue, 05 June 2018 at 4:25 PM
is there an ezskin3 tutorial? Something that helps me understand WHY specific nodes (and node orders) drive Superfly nuts (Semi-novice level)
Tom Tinney,
Writer, Rider, BIKER-NERD!!
Mewe Group:Biker Nerd Clubhouse
ironsoul posted Wed, 06 June 2018 at 5:41 PM
Not sure if Ezskin would explain why, it replaces the shader tree to avoid the problem nodes. I would point to BBs response above, specular causes problems not just between FF and SF but also other apps (eg Poser to Vue).
Below is an illustration of the problem and not intended to be taken as a correct solution (I don't have BBs indepth understanding of the math).
I replaced the Anisotropic node (more commonly used for hair highlights) with the ks_microfacet node and reduced the about of spec returned. The eyesurface would also need to have this change for the full effect.
Azpir8king posted Thu, 07 June 2018 at 9:53 AM
Thank you. That helps me understand a little more.
Tom Tinney,
Writer, Rider, BIKER-NERD!!
Mewe Group:Biker Nerd Clubhouse
sandwood12 posted Thu, 21 June 2018 at 5:01 AM
I have same problem I just stay the old firefly until some an correctly fix this problem or a clearer way fixing it. New firefly is not much difference over the one.
Azpir8king posted Thu, 21 June 2018 at 10:14 AM
sandwood12 posted at 10:13AM Thu, 21 June 2018 - #4332157
I have same problem I just stay the old firefly until some an correctly fix this problem or a clearer way fixing it. New firefly is not much difference over the one.
Download and install the EzSkin3 tool (Plugin). It does work and relatively easily. Superfly renders so much faster and better than Firefly. It's worth it.
Tom Tinney,
Writer, Rider, BIKER-NERD!!
Mewe Group:Biker Nerd Clubhouse
Eric Walters posted Mon, 26 November 2018 at 10:34 PM
Thanks BagginsBill for Cycles for Poser11! OSX Sierra, Poser Pro11 current version updated a few days ago, Cycles is not showing in the menu.
I just came back from a Long 3D absence. I got EzSkin3 from Snarly- and it works in Poser11 Pro. I've installed your cycles pyc as you recommend-but Poser Mac is not seeing it for some reason. It is in Custom Shaders- but does not show up in the EZ menu-just Firefly and Superfly. I CAN see cycles in the Poser Scripts menu-not in EZskin3 THANKS!
RAGraphicDesign posted Thu, 31 January 2019 at 1:29 PM
Hi everyone. Using both Poser 9 and Poser 11 I downloaded both EZSKIN 2 and EZSKIN 3. As for EZSKIN 3, which I installed for Poser 11, I found the various instructions regarding where to fix the various elements contained in the zipped folder. For EZSKIN 2 I have placed everything except the folder called "EZEffects". I do not know where to put it ..... Thankyou:)