Skip to content
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

NavigationMesh dynamic obstacle detection #3130

Closed
soloparatolos opened this issue Dec 23, 2015 · 11 comments
Closed

NavigationMesh dynamic obstacle detection #3130

soloparatolos opened this issue Dec 23, 2015 · 11 comments

Comments

@soloparatolos
Copy link

NavMesh is working great right now but lacks the ability to detect Bodies and Areas in real time to calculate paths when something changes in the scene. Implementing something like this seem really relevant.

@reduz
Copy link
Member

reduz commented Dec 23, 2015

I've been thinking about how to do this, it should hopefully not be that
difficult

On Wed, Dec 23, 2015 at 4:43 PM, soloparatolos notifications@github.com
wrote:

NavMesh is working great right now but lacks the ability to detect Bodies
and Areas in real time to calculate paths when something changes in the
scene Implementing something like this seem really relevant


Reply to this email directly or view it on GitHub
#3130.

@soloparatolos
Copy link
Author

I never tried Urho 3d but I've seen they have something like this. Dont know if their approach can be acceptable for Godot.

@reduz
Copy link
Member

reduz commented Dec 23, 2015

They use recast, but I prefer something more customizable
On Dec 23, 2015 17:12, "soloparatolos" notifications@github.com wrote:

I never tried Urho 3d but I've seen they have something like this. Dont
know if their approach can be acceptable for Godot.


Reply to this email directly or view it on GitHub
#3130 (comment).

@soloparatolos
Copy link
Author

Perfect, more options are always better.

@reduz reduz added this to the 2.1 milestone Jan 10, 2016
@akien-mga akien-mga modified the milestones: 2.2, 2.1 Jul 15, 2016
@akien-mga
Copy link
Member

Not critical for the upcoming 2.1, so moving to the next milestone.

@akien-mga akien-mga removed this from the 2.2 milestone Sep 18, 2017
@akien-mga
Copy link
Member

What's the status on this in the current master branch?

@reduz
Copy link
Member

reduz commented Sep 18, 2017 via email

@akien-mga
Copy link
Member

We've planned to work on navigation issues for 3.2, so moving to that milestone.

@akien-mga akien-mga modified the milestones: 3.1, 3.2 Sep 15, 2018
@Byteron
Copy link
Contributor

Byteron commented Jun 12, 2019

Is this being worked on now?
Certainly would be useful to have.

@regakakobigman
Copy link

regakakobigman commented Aug 30, 2019

Will this be making it into 3.2 before the feature freeze?

@Calinou
Copy link
Member

Calinou commented Mar 19, 2020

This was implemented by #34776, closing.

@Calinou Calinou closed this as completed Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants