Search Issue Tracker
By Design
By Design in 6000.6.X
Votes
0
Found in
6000.5.0a8
6000.6.0a1
Issue ID
UUM-135963
Regression
No
Color Temperature resets/clamps to minimum value when editing it in Lighting Search window
Steps to reproduce:
- Create a new project using Universal 3D template
- Go to Windows > Rendering > Lighting Search
- Select the "Directional Light" and find the "Color Temperature" column
- In the "Color Temperature" value field, try to enter any digit
- Observe the behavior
Actual results: As soon as the first digit is entered, the value is immediately reset/clamped to 1500 (the minimum value)
Expected results: The field should allow free text entry while the user is typing and camping to the valid range should only occur after the user finishes editing
Reproducible with versions: 6000.5.0a8
Can’t test with versions: 6000.0.69f1, 6000.3.10f1, 6000.4.0b11, 6000.5.0a7 (Lighting Search Window with such columns not available)
Tested on (OS): Windows 11
Notes:
- The issue appears to be caused by value validation/clamping running while the field is still being edited, so any intermediate value below 1500 is immediately snapped back to 1500.
- Editing the same Color Temperature value from the standard Inspector does not show this problem
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
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
The bug only happens if the edited light is selected AND shown in the insptor. What this means? The Inspector itself is enforcing bounds checking:
- The Inspector checks for the value being entered and will clamped it to its minimum.
- The Search window refresh because the value changed.
So there is no bug in search.
Resolution Note (6000.6.X):
The bug only happens if the edited light is selected AND shown in the insptor. What this means? The Inspector itself is enforcing bounds checking:
- The Inspector checks for the value being entered and will clamped it to its minimum.
- The Search window refresh because the value changed.
So there is no bug in search.