Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b11
Issue ID
951618
Regression
No
Physics.Raycast hits ghost collider if gameObject has attached Character Controller and Physics.autoSimulation is set to False
Steps to reproduce:
1) Download attached project 'BugReport_Physics_Raycast.zip' and open in Unity
2) Open scene 'Scene' and press Play
3) Select 'Player' gameObject and change the position of X axis in the Inspector window
Note that physics.Raycast hits ghost collider
Expected result: Raycast should detect updated gameObject with Character Controller attached (check attached video 'expected.mp4')
Actual result: Raycast hits ghost collider (check attached video 'actual.mp4')
Reproduced with: 2017.1.0b2 2017.1.0f1, 2017.1.1p2, 2017.2.0f1, 2017.3.0b1
Note that Raycast does not hit a ghost collider if Character Controller on the gameObject is disabled and Capsule collider is attached
Physics.autoSimulation definition was included from Unity 2017.1.0b2
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Peter77
Sep 22, 2017 13:16
You can find out why this issue has been closed "By Design" in this thread:
https://forum.unity.com/threads/case-951618-physics-raycast-hits-ghost-collider.495817/