Search Issue Tracker
Fixed
Fixed in 6000.0.6f1, 7000.0.0a2
Votes
0
Found in
2023.2.18f1
6000.0.0b15
7000.0.0a1
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Add comment