Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2020.1
Issue ID
1198078
Regression
No
[GI - Lightmapper] Invalid texels are not treated the same way in CPU and GPU lightmapper
Invalid texels are not treated the same way in CPU and GPU lightmapper:
When a ray (launched by lightmapper baking) hit a backface we increment a invalid texel counter. In the compositing stage we then try to fix invalid texels.
The bug is that we do not have the same behavior between CPU and GPU lightmappers.
From what I saw in the attached repro project:
-GPULM tries to filter invalid texels with neighboors valid ones hence the distorted shadow.
-CPULM doesn't seem to do anything with it.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment