Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.42f1
2022.3.41f1
Issue ID
UUM-77827
Regression
No
The Intensity property on the Debug Inspector will show the original value but the Normal Inspector will show the value applied to the Prefab when reverting all of the overrides on the Prefab instance
How to reproduce:
1. Open the “LightPrefabIssue“ project
2. Open the “OutdoorsScene“
3. Open a second Inspector window with “More Items (*⋮*) > Add Tab > Inspector“
4. Open the “LightTest“ Prefab instance in both of the Inspector windows
5. Set the first Inspector window to Debug mode
6. In the Normal Inspector window set the Intensity property of the Light component to 0
7. Right-click on the Intensity property and choose Apply to Prefab 'LightTest'
8. In the Normal Inspector window click on the overrides drop-down window and choose Revert All
9. Observe the Debug Inspector windows Intensity property (“Light.m_Intensity”) in the Light component
Expected result: The Intesity value in the Debug Inspector Light component is 0
Actual result: The Intesity value in the Debug Inspector Light component is 79.57747
Reproducible with: 2021.3.42f1, 2022.3.41f1, 2023.3.0b4
Not reproducible with: 6000.0.14f1
Fixed in: 2023.3.0b5
Reproducible on: macOS 14.5 (Intel), Windows 10 Pro (22H2)
Not reproducible on: No other environments 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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.