-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Algorithm used by NavMesh Velocity Component #149
Comments
See issue #146 and let me know if you still have questions. |
Ok, @curds01. The complete strategy is described in this paper (https://dl.acm.org/doi/abs/10.1145/2159616.2159619)? |
Almost. The framework for way portals is in Menge (i.e, preferred velocity is represented as a span of velocities). But each model has to implement its solution relative to a portal. Currently, none of them do. I keep meaning to port the code into the PedVO to actually make use of the portals and just never get around to it. Also, if you don't have access to acm, you can get the paper directly from: http://gamma.cs.unc.edu/WayPortals/download/curtis12_wayportal.pdf |
Thanks. |
Excuse me, how do you compute the guidance field (Picture(c) in Figure6) in your paper? I suppose there should be a simple flow field solver in your program? Is that right? I have several questions about your global navigation methods in your paper, and I would like to know how you compare these different navigation methods. |
I've moved your question to stackoverflow. Please look there for the discussion. |
When I use the already implemented NavMesh Velocity Component what algorithm is used for path planning and path following?
The text was updated successfully, but these errors were encountered: