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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.