forked from Azurblau/AzBot
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
D3Bot uses too expensive calls every frame #57
Labels
Comments
I know of the problem, it's mainly because the closest node needs to be found for bot/target localisation. And right now this is done by iterating over all nodes. This happens at the rate of 1/s, and i don't want to reduce it further. Here are some things that can be improved:
|
Dadido3
added a commit
that referenced
this issue
Jun 23, 2020
I found some more stuff that could be optimized. It should run a bit smoother now, it's not perfect, but much better than before. |
Dadido3
added a commit
that referenced
this issue
Sep 23, 2022
Dadido3
added a commit
that referenced
this issue
Sep 23, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even on navmesh-optimized maps bots do too many calls each frame, causing the server's CPU to go down and overload, and AFAIK as well as the entire navmesh table is checked for proper nodes. Currently only one way to reduce the lag is either to optimize the navmesh (which is very limited at this point) or remove bots as at higher bot amounts the entire server starts lagging down.
Maybe reduce the number of calls required/do it per x frames, or cache the navmesh table to prevent going through 1000+ objects?
The text was updated successfully, but these errors were encountered: