why don't uberenvironment and pwsurface play well together?
evilded777
Posts: 2,440
I've been wondering for the longest time why uberenvironment was soo slow. I'm talking tortureously, canceling the render even on lowest possible quality settings slow.
I've been dying to get my ahEnvironment light back in Studio 4.
But then I tried something, just for the hell of it: replaced my pwSurface with Human Surface.
Problem solved.
Not nice.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
UberSurface also works fine with it. I use that instead of pwsurface2 now.
If you are going to use UE with pwS2, it is HIGHLY recommended that you disable the Ambient Occlusion, AO for short, in one or the other. Do not have it active for both and here is why.
Uberenvironment is a type of lighting for DS. pwSurface2 is a surface shader. Both pwSurface and Uberenvironment use AO but they both do it differently. And its the AO that is clashing. UE has a single control for AO, which some people prefer, that affects the entire scene all at once. pwS2 being a surface shader applies AO only to the surface of which pwS2 is applied to. Please note, in DS3 & 4 you can use the surface selection tool to right click any surface and tell it to mass select all surfaces using pwS2 or whatever surface shader you are using. Though there is no global control for AO with pwS2, you can have far greater control over how it is applied. Two examples would be colour and just how much AO is used. pwS2 allows you to define the colour of your AO so if can better reflect the surface its being used on without affecting the strength of which it is applied. You can also determine the amount of AO used in different parts of your scene. If you render a lot of scenes with hair and raytraced shadows, you can leave the amount of AO in the hair to be lowe then in other parts of the scene. I tend to do that mainly via the quality level controls that come with pwS2 though the overall strength of AO can be used to affect that as well.
I personally do not use UE at all. As an avid pwS2 user I prefer the standard DS lights combined with pwS2 on all my surfaces. It is a lot harder to fake Global Illumination that way I will admit and though I have in not perfected it, I know it can still be done reletively well. From my own personal tests, I find pwS2 used with standard DS lighting renders a lot faster than UE and with equal quality.
Please feel free to check out my gallery here to see examples of pwS2 in use - http://mattymanx.deviantart.com/gallery/
That's an interesting conclusion, Matty.
It had not occurred to me that the AO might be in conflict. I will have to investigate. I wouldn't think surface AO and light/scene based AO would be a problem like this. Its not with that other software.... :)
It's only a problem because of the differing types of math involved. If you use Shader Mixer AO, you can double up on AO (by using UE2) without the tremendous render hit that you get when you use pwS2 AO and UE2. There is still some penalty, but it's not nearly as severe.
In my testing so far, this seems to be a DS 4 problem... DS3 didn't bat an eye at the two of them together (UE2 for DS3, pwS2 for DS3 with AO on).
I need to test with DS 4 and AO off still.
I will admit I would have never tried them together. Never would have guessed that they get along in DS3
It would appear that Mattmanx's initial suggestion that the two AO's were conflicting is correct.
More testing might be in order, but I am pretty convinced that's it. Turn off the pwsurface AO (or at least, don't turn it on) and I'm zipping along the way I expect to be.
Thanks Matty.