Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
Issue ID
1190228
Regression
No
[GPU PLM] Texels are marked as invalid when hitting a backface even with 0 bounces
Steps to reproduce:
1. Open the attached project (GPUPLMInvalidTexelsTest01)
2. Navigate to Lighting Settings and make sure that Progressive CPU is set as the lightmapping backend
3. Bake the lighting
4. Now switch lightmapping backend to Progressive GPU and rebake
5. Notice the artifacts caused by invalid texels
Notes:
- Reproduces only with GPU PLM when Bounces count is set to 0
- If Bounces count is set to > 0 the issue reproduces on both backends - that is expected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment