You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The characters continuously request paths to the destination (as a result of their needs behaviours) almost flooding the system. However, the characters don't seem to have a direction for moving at all. They just sit idle.
Why it happens.
After investigation, the characters request for a path returns a successful path (The future is set to a valid result) however, the path always seems to have no WalkableBlocks in it's nodes. Hence, the characters have no path to actually follow along (in the move_along_path and move_to behaviours). The characters then keep requesting paths, possibly creating strain on the system. Maybe the NavgraphSystem is not tracking the blocks being added later by DC (example, while filling the floor before placing the house). Thus, whenever a path is requested, to the NavGraphSystem, it looks like the path is being requested from some point in the air. This point doesn't have any attached blocks to it (It's just a point hanging in the air). Thus, the NavGraphSystem is unable to return a valid path
How to fix
Improvements to the UdateChunk events and NavGraphChanged events.
The text was updated successfully, but these errors were encountered:
Pathfinding Issues
Related to #29
What happens
The characters continuously request paths to the destination (as a result of their needs behaviours) almost flooding the system. However, the characters don't seem to have a direction for moving at all. They just sit idle.
Why it happens.
After investigation, the characters request for a path returns a successful path (The future is set to a valid result) however, the path always seems to have no WalkableBlocks in it's nodes. Hence, the characters have no path to actually follow along (in the move_along_path and move_to behaviours). The characters then keep requesting paths, possibly creating strain on the system. Maybe the NavgraphSystem is not tracking the blocks being added later by DC (example, while filling the floor before placing the house). Thus, whenever a path is requested, to the NavGraphSystem, it looks like the path is being requested from some point in the air. This point doesn't have any attached blocks to it (It's just a point hanging in the air). Thus, the NavGraphSystem is unable to return a valid path
How to fix
Improvements to the UdateChunk events and NavGraphChanged events.
The text was updated successfully, but these errors were encountered: