Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0f6
2020.1.0a22
Issue ID
1217996
Regression
Yes
GPU Lightmapper produces invalid texels in a certain scene
Steps to reproduce:
1. Open the scene ArtPresent.
2. Bake GI using the GPU Progressive Lightmapper (options don't matter).
3. Notice that most texels in the scene are invalidated.
Notes:
- Switch to Texel Validity visualisation in the Scene View. Observe that a big amount of pixels in the scene are invalid.
- Clearing the GI Cache, clearing Baked Data for the scene or manually deleting the folder that contains it don't fix the issue. The only way to fix the issue is to transfer the gameobjects to a fresh new scene.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment