Search Issue Tracker
Won't Fix
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
- Button OnClick event remains the same when the selected function is changed to private
- [DX12] Crash on ShaderLab::SubProgram::Compile or freeze when compiling a specific Ray Tracing shader
- [Android] [OpenGLES3] Some of the shadows are not rendered when deployed with OpenGLES3 Graphics API on Android
- Ghosting around GameObjects while moving when using Fast Approximate Anti-aliasing (FXAA)
- Build becomes unresponsive when enabling "Deep Profiling Support" and "Autoconnect Profiler" build options in a specific project
Resolution Note:
It is not possible to reproduce this issue due to a broken reproduction project.