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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment