Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2018.4
2019.3
2019.3.6f1
2020.1
2020.2
Issue ID
1246726
Regression
No
NavMeshQuery.CreateLocation always returns the same point when using a NavMeshLink polygon, even if the width is > 0
How to reproduce:
1. Open user-submitted project (CreateLocationOnLink.zip)
2. Open the SampleScene
3. Select the NavMesh GameObject(rebake it if necessary)
4. Enter Play Mode
5. Open the Scene View
6. Note the position of the Debug.DrawLine and LinkLocationTester GameObject
Expected result: Debug.DrawLine is drawn at the same position as the LinkLocationTester
Actual result: Debug.DrawLine is drawn at the corner of the polygon associated with NavMesh
Reproducible with: 2018.4.23f1, 2019.3.13f1, 2020.1.0b9, 2020.2.0a11
Could not test with: 2017.4.40f1(project incompatible)
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
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b10
Resolution Note (fix version 2020.1):
Fixed in 2020.1.12f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.16f1