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
- 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
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.