Search Issue Tracker
Fixed in 5.3.0
Votes
3
Found in
5.2.1f1
Issue ID
731607
Regression
Yes
LoadLevelAdditive assigning wrong lightmap for terrain
Reproduction steps:
1. Open the reproduction project
2. Open mainScene.unity
3. Press Play
After hitting play you can see the 2 terrains that were loaded in, are sampling from the lightmap meant for the cube in the mainScene, which is of index 0. As opposed to index 1 and 2 which are the proper lightmaps for these terrains.
Image of 5.0.2p4 https://i.gyazo.com/256c12381abef3b2c1ee4cfb4ad1039f.png
Image of 5.1.3p3 https://i.gyazo.com/9c4cf6659416c816939fee4eadeea6bc.png
Image of 5.2.1p2 https://i.gyazo.com/4a2734cb5d557629e8067ec5b999f9d5.png
note: the Sphere loaded in from terrain02.untiy correctly sampling from lightmapIndex 2 which proves this works properly for mesh renderers but not terrains.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment