Search Issue Tracker
Active
Votes
0
Found in
2023.2.18f1
6000.0.0b15
Issue ID
UUM-69791
Regression
Yes
Lighting Component's and Lighting Setting's Numerical fields are stored as HEX expressions and cannot be saved to Clipboard as Numerical Values when using Keyboard Shortcuts
*Steps to reproduce:*
# Open any Project
# Select a gameObject with any Light Component attached
# Select a Numerical value in any of the fields and try copying it with keyboard shortcuts and pasting it out of the Light Components (Like the Transform Component)
# Try the same with Lighting Settings Values
*Actual results:* Values copied with Keyboard Shortcuts are saved as HEX values (e.g #6B7AA0) and cannot be pasted back into any of the Lighting Area fields, values copied by right-clicking with the mouse work as expected
*Expected results:* Values are copied and saved as numerical values and copied values can be used interchangeably throughout the Editor
*Reproducible with versions:* 2023.1.0a13, 2023.1.20f1, 2023.2.18f1, 6000.0.0b15
*Not reproducible with versions:* 2022.3.25f1, 2023.1.0a12
*Tested on (OS):* Windows 11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Editor can't find Audio Spatializer when using PS5AudioSpatializer plugin
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
Add comment