The SkyLight darkens anything that uses “2 Sided” and “SubSurface” shading models. And it darkens them too much.
Everything works fine as long as the SkyLight is set to Stationary. But this happens as soon as you put skylight on Movable. (Happens without having generate mesh distance fields and DFAO activated so it’s just something wrong with the SkyLight itself or the shaders).
After using 4.10 for a while then I downloaded 4.11.2 and faced the problem for the first time. And it is still there in 4.12 Preview 2 as well. (Both downloaded through launcher).
Repro steps:
Create a new level
Check Force no precomputed lighting option in the world settings and click on build lighting once to get rid of the pre-baked lighting that’s on the newly created level.
Put a piece of foliage/vegetation in the scene. (Something that has leaves and uses the “2 Sided” shading model.
Remove directional light. (Do this so you will see the problem a lot easier).
Add Skylight.
Switch back and fourth between Stationary and Movable to see the darkening problem.
The problem happens 100% of the time when I do this in 4.11.2 and 4.12 preview 2.
System specs:
Windows 7 x64
GTX 970
Core i7 4790K
16GB RAM
Example setups:
Skylight set to Stationary - No DFAO
Skylight set to Movable - No DFAO
Another test
Another test in different project
It is very critical for us to have skylight working properly on movable. So we can then use DFAO. But currently it darkens the assets so much without DFAO that if we enable DFAO too then it’s just total darkness on these assets.
Looking forward to get a reply on this!
Yes. It happens when directional light is affecting the world as well. But because the directional light is lightening up the assets, it undo the skylight problem to some degree. But the problem is still there with/without directional light.
So what if we don’t get any answers on answer hub too? do I have to bump there as well?
Just want to know if it’s going to get fixed asap or not. It’s a big red flag if we can’t have DFAO in projects because of skylight not working on movable.
Shivers down my spine and this strange feeling that comes with cold and sweaty hands when thinking about doing a game that takes 1-2 years to complete in UE4.
Can you let the decision making board know that feature hunting in every version, trading of stability, is not going to convince developers to use the engine?
Just showed the ‘Two sided foliage in 4.11’ line to my buddy.
Reaction was something close to this:
Have mercy with us, guys! Do not become the next Cry-Engine, with users just waiving at UE4 after too much mess produced by feature mongering. That already got Cry-Tek into trouble. For every serious project, stability and reliability is number one.
I just downloaded 4.12 Preview 4 and there are still problems with 2 sided and subsurface shading models there.
Things don’t get as dark as OP but they still do. And the following screens are without having DFAO and SSAO. It’s just a skylight switching from stationary to movable.
Now if we were to use DFAO and/or SSAO, things get much darker as well.
Repro steps are the same but I will just write again.
**
Repro steps:**
Create a new level
Check Force no precomputed lighting option in the world settings and click on build lighting once to get rid of the pre-baked lighting that’s on the newly created level.
Put a piece of foliage/vegetation in the scene. (Something that has leaves and uses the “2 Sided” shading model.
Remove directional light. (Do this so you will see the problem a lot easier).
Add Skylight.
Switch back and fourth between Stationary and Movable to see the darkening problem.
The problem happens 100% of the time when I do this in 4.12 preview 4.
This is a solid dead end for foliage/vegetation and outdoor scenes. Please look into it. We’re stuck at this since 4.11.
Thanks.
Edit: @DanielW, I just noticed “Lower Hemisphere is black” was unchecked on the skylight. When I check it I get witness the problem at its 100% strength like in the OP so this isn’t fixed at all. Did you mean preview 5 when you mentioned it’s fixed in the next preview?