Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.1.0f3
Issue ID
942082
Regression
No
NavMesh returns incorrect NavMeshBuildSettings when accessing via GetSettingsByID
To reproduce:
1. Open user's project
2. Enter Play mode
3. Observe console
Expected: console prints out identical data as ID's are the same
Actual: console prints out default NavAgent data disregarding the same ID's
Reproduced in: 5.6.3p2, 2017.1.0p5, 2017.2.0b8, 2017.3.0a5
Note: feature not available in earlier versions
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
- Builds fail with "System.IO.IOException: The file is too long" when building a specific project
- Meta Quest System Keyboard does not render text in its input field when typing
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
Resolution Note:
Will be fixed as part of work planned for improving Navigation workflow.