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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment