Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Duplicate in 2021.2.X
Votes
0
Found in
2018.4
2018.4.12f1
2020.2
Issue ID
1241302
Regression
No
Terrain normals produce artifacts when connecting neighboring Terrain using Terrain.SetNeighbors
How to reproduce:
1. Open the attached "1241302 repro"project
2. Open the "SampleScene" from the Assets folder
3. Enter Play Mode
Expected result: normals are recalculated and the two Terrains in the Scene connect seamlessly
Actual results: normals aren't recalculated and there is a visible artifact line between the two Terrains in the Scene
Reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a12
Notes:
-Using Auto Connect instead of the "SetNeighborTest" Script doesn't reproduce any broken normals or artifacts at the connection line
Comments (1)
-
gilley033
May 26, 2020 23:03
"Notes:
-Using Auto Connect instead of the "SetNeighborTest" Script doesn't reproduce any broken normals or artifacts at the connection line"Why is this the case? Auto Connect just calls SetNeighbors internally, so why should it be any different than us manually calling SetNeigbors?
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
- Assigned font's bold/font-weight styles render using Default Font's assets when Default Font has corresponding style assets defined in TMP Settings
- "Modifying the parent of a VisualElement while it’s already being modified is not allowed" error is thrown when entering text and pressing tab in the Search window
- Mesh colliders are not updating their positions of bounds correctly
- Images are missing from the "Open the sprite editor" documentation for 6.0, 6.1 and 6.2
- The previous element in the array is modified when assigning an Asset to a new element of AssetReferenceT
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.23f1
Resolution Note:
Fixed in 2020.3.23f1