Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2020.3
2020.3.20f1
2021.3
2022.1
2022.2
Issue ID
1418034
Regression
No
Lighting is corrupted in build when the built scene is not opened in the Editor
How to reproduce:
1. Open the attached project "LightGeneration"
2. Open the SampleScene
3. Build And Run the BuildScene
Expected result: Lighting is built correctly and looks the same as in Editor
Actual result: Lighting is not rendered correctly, the scene is dark, but shadows still exist
Reproducible with: 2019.4.38f1, 2020.3.35f1, 2021.3.4f1, 2022.1.6f1, 2022.2.0a17
Reproducible on: Windows 11 Pro
Note: Not reproducible if the built scene is opened in the Editor
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
- Switching between UI Documents with different Canvas sizes marks the UXML file as dirty
This is a duplicate of issue #1375015