Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.62f1
6000.0.50f1
6000.1.5f1
6000.2.0b3
Issue ID
UUM-107644
Regression
No
Light Emission "Temperature" value does not change when manually inputting the value and sliding the slider
Reproduction steps:
1. Open the attached “IN-103186.zip” project
2. Open the “SampleScene”
3. From the Hierarchy, select the "Directional Light" GameObject
4. In the Inspector, in the Light Component find the Emission tab
5. In the Temperature property, enter any value manually
6 Use the Temperature slider to modify the value
7. Observe the value
Expected result: The value in the property field changes with the slider
Actual result: The value in the property field does not change
Reproducible with: 2022.1.0a1, 2022.3.62f1, 6000.0.50f1, 6000.1.5f1, 6000.2.0b3
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- The actual light value changes in the Scene
- If Enter is pressed after inputting the value, everything works as expected
- If after the value is entered and something else is clicked on to remove focus, the value reverts to the previous one
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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.