Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/TheCyaniteProject/PathFinder3D
3D A* Pathfinding that doesn't need baked navmeshes and can be used with dynamically created terrain (MapMagic or other)
https://github.com/TheCyaniteProject/PathFinder3D
3d astar-pathfinding dynamic pathfinding realtime unity3d
Last synced: 4 months ago
JSON representation
3D A* Pathfinding that doesn't need baked navmeshes and can be used with dynamically created terrain (MapMagic or other)
- Host: GitHub
- URL: https://github.com/TheCyaniteProject/PathFinder3D
- Owner: TheCyaniteProject
- Created: 2021-10-01T14:07:43.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2022-09-28T22:31:59.000Z (over 1 year ago)
- Last Synced: 2024-01-14T18:25:50.047Z (5 months ago)
- Topics: 3d, astar-pathfinding, dynamic, pathfinding, realtime, unity3d
- Language: C#
- Homepage:
- Size: 18.7 MB
- Stars: 66
- Watchers: 3
- Forks: 9
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Lists
- awesome-unity3d - PathFinder3D - 3D A* Pathfinding that doesn't need baked navmeshes and can be used with dynamically created terrain (MapMagic or other) (Open Source Repositories / AI)
README
# PathFinder3D
3D A* Pathfinding that doesn't need baked navmeshes and can be used with dynamically created terrain (MapMagic or other)
PathFinder3D (Also check out my original [PathFinder](https://github.com/TheCyaniteProject/PathFinder) for 2D games) is an asset that allows for pathfinding on dynamically created levels. I created this asset so I could have an easy to configure Pathfinding for [MapMagic 2](https://assetstore.unity.com/packages/tools/terrain/mapmagic-2-bundle-178682)
You can center the pathfinding grid on the level (pathfinding across the entire level), the player (pathfinding only near the player), or the agent (pathfinding that follows the agent).
Climbing things is more costly, so agents will prefer to go arround things when possible, but will still climb things to reach the player.
There's a layermask for what you define as 'terrain' (that the agent can move over/on), and one for what you defind as 'obsticle' (that the agent will avoid/go around)
The pathfinding drops tracking nodes down on to the terrain layers, and then enables/disables them if obstructions are in the way.
