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
- [URP] Incorrect tree shadows are shown in Play Mode when SRP Batcher is enabled
- [iOS][UaaL] After unloading a Unity scene, memory remains allocated depending on how much memory was used in the scene
- [WebGL] "Unable to open archive file" error is thrown in Build when "Compress Local Catalog" option is enabled for Addressables
- editor crashes on trying to open project on a very long path
- Performance in Game View is significantly impacted by Gfx.WaitForPresentOnGfxThread when a second monitor is connected
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