Search Issue Tracker
Fixed in 2019.3.X
Votes
6
Found in
2018.3.14f1
2019.1.0a9
2019.2.0a1
2019.3.0a1
Issue ID
1150178
Regression
Yes
Terrain position in world space is counted when sampling Terrain Height
How to reproduce:
1. Open attached project ('1150178repro')
2. Click on 'Terrain' object and in the Terrain component, click on 'Paint Terrain' tool
3. Set the tool to 'Set Height'
4. Hold shift (or control, depending on what the tooltip says) and click on any part of the terrain
Expected results: Returned height is only relative to the Terrain object (0 on flat terrain)
Actual results: Returned height is relative to the Terrain object + the object's Y coordinate in world space
Reproducible with: 2018.3.14f1, 2019.1.1f1, 2019.2.0a10, 2019.3.0a1
Not reproducible with: 2017.4.26f1, 2018.3.6f1, 2019.1.0a8
Regressions: 2018.3.6f1 -> 2018.3.7f1 and 2019.1.0a8 -> 2019.1.0a9
Could not test with later 2019.2 versions due to the project immediately crashing.
Note: Since the height of Terrain can only fit between 0 and 600, when the Terrain object is outside these bounds, flat terrain for example will return either 0 (when Y is negative) or 600 (when Y is positive).
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
mohammadgarous
Aug 26, 2019 07:27
very bad bug please fix in 2019.1.14F