Search Issue Tracker
Fixed in 5.3.0
Votes
1
Found in
5.0.1f1
Issue ID
692548
Regression
No
FPS controller collides with spherical triggers
Steps to reproduce:
1. Open attached project's scene "bug scene".
2. Select in hierarchy "FPSController" and "trigger" that their colliders would be seen.
3. Enter play mode.
4. Try moving through trigger.
5. FPSController's trajectory is not straigt then passing trigger's collider.
Bug fix was verified in 5.3.0f3 (79f30e8153f8)
Comments (4)
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
Crazydadz
May 11, 2015 20:00
Resolve: Just put a layerMask in the SphereCast of the GroundCheck() function.
Crazydadz
May 11, 2015 19:52
My bad, there is no link with the StickToGroundHelper() function...just disabling the RaycastHit Triggers get rid of the bug. But we need the RaycastHit triggers...
Crazydadz
May 11, 2015 19:22
I found the "issue", In the FPSController there is a function StickToGroundHelper() that use SphereCast and in my project RaycastHit triggers is enabled.
Crazydadz
May 11, 2015 19:01
Having the same issue. Sometimes, the FPSController is stucked at the limit of the spherical triggers....