Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.2.2f1
2023.1.0a11
2023.2.0a19
2023.3.0a5
6000.0.0b11
Issue ID
UUM-20625
Regression
Yes
[AMD] [DX11] Additional lights are broken when Spotlight is added to the Scene
Reproduction steps:
1. Open the attached project "My project"
2. Make sure that the Editor is using DX11
3. Switch platform to the Android
4. Right-click on the Hierarchy, hover over Light, and click Spotlight
Expected result: Lights with color stay colored
Actual result: Lights with color lose color
_Reproducible with: 2022.1.0a13, 2022.2.17f1, 2023.1.0a1, 2023.2.0a11, 2023.3.0a5_
_Not reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.1.0a12, 2023.1.0a2, 2023.1.0b13_
Reproducible on: Windows 10 Enterprise 21H2
Notes:
- When you put more than 1 additional light on the Scene, all lights copy properties from one (Color, type)
- More info in the Unity Forum: [https://forum.unity.com/threads/so-tired-because-regressions-after-each-update.1348976/]
- *Android Platform must be selected to reproduce*
- *Direct3D11 must be selected to reproduce*
- When DX12 is selected the 2 lights that are already in the Scene are green and red, but when switched to DX11 they both become green
- *AMD GPU required to reproduce, doesn't repro on NVidia*
Workaround: Use another rendering backend than DX11. Both DX12, Vulkan and OpenGL seem to work fine.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
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.