Hello! Awesome scripts!I found that under the A* weight script, there was A memory leak because the path was drawn in real time and A* script was called A lot. However, I could never find the cause of the memory leak.
Hi! Thank you so much for pointing this out. Thought I was pretty good about memory management in there, but I must have missed something. I am going to try to get this sorted out and hopefully have a fix out in the next week.
After many hours of debugging, I believe I have found a solution to the memory leak problem. Unfortunately, its going to require me to refactor a decent chunk of the scripts. So it may be a couple more days until I am able to upload the new version.
I have just uploaded version 1.1 of the scripts and reference project! To my knowledge, all the memory leak bugs have been fixed. In a test project, I called all three algorithms every step for 5 minutes straight and saw no increase in memory usage. So hopefully this will solve your problem.
I apologize for any delay this might have caused in your development. As always, if you have any more issues with the scripts, you can post again here or message me on Twitter.
Not at the moment! But that is a great idea for an additional script that could be added to this! I may do that in the near future.
The pathfinding scripts all output arrays of coordinates, so if you want an object to follow a calculated path, then you could always convert those coordinates into a GMS path.
← Return to tool
Comments
Log in with itch.io to leave a comment.
omg how have I never found this before!
Hello! Awesome scripts!I found that under the A* weight script, there was A memory leak because the path was drawn in real time and A* script was called A lot. However, I could never find the cause of the memory leak.
Hi! Thank you so much for pointing this out. Thought I was pretty good about memory management in there, but I must have missed something. I am going to try to get this sorted out and hopefully have a fix out in the next week.
Thank you for your help
After many hours of debugging, I believe I have found a solution to the memory leak problem. Unfortunately, its going to require me to refactor a decent chunk of the scripts. So it may be a couple more days until I am able to upload the new version.
OMG,You're amazing,
I have just uploaded version 1.1 of the scripts and reference project! To my knowledge, all the memory leak bugs have been fixed. In a test project, I called all three algorithms every step for 5 minutes straight and saw no increase in memory usage. So hopefully this will solve your problem.
I apologize for any delay this might have caused in your development. As always, if you have any more issues with the scripts, you can post again here or message me on Twitter.
Hello! Awesome scripts! Have you an example to show how use it in order to move the object with the path ? Thank you!
Not at the moment! But that is a great idea for an additional script that could be added to this! I may do that in the near future.
The pathfinding scripts all output arrays of coordinates, so if you want an object to follow a calculated path, then you could always convert those coordinates into a GMS path.
https://docs2.yoyogames.com/source/_build/3_scripting/4_gml_reference/paths/inde...
I hope this helps! If you have more questions, feel free to shoot me a message on Twitter. I am more likely to respond quickly on there.
@ProtonSquid
Thanks you!