Search Issue Tracker
Active
Under Consideration for 6000.4.X, 6000.5.X, 6000.6.X
Votes
0
Found in
6000.0.70f1
6000.3.11f1
6000.4.0b11
6000.5.0a8
6000.6.0a2
Issue ID
UUM-137127
Regression
No
The snapToHeightmap parameter of the SetTreeInstances method is ignored when calling SetHeights on Terrain
How to reproduce:
1. Open the attached “IN-136057“ project
2. Open the “SampleScene“ scene
3. Enter Play mode
4. In the Game view, note the y-axis positions of the Terrain’s trees
5. In the Hierarchy window, select the “Reproduction“ GameObject
6. In the Inspector, open the Context Menu of the “Reproduction (Script)“ Component and select “Set Terrain Heights”
7. Repeat step 4
Actual result: The trees were snapped to the Terrain’s Height Map
Expected result: The trees remained in the same position on the y-axis
Reproducible with: 2023.1.0a1, 6000.0.70f1, 6000.3.11f1, 6000.4.0b11, 6000.5.0a8
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Workaround: Instead of using SetHeights(), use SetHeightsDelayLOD()
Note: The provided workaround may cause the terrain to be rendered at an inappropriately high level of detail
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
Add comment