Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
903775
Regression
No
[PLM] Overall intensity mismatch with Enlighten
On advisory boards and forums, some users complained about the overall intensity mismatch across Enlighten and Unity. This bug report aims to isolate the issue.
Default intensity and falloff of baked point lights and spotlights of Progressive Lightmapper don't match with Enlighten. A small repro scene is shared in the project.
Reproduction steps for brightness difference across Enlighten and Progressive Lightmapper:
1) Download the project and open the scene "TestIntensity"
2) Bake the scene with Enlighten
3) Bake the scene with Progressive Lightmapper
4) Observe the intensity difference between different backends
Notes:
One more scene is shared in this project to observe the difference betweeen Enlighten and Progressive Lightmapper. If you open `TestShadows` scene, you can click on `LightMode` asset in the project and toggle between Baked and Realtime lights. Then, you can switch between Enlighten and Progressive Lightmapper. This scene should ideally be used to determine the brightness difference when light modes feature is implemented.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment