Search Issue Tracker
Fixed in 5.0.1
Votes
6
Found in
5.0.0f3
Issue ID
675843
Regression
Yes
[Raycast] When terrain is changed but not saved, RaycastHit.point returns incorrect value
Steps to reproduce this issue:
1. Open 'TerrainRaycastBug' project
2. Open 'TerrainRaycastBug' scene
3. Switch to scene view
4. The redline indicates raycast, green sphere indicates a hit point with terrain
5. Change the shape of a terrain in the place where the hit point appears
6. Notice green sphere(hit point) does not follow with the changing shape
7. Save the scene
8. Everything fixes up
Regression since 5.0.0f3
How to reproduce: http://youtu.be/DpvH_nYeu6A
Comments (5)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Nesvi
Mar 25, 2015 18:20
Same problem here.
maikkel
Mar 17, 2015 01:32
Yes, the terrain collider seems to be flipped diagonally when the terrain is edited during runtime (or the terrain tools in the editor)
This is quite a severe bug, I'll have to go back to version 4 until this is fixed, because dynamic terrain deformation is a major feature in my current project.
ArminHarbick
Mar 08, 2015 05:07
It looks like editing the terrain on the X axis changes the terrain collider on the Z axis, and vice versa.
ArminHarbick
Mar 08, 2015 03:15
I've got about the same problem.
I've noticed that when I create a hill, the collider for that hill is somewhere else on the terrain. Approximately mirrored across an axis, but not exactly.
Enzx
Mar 04, 2015 14:21
I have same problem,
terrainData.SetHeights and terrainData.GetHeigts are working like version 4 but terrian collider doesn't update after Setting height in runtime.
Also, Terrain.CreateTerrainGameObject() doesn't seem to create new collider from terrainData.