Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2018.1.0b5
Issue ID
996092
Regression
No
NavMesh Agent is still considered on OffMesh Link at 0 position X
Reproduction steps:
1. Download "Test.zip" project and open in Unity
2. Open "ObstacleTest" scene
3. Select "Guy" in Hierarchy and set its position X to 0
4. Enter Play mode
5. Go straight (press "W" or up arrow key) and press shift to jump over the wall
6. Go back (press "S" or down arrow key)
Expected: player "Guy" stands in place
Actual: going back makes the player's movement glitch
Reproduced on: 5.6.5p1; 2017.1.3p1; 2017.2.1p3; 2017.3.1p1; 2018.1.0b6; 2018.2.0a1
Note: reproducible on Mac and Windows
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Will be fixed as part of substantial refactoring work planned for the NavMeshAgent.
More information will be communicated on the Navigation forum. https://forum.unity.com/forums/navigation.79/