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
- 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
Add comment