godotengine / godotengine/godot-docs

get_point_path() it say's it won't work in a thread but it does, are the docs wrong.

Open
#5,641 0 comments 0 reactions 0 assignees View on GitHub
area:class reference bug
Dominant language
reStructuredText
Stars
5.7k
Forks
3.8k
Avg merge
1d 20h
Merged PRs (30d)
25

Description

3.3

Sorry if this question is formatted badly but it was on the q&a site for a year or so and no one explained why this happened so I decided to put it here, but since I have for the most part forgotten about this and am not even sure it is still a thing I just copy and pasted it, also because I'm lazy :P

If you were to control-click on this function `astar2d.get_point_path()` it would tell you that it doesn't work in a thread, and I programmed my multi-threaded pathfinding system with that in mind, but then I decided to try it anyway because it could offer higher performance. It worked perfectly. Also to anyone who might think that it isn't running on a separate thread and just looks like it is, I know it is because everything it does is completely desynced from the main thread and I spent 2 days trying to make it not crash because of that.

But my main point is, it said it would output an error and an empty `PoolVector2Array` but it didn't, instead it returned a working valid astar2d path.

It says it won't work in the online docs. [https://docs.godotengine.org/en/stable/classes/class_astar2d.html?highlight=astar#class-astar2d-method-get-point-path](https://docs.godotengine.org/en/stable/classes/class_astar2d.html?highlight=astar#class-astar2d-method-get-point-path)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.