Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.1.X
Votes
1
Found in
5.6.1f1
Issue ID
916451
Regression
Yes
Elevating terrain using TerrainData.SetHeights results in Raycast not hitting some of it
To reproduce:
1. Open attached Unity project "TerrainTest2.zip"
2. Open "Scene" scene
3. Go into play mode
4. Move the mouse around the terrain in Game View
5. Observe Scene view
Expected result: Raycast should hit every place of the terrain (see attached gif "TerrainExpected.gif")
Actual result: Raycast does not hit in some places of the terrain (see attached gif "TerrainActual.gif")
Regression first introduced in: 5.6.0a1
Reproduced on: 5.6.0a1, 5.6.1p2, 2017.1.0b7, 2017.2.0a1
Not reproduced on: 5.5.3p4
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
eXonius
Aug 23, 2017 23:51
In case anyone has this problem, here is the workaround to make the collider update:
terrain.GetComponent<TerrainCollider>().enabled = false;
terrain.GetComponent<TerrainCollider>().enabled = true;