Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.3.X
Votes
0
Found in
2017.3.1p4
Issue ID
1044247
Regression
No
Nav Mesh Pathfinding bakes incorrectly when GameObjects are placed very specifically
How to reproduce:
1. Open the project attached by the user (Bugreport2.zip), open the "bug" Scene
2. Select "Pathfinding" in the Hierarchy
3. Observe the incorrect splicing near the "Cube" GameObject
4. Play the Scene, attempt to move the red Agent near the "Cube" GameObject
5. Observe as the Agent's pathfinding is blocked by the incorrect splicing
Expected result: The incorrect splicing does not occur and the Agent can move through
Actual result: Since the splicing is incorrect, the Agent cannot move through
Reproducible with: 2017.1.0a1, 2017.1.4p1, 2017.2.3p1, 2017.4.5f1, 2018.1.4f1, 2018.2.0b8, 2018.3.0a1
Notes: Have not been able to reproduce on my own, it seems that this requires very specific and random placing of GameObjects.
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
Add comment