Search Issue Tracker
Not Reproducible
Votes
9
Found in
4.2.0f2
Issue ID
550845
Regression
No
[Lightmapping] "Bake Selected" ignores Lock Atlas setting
-e 'Bake Selected' ignores Lock Atlas setting
1) Open the attached project and load the "lightmaps" scene
2) Select the sphere
3) Open the 'Lightmapping' panel
4) Expand the 'Atlas' section on the Object tab and observe that the sphere is assigned lightmap index 1
5) Turn on 'Lock Atlas' on the Bake tab
6) Click 'Bake Selected'
7) When baking has completed and Unity has finished reimporting the light maps, select the sphere and check the Atlas section of the Object tab
Expected result:
As Lock Atlas is turned on, the atlas settings for the object should not have changed; the object should still be on lightmap index 1.
Actual result:
The atlas settings have changed; the object is now on lightmap index 0.
Comments (2)
Add comment
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
zibizz1
May 05, 2015 13:39
this still ocurr in 6.6.4
bluebrain
Jul 30, 2014 05:15
This is still an issue in 4.5, we've discovered, and it's been a bit of a nightmare for us on a project over the past month.