Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
8
Found in
2021.3.6f1
2022.1.5f1
2022.2.0b1
2023.1.0a1
Issue ID
UUM-8789
Regression
No
Light Probe is incorrectly generated when Lighmapper is set to Progressive GPU
How to reproduce:
1. Open the attached project “Lightprobe”
2. Open the scene “st_02_00“
3. In the Lighting window change the Lightmapper field to Progressive CPU and Generate Lighting
4. Change the Lightmapper field to Progressive GPU (Preview) and Generate Lighting
5. Observe the result
Expected result: The Light Probe is generated the same way (The Sphere is in the shadows, so it should be dark)
Actual result: The Light Probe is generated incorrectly using Progressive GPU (Preview)
Reproduced with: 2021.3.6f1, 2022.1.5f1, 2022.2.0b1, 2023.1.0a1
Could not test with: 2019.4.38f1, 2020.3.36f1 (Compilation errors)
Reproduced on: Windows 11 Pro
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
It is not possible to reproduce this issue due to a broken reproduction project.
Resolution Note (2023.1.X):
It is not possible to reproduce this issue due to a broken reproduction project.