Search Issue Tracker
Won't Fix
Unknown (hidden) 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X, 2021.3.X, 2022.1.X, 2022.2.X, 2023.1.X
Votes
6
Found in
2020.3.0f1
2021.3.3f1
2022.1.1f1
2022.2.0a15
2023.1.0a1
Issue ID
UUM-2496
Regression
Yes
NavMesh::Raycast freezes the whole editor in an infinite loop on Application.UpdateScene
How to reproduce:
1. Open the user attached project
2. Open "SampleScene"
3. Select "NavMeshCastTest" in the Hierarchy
4. Change its X position
Reproducible with: 1.0.0-exp.1 (2020.3.0f1, 2020.3.34f1, 2021.3.3f1, 2022.1.1f1, 2022.2.0a15)
Not reproducible with: 1.0.0-exp.1 (2019.4.39f1)
-
MorpheusXI
Sep 15, 2022 16:45
Please clarify the status of this AI issue and versions affected please > is (2019.4.39f1) affected?
- Found in
2019.4.39f1
- Not reproducible with: 1.0.0-exp.1 (2019.4.39f1)Thanks
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
The workaround provided to the customer fixed the issue:
Adding an offset to the NavMeshSurface, so that the tile-grid is not constantly aligned with the 2d walkable area. Moving the local transform of the object holding the NavMeshSurface can help creating the offset without having to move other objects in the environment.
Resolution Note (2021.2.X):
fix only required in 2021.3
Resolution Note (2021.1.X):
fix only required in 2021.3