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
- Shader Compiler IPC Exception and Editor Crash on AMD 9000-X3D CPU series
- Editor crashes in TextLib::FindIntersectingLink when hovering UITK Labels with <link> tags rendered via ATG
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
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.