Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.5.0p3
Issue ID
910223
Regression
No
Using NavMeshAgent and NavMeshObstacle simultaneously, Y coordinate of the object moved by NavMeshAgent becomes MaxValue
To reproduce:
1) Open attached project and scene
2) Play it
3) Select Player object in hierarchy to see its Y value in inspector
4) Using arrowkeys, move the object to behind the other object
5) Move into the other object from behind
Expected: Object is blocked from moving
Actual: Object disappears from view as Y value is changed to 3.402823e+38
Reproduced in 5.5.0p3, 5.5.3p3, 5.6.1f1, 2017.1.0b5 (player is more clamped in 2017, so it is harder but still reproducible)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment