Search Issue Tracker
By Design
Votes
0
Found in
4.1.0b3
Issue ID
521176
Regression
No
Agent calculate not optimal path using LayerCost
Agent calculate not optimal path when using LayerCost
Check out attached screenshots
To reproduce use attached project
Comments (1)
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
- ScrollView clips content when under an ancestor that has a filter set
- "Retrieving array element that was out of bounds" error thrown when attempting to remove a column from a Multi-Column List View
- Multi-Column List View horizontal scroll resets to left most position when scrolling vertically
- Floating License is lost for concurrent jobs
- Warning "Failed to insert item" is logged when Assigning Project to Organization's Project in the Project Settings
Myosotis
Dec 29, 2014 13:20
What is meant by "By Design"?
Isn't setting layer cost meant to help you obtain the optimal path? Its a serious bug making Navmesh layer feature not usable at all.