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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.