Admittedly I am not using the pose camera but that can't be it, can it?

I have PP2012 on Win7, set my unit to inches and feet, to try it and used EZskin to see if it helps. What did I miss?

And yes I have updated to poser's Sr2.1. But it was like this before and I have opened my saved file, so it is also not the render settings.

Gamma Correction.  Turn it down to 1 or turn it off.

Did you remember to change the gamma to 1 on the transparency & bump maps?

Quote - Gamma Correction.  Turn it down to 1 or turn it off.

Somebody is trying EZSkin and using Poser Pro 2012, and then you tell them to turn off gamma correction?

That's like somebody with a question about their new Ferrari, and you say "Don't go above 30 MPH".

Note that by default EZSkin sets the correct gamma settings for you in the Texture Manager unless:

You turn off the feature in EZSkin

or

The Transparency / Bump / Displacement map is the same map as the Diffuse map, in which case it favours the Diffuse Map and sets the gamma to 'Render settings'

Quote - > Quote - Gamma Correction.  Turn it down to 1 or turn it off.

Somebody is trying EZSkin and using Poser Pro 2012, and then you tell them to turn off gamma correction?

That's like somebody with a question about their new Ferrari, and you say "Don't go above 30 MPH".

I am.  See Snarly's post above.

I hate to see someone waste gamma correction like that.  IF the situation snarly points out is occuring it would be better to duplicate the diffuse node and connect any transparency, bump, or displacement to that node.  Then you could set that gamma to 1 and leave the diffuse node as render settings.   I cant honestly see having the transparency hooked up to the diffusemap though.

If the shader is wired poorly, then let's examine the shader. If that's the problem, the correct advice is to fix that, not throw GC out the window.

But - you're all guessing WITHOUT EVEN A RENDER.

How do you know it's not just a problem with min shading rate? Maybe the render is being done from a distance where it's not going to look right even at .63.

If it were the min shading rate wouldn't lashes be effected also?

I added a render of the eyebrow problem: on the left it's rendered (area render) the rest is unrendered preview.

Tried with a lowered min shading rate, now it's fine - thanks for refreshing my old person's memory. :)

Hah. Awesome.

I don't know why people argue with me.

Quote - I hate to see someone waste gamma correction like that.  IF the situation snarly points out is occuring it would be better to duplicate the diffuse node and connect any transparency, bump, or displacement to that node.  Then you could set that gamma to 1 and leave the diffuse node as render settings.   I cant honestly see having the transparency hooked up to the diffusemap though.

It doesn't work like that.

If you duplicate a node the resultant two nodes are still referencing the same texture, and Texture Manager will only allow one setting per texture (not per node).

In other words, you change one, you change them both.

It's not just the extra node you need to create, so much as an extra texture map, which EZSkin isn't set up to do (but is an interesting possibility now we're thinking about it).

Although it has no bearing on the OP's issue (neatly sorted out by BB), this is worth bearing in mind anyway.

Thanks, I didn't know that.

So the same image file will have the same gamma even if I use it in different nodes?

I don't normally do that anyway but I have occasionally used a math node to greyscale out the diffuse texture for bump while testing or working on the texture and haven't got around to doing a proper bump map yet

Quote - > Quote - I hate to see someone waste gamma correction like that.  IF the situation snarly points out is occuring it would be better to duplicate the diffuse node and connect any transparency, bump, or displacement to that node.  Then you could set that gamma to 1 and leave the diffuse node as render settings.   I cant honestly see having the transparency hooked up to the diffusemap though.

It doesn't work like that.

If you duplicate a node the resultant two nodes are still referencing the same texture, and Texture Manager will only allow one setting per texture (not per node).

In other words, you change one, you change them both.

It's not just the extra node you need to create, so much as an extra texture map, which EZSkin isn't set up to do (but is an interesting possibility now we're thinking about it).

Although it has no bearing on the OP's issue (neatly sorted out by BB), this is worth bearing in mind anyway.

A math node is not necessary to convert to gray scale. Plug a color data stream into any number, including the bump channel, and it becomes a number, I.e. gray.

And this texture (which I think relies on snarlygribbly's shader) also suffers from very slow rendering. Can somebody else or am I again doing something wrong?

tried with the above render settings and these new old ones I'll add here (they came with that old saved pz3).

15 pixel sampling will slow renders down considerably along with SSS which is included in Snarly's EZSkin.  You really don't need that value so high.  Irradiance caching could be lowered also. 

Also, why is your gamma correction = 1?

IC = 100 is very slow, no matter what you're rendering

Quote - And this texture (which I think relies on snarlygribbly's shader) also suffers from very slow rendering.

As much as I'd like to, I can't take any credit for the shader :-)

It is (very) heavily based on Bagginsbill's ideas published at RDNA.

EZSkin just makes it easier to apply, that's all.

Simple question, why using ppro2012 without IDL but with SSS ?

Quote - IC = 100 is very slow, no matter what you're rendering

Quote - 15 pixel sampling will slow renders down considerably along with SSS which is included in Snarly's EZSkin.  You really don't need that value so high.  Irradiance caching could be lowered also. 

Also, why is your gamma correction = 1?

The setting is just one of many combinations I tried.

I opened an old file to see how long that would take, and it used those numbers. (And took about 2 minutes to render the first time I tried) The gamma is from that pz3 also - if I set GC to 2,2 there V4 and her hair and texture get superdark and grey. I don't know why.

This working file has also ten lights and is still faster than the newer one with only 1 infinite light source...

Quote - Simple question, why using ppro2012 without IDL but with SSS ?

Do I need to? I never have and always had renders I was totally okay with. And I was happy with render times...

Quote - As much as I'd like to, I can't take any credit for the shader :-) It is (very) heavily based on Bagginsbill's ideas published at RDNA.

EZSkin just makes it easier to apply, that's all.

Aaah, now I feel bad - I don't mean to accuse, I was asking because I was wondering if the script could be at fault. I tried with a V4 and just EZSkin and it took 27 minutes to render - with PP2012 standard firefly settings plus raytracing, smooth polygons and remove backfacing polys...

But I think it is something else to do with the update. Should have waited to use it. :(

Okay, I can't edit... so I reset the preffered scene to factory default, and imported my bad file... now Poser plays nice with me again. I don't know hat I changed that was wrong, but I'll try to avoid it in future.

As always, the problem sat in front of the computer.