It's pretty much at the top of the list of things to doOh, and a scalable Setup window REALLY would come in handy

Moderator: face_off
It's pretty much at the top of the list of things to doOh, and a scalable Setup window REALLY would come in handy
Yes, it's a pretty similar approach as I usually use in the stand-alone version (from which I derived my Poser-plugin settings).face_off wrote:Interesting Uwe. And yes, a very good start. I assume you've seen http://poserphysics.blogspot.com/2012/1 ... hader.html?
Well, I politely have to disagree.face_off wrote:I only did studies with frontal and side lights - not back lights. In those cases, I didn't find any difference between -1, 0 and 1 for direction. However the reflected light should be as important as the back light - so I thought 0 would be the best for the direction.Direction goes more to +1 because we want the light to travel through and not reflected.
That's exactly the function of the SSS-map. Being a floatimage, the brighter areas allowing more and the darker area allowing less or no scattering.face_off wrote:I found with absorption at 0, there can be a buildup of light inside the mesh - which is what is happening in her nose. Again, I'm not expert, but I found you need the absorption near the scatter value so that the light doesn't scatter forever.absorption:0, scattering:0.09
Ah, so would like the Poser prop/Figure selected AND expanded (so you see all the prop/figure materials)? Keep in mind also that as you click more Poser props/figures, it will expand more of the tree making it look a little "messy".i just meant that when you select an object, actually, it selects automatically the material concerned ( which is great ! ) but just the level 0 ( see pict. attached), i propose you the same process but develop the 1st level of the material instead of keeping it 'closed': it just avoids to open it ( gain of 1 click ) -> hope you understand, here is a screen capture to illlustrate
Thanks Vincent - I can certainly add that feature. Collapsing the previously selected tree may be an inconvenience for some users - however I'll see how it goes.For consecutive selecting, it closes the previous one to expand the last selected... of course, it is (again) just a suggestion...
Tweaking workflow can be a sensitive area - what works for one user might not for others. So unfortunately I need to take a cautious approach to changes like thisyes probably and in some case for me too...
thanks