Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2021.2.0b14
2021.2.10f1
2021.3
2022.1
2022.2
Issue ID
1400554
Regression
Yes
[URP] Terrain isn't affected by Ambient light when created with TerrainTools Package
How to reproduce:
1. Open the user's attached "My project (5)" project
2. Observe the Scene view in the "SampleScene" Scene
Expected result: "Terrain" Terrain created in the Hierarchy and "TerrainGroup_0" created using TerrainTools Package are affected by Ambient light
Actual result: Terrain created with TerrainTools Package isn't affected by Ambient light
Reproducible with: 12.0.0 (2021.2.0b14, 2021.2.19f1), 12.1.6 (2021.3.1f1), 13.1.8 (2022.1.0f1), 14.0.1 (2022.2.0a8)
Not reproducible with: 7.7.1 (2019.4.38f1), 10.8.1 (2020.3.34f1), 12.0.0 (2021.2.0b13), 14.0.2 (2022.2.0a9, 2022.2.0a11)
Note: In some versions, both Terrains don't get affected by Ambient light
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 (fix version 2022.2):
Fixed in 14.0.2 (2022.2.0a9)