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
- Crash on PluginManager::RefreshPlugins when closing the Editor without making any changes with JetBrains Rider selected as the External Code Editor and Google Mobile Ads third-party plugin imported
- GetMainLight() returns incorrect distanceAttenuation value for a Custom Shader when URP Forward+ Rendering Path is used
- Standalone Profiler crash on GuidReservations::Reserve when it is opened on a specific project
- m_RenderPipelineGlobalSettingsMap or m_SRPDefaultSettings is pointing to UnityEngine.Rendering.HighDefinition.HDRenderPipeline when High Definition RP package is removed
- Rendering Debugger fields have no padding at the bottom of the fields list
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....