Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.13f1
2023.1.19f1
2023.2.0b17
2023.3.0a13
Issue ID
UUM-56505
Regression
No
[Android] Some lights do not apply changes and instead copies properties from another light when the Android Platform is selected
Reproduction steps:
1. Open the attached project "ReproProj" with Android platform
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Select “Spot Light“, “Spot Light (1)“, or “Spot Light (2)“ GameObject
4. In Inspector, try changing the Rotation, Color, or Intensity
5. Repeat steps 3 and 4 for each Spotlight GameObject
Expected result: Each Spotlight applies changes but does not affect other Spotlights
Actual result: Some Spotlights do not apply changes and instead copies properties from another Spotlight
Reproducible with: 2021.3.32f1, 2022.3.13f1, 2023.1.19f1, 2023.2.0b17, 2023.3.0a13
Reproducible on: Windows 10 Enterprise 21H2 (Android Platform)
Not reproducible on: Windows 10 Enterprise 21H2 (Windows Platform)
Notes:
- Reproducible with OpenGLES3 and Vulkan
- Reproducible with other types of light
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function 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.