Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a13
2019.1.1f1
2019.2.0a1
2019.3.0a1
Issue ID
1155255
Regression
Yes
3D Template's default "Sample Scene" has "Auto Generate" lighting setting enabled while newly created scenes have it disable
How to reproduce:
1. Open attached project "LightMapTest.zip" (or create a new project with 3D template)
2. Compare "Sample Scene" lighting with the "New Scene" lighting (or compare "Sample Scene" with newly created scenes)
Expected result: both scenes are lit, "Auto Generate" options are enabled
Actual result: newly created scenes ("New Scene") have "Auto Generate" option disabled
Reproducible with: 2019.1.0a13, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
Not reproducible with: 2017.4.27f1, 2018.2.21f1, 2018.4.1f1, 2019.1.0a12
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
Resolution Note (2019.3.X):
This is by design. SampleScene templates have remained unchanged, while new user-created scenes now have Auto Generate disabled by default. This was a widely-requested feature request.