Search Issue Tracker
Fixed
Fixed in 6000.0.48f1, 6000.1.0f1, 6000.2.0a7
Votes
1
Found in
6000.0.21f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-82822
Regression
Yes
Light2D Shadows and Volumetric configurations are overwritten when multiple lights are selected in the Hierarchy
How to reproduce:
1. Open the attached “IN-84851“ project
2. Open the SampleScene
3. Observe the Scene window and note that all three lights present on the scene have different configurations
4. In the Hierarchy window, select all three lights (their names start with “SportLight3”) by holding Shift or Ctrl
5. Observe the Scene window
Expected result: Each light should maintain its configuration
Actual result: The lights change their configuration, all copying the configuration from one of the selected lights
Reproducible in: 2023.1.0a18, 6000.0.21f1
Not reproducible in: 2021.3.44f1, 2022.3.48f1, 2023.1.0a17
Reproducible on: Windows 10 (by user), Windows 11
Not reproducible on: No other environment tested
Workaround:
Set the Inspector to Debug mode before selecting several lights at once
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Add comment