Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b4
Votes
1
Found in
2021.3.34f1
2022.3.17f1
2023.2.4f1
2023.3.0b1
Issue ID
UUM-59676
Regression
Yes
Lighting in the Scene changes after duplicating a GameObject
How to reproduce:
1. Open the user’s attached “KughtProblem35.zip” project
2. In the Hierarchy, select “DinnerTable” GameObject and duplicate it
3. Move the duplicated object and observe the lighting
Expected result: Lighting is the same as before the 2nd step
Actual result: Lighting is different after the 2nd step
Reproducible with: 2021.3.29f1, 2021.3.34f1, 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Not reproducible with: 2021.3.28f1
Reproduced on: macOS 13.6.3 (Intel)
Not reproducible 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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.3.0b4):
Fixed in: 2023.3.0b4
Resolution Note (fix version 2023.2.13f1):
Fixed in: 2023.2.13f1
Resolution Note (fix version 2022.3.21f1):
Fixed in: 2022.3.21f1
Resolution Note (fix version 2021.3.36f1):
Fixed in: 2021.3.36f1