Navmesh is setting some vertices to be quite above what would be the max step height of the agent when two platforms are aligned with one above the other. The navmesh may reach up to the upper platform, but it does not connect the two regions.
The navmesh goes to an expected state if Region Partitioning is set to use Chunky Monotone. It also will work as expected if the Mark Low Height Areas flag is enabled.
Expected Result: The navmesh builds to stay with the lower platform and no connection to the upper platform is made.
Actual Result: The navmesh builds triangles that extend from the bottom platform to the top platform but do not make a connection with the navmesh area on the top platform.
Request a info about UE-127172 bug tracker
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
I am not able to find world outliner how to enable it?
How can i modify the param name in EQS node
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How to achieve HLSL Multiple Render Target in Material blueprints?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-178041 in the post.
1 |
Component | UE - AI - Navigation |
---|---|
Affects Versions | 5.1.1 |
Target Fix | 5.4 |
Created | Feb 21, 2023 |
---|---|
Resolved | Feb 16, 2024 |
Updated | Feb 23, 2024 |