Search Issue Tracker
Duplicate
Duplicate in 2019.3.X
Votes
0
Found in
2019.2
2019.3
2020.1
Issue ID
1186840
Regression
Yes
4K lightmaps broken unless you clear the GI Cache before every bake
4K GBufferHeavyData positions written to GI Cache doesn't match what is read back later on.
This issue makes it impossible to work with 4K lightmaps unless you clear the GI Cache before every bake.
1) Create a test scene that generates a 4K lightmap.
2) Bake lighting.
3) Observe that the lightmap is ok.
4) Clear baked data.
5) Bake lighting.
6) Observe that the lightmap is broken.
7) In debug builds, this assertion is printed in the log "CacheWSData: numValidPositions should match m_OccupiedSampleCount!"
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