I’ve had a test project in 4.14 where Ai will follow a object bouncing around. The Ai is using simple move to called on tick to a vector location that’s designated by an actor tracing to the ball with a -300 units so it’s near the object but uodates on tick the vector.
The ball has a dynamic I stick sphere around it so Ai will go around it to the location when possible and the same goes for the Ai having a sphere around them.
In 4.14 it works fine… Actors run around avoiding eachother for hours no problem.
In 4.15 after a hour or so you start to notice a jitter and lose of frames which only gets worse over time.
After using show navigation ive noted the octree grows in its time to generate in the latest build.
Did something get fixed which may have broken something?
These are my Settings and the outcome of a 9 hour game where bots played on their own.
As you can see the dirty navmesh information built over time causing the time to generate to get pretty high, granted i can close the match and start it again and it runs normal right away.
This is telling me something is not cleaning up or i’m missing a way to have it clean as it goes.
So not sure if this truely is a bug or not.
Just note again:
Ball has a collision capsule around it, set to no collision but marked as a dynamic obstacle.
Players have a collision sphere marked the same obstacle.
I am merely trying to have the bots path around each other while playing and walk around the ball when trying to get to the opposite side so facing the ball they’d be facing the opponents team side without navigation having them walk through the ball.
Sorry for the delay. I’ve left my AI Test project running overnight to see if I could get a similar result, but I didn’t see the same lag that you’re experiencing.
Could you attempt to recreate the issue in a clean project to see if you’re able to experience it elsewhere, or could you provide the current project that you’re working in so I can let it run and see if I’m able to reproduce it?
I’m marking this topic as resolved for tracking purposes, as we have not heard from you in a few days. If this issue persists, feel free to respond to this thread. For any new issues, please create a new Answerhub topic.
