recast navmesh wip #1250
Open
recast navmesh wip #1250
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT MERGE!
needs careful consideration.
As discussed with dubble on discord, I am submitting this pull request and hoping that someone else can carry on with this work.
The original work was done in december of 2023 so its based on a pretty old dev branch. I simply copied over that stuff to the newest dev branch with minimal changes to the actual gwtoolbox code. I have no idea if it still works.
Recast/Detour and its dependancies are added as plain cpp/h files and added to the cmake build process.
The idea was to build a Navmap window which is using code from Minimap. I had plans to have cool looking GUI so when a user zones in to a new map, they can select a portal or a quest marker to navigate to, it would navigate on the 2D map as well as create in game pathing render.
The in game pathing render would resemble BlishHUD and would use chatgpt triangle strip code, ie convert a vector of points into a dx9 drawable textured 3D line.
Inside this pull request there is the foundation of recast pathfinding, with no actual pathfinding being done yet. The new work on pmap node definitions by tedy are not yet implemented.
Some of my ideas:
GW1 agent radius (+ vision radius?) gets converted into a recast agent with the same radius
Monsters could have their own agents/obstacles. There could be steering behaviors to avoid monsters but this is advanced of course
There could be area cost added to certain polygons (for example icy lakes means pathfinder would avoid that area if it can)
Monster groups could have their vision radius drawn or part of the pathfinding so you can avoid mobs
Navigate towards portals, exit points, quest markers
Dungeon doors will alter the navmesh instantly
Idea to get started:
Maybe dont even bother with the Navmap window, on map load, find a list of portals and let user pick one to navigate to from a dropdown combo box, this is drawn in game and thats it. The other stuff could be added later once everything is stable.
A few images:
