Search Issue Tracker
By Design
Votes
0
Found in
2021.3.33f1
2022.3.14f1
Issue ID
UUM-57969
Regression
No
Lighting is applied differently to GameObjects when comparing results during Play Mode and outside of Play Mode
How to reproduce:
# Open the “Test.zip” project
# Select the “Directional Light” GameObject
# Change the lighting direction and observe the Scene view
# Enter the Play Mode, repeat step 3, and observe the Scene view
Expected results: Lighting is applied the same to GameObjects in Play Mode, just like outside of Play Mode
Actual results: Lighting is applied differently to GameObjects when in Play Mode
Reproducible in: 2021.3.33f1, 2022.3.14f1, 2023.2.0a17
Not reproducible in: 2023.2.3f1, 2023.3.0a17
Fixed in: 2023.2.0a18
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
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
- Deletion prompt is opened when trying to delete a Parent Blendtree State via delete shortcut
- “Assertion Failed”, “Invalid AABB a” and Mesh errors are thrown when editing Group Seed or Frequency settings for Tree Object
- “GetAllOverlapping failed…” error when clicking a GameObject during a custom picking pass in the Scene view for the second time
- “NullReferenceException” thrown when moving control points on a tree branch in Scene view
- [Linux] Player window unexpectedly resizes to monitor dimensions when calling "Screen.SetResolution" function with hardcoded resolution matching current display's width or height
Resolution Note:
Thank you for submitting this issue with us.
This discrepancy arises from the automatic baking of environment lighting kicking off in the editor but not play mode. The solution is to bake the scene. We have removed this automatic functionality in the 2023 stream to clarify the workflow.