Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a9
2019.1.0a14
2019.2.0a1
Issue ID
1118605
Regression
Yes
Height of the Terrain is calculated without using Y position of the GameObject when setting height in Terrain component
How to reproduce:
1. Open attached project "Case_1118605_TerrainHeight"
2. Open "SampleScene" scene
3. Select Terrain GameObject in the hierarchy
4. Set the height of the Terrain to 10 and click "Flatten"
5. Set Y position of the Terrain GameObject to 10
6. Click "Flatten" again
Expected result: The Terrain does not change its height in the world perspective
Actual result: Terrain height is lowered in the world perspective
Reproducible with - 2019.1.0a9, 2019.1.0a15, 2019.2.0a2
Not reproducible with - 2017.4.19f1, 2018.3.3f1, 2019.1.0a8
Comments (1)
-
DeathRace26
Nov 11, 2019 14:53
This issue is actually reproductible in 2018.4.11
Please, fix this for newest stable release
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
- URP Cascaded Shadows do not have a falloff in Player when the Player is built not in Development Mode
- Grid in animation preview window is rendered on top of the object
- WebGPU Graphics.RenderPrimitives fails on MeshTopology.Quads with Validation errors when exceeding 64k vertices
- Task status is "WaitingForActivation" when awaiting a faulted task inside that task
- 0 is returned when any output from Split Node is input into the Lerp Node
Resolution Note (fix version 2019.3):
Fixed in 2019.3.0a11