Search Issue Tracker
Fixed
Fixed in 6000.0.27f1
Votes
0
Found in
6000.0.26f1
Issue ID
UUM-87406
Regression
Yes
Physics debugger collision geometry is always at (0, 0, 0) coordinate when a Terrain GameObject is debugged
How to reproduce:
1. Open the “TerrainDebugger.zip“ project
2. Open the “OutdoorsScene“
3. Enable Physics Debugger in Windows > Analysis > Physics Debugger
4. Check the “Collision Geometry“ checkbox in the Physics Debugger overlay in the Scene view
5. Observe the Scene view
Expected result: Physics debugger collision geometry surrounds actual terrain geometry
Actual result: Physics debugger collision geometry is translated to the (0, 0, 0) coordinate
Reproducible in: 6000.0.20f1, 6000.0.26f1
Not reproducible in: 2021.3.46f1, 2022.3.53f1, 6000.0.19f1, 6000.0.28f1, 6000.1.0a5
Fixed in: 6000.0.27f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment
Note: Colliders seem to work fine on the terrain GameObject
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment