Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.40f1
2021.3.11f1
2022.1.18f1
2022.2.0b10
2023.1.0a14
2023.2.0a1
Issue ID
UUM-17124
Regression
No
Light is not fully displayed when Lightmap Encoding is set to Low or Medium Quality
Steps to reproduce:
1. Open the user’s attached project
2. Open the “Assets/lightbake_error.unity“ Scene
3. Navigate to Edit > Project settings > Player > Other Settings
4. Change the “Lightmap Encoding“ to “High Quality“
5. Observe the white circle in the Scene view (the light is fully displayed and no part of it is missing)
6. Change the “Lightmap Encoding“ to “Low Quality“ or “Medium Quality“
7. Observe the white circle in the Scene view
Expected result: The light is fully displayed and no part of it is missing
Actual result: The middle of the displayed light is missing
Reproducible with: 2020.3.40f1, 2021.3.11f1, 2022.1.18f1, 2022.2.0b10, 2023.1.0a14
Reproducible on: Windows 10
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
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
- Profiling information icon does not update for Light Mode
- [Linux] Type to select functionality is missing for drop down menus
- TextMeshPro calculates Width Compression incorrectly when using certain values in the WD% field
- VFX Graph link contrasts fail WCAG guidelines
Resolution Note:
Thank you for reporting a bug to Unity.
The aforementioned issue is explained by a input file containing infinite valued pixels. We suggest working around this issue by processing the input files such that such a value does not occur.
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.