Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.4f1
Issue ID
1085632
Regression
No
PhysicsDebugger visualization of GameObject doesn't display correctly when GameObject has Character Controller component
Steps to reproduce:
1. Open project in "PhysicsDebuggerBug.zip"
2. Open BugScene
3. Select the GameObject "Character"
4. Open the Physics Debugger window
5. Select "Collision Geometry" in Scene view if not already checked
6. Try to move around selected GameObject
Expected result: Physics Debugger's visual representation of "Character" GameObject should move with him and fit into its collider gizmo.
Actual result: Physics Debugger's visual representation of "Character" GameObject does not move with him and is smaller than its collider gizmo.
Reproduced in 2017.4.12f1, 2018.1.9f2, 2018.2.11f1, 2018.3.0b4, 2019.1.0a3
Note: If you press Play and then try to move selected GameObject Physics Debugger's visual representation does move with it, but it is still smaller than "Character" collider gizmo.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Solving this case requires adding an overhead to the update sequence so I think it would have to be done later on when we have the pipeline ready for the change.