Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
3
Found in
2019.4
2019.4.1f1
2020.1
2020.2
Issue ID
1263524
Regression
No
Additive loading of overlapping sets of Light Probes causes some objects to begin flickering
How to reproduce:
1. Open the user's attached "LightProbeTest.zip" project
2. Open the "UnlitScene" Scene from the "Scenes" folder
3. Enter the Play mode
4. In the Hierarchy window select the "SceneLoader" object
5. Right-click on the "SceneLoader" Script in the Inspector window and select "Load Scene Two"
6. In the Hierarchy window select the "Tetrahedralizer" object
7. Right-click on the "Tetrahedralizer" Script in the Inspector window and select "Tetrahedralize"
Expected result: Objects in the Scene get illuminated by Light Probes, no visible flickering present
Actual result: Some of the objects start to flicker
Reproducible with: 2019.4.8f1, 2020.1.2f1, 2020.2.0a21
Cannot test with: 2018.4.26f1 (due to errors)
Comments (1)
-
iamarugin
Nov 10, 2021 12:37
This fix broke Tetrahedrization completely for my project.
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0a9
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0b15
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.25f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.22f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.33f1