Game Development Stack Exchange is a question and answer site for professional and independent game developers. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm creating a path-finder for navmesh. I'm wondering which method should I use after the A* has been completed, funneling or string pulling? What are the advantages/disadvantages of using them on a triangle-based navmesh?

share|improve this question
I might be completely wrong here since I looked both these algorithms up the other day, but aren't they essentially one and the same thing? – Ray Dey Jan 12 '11 at 16:25
@Ray Dey, both can be used to accomplish path refining in a mesh after the path-find has been executed. – Shawn Mclean Jan 12 '11 at 16:29
Sorry, what I meant to say was WHEN I looked both these algorithms up, they seemed to point to the same resources (on Google anyway) – Ray Dey Jan 12 '11 at 17:12
up vote 1 down vote accepted

If you're stopping condition for the funneling algorithm is the invalidity of the cone I think you'll get pretty much the same end result than with string pulling.

But using another stopping condition you can produce more various behaviors by setting a particular aperture threshold and/or by tweaking how the local target/velocity is chosen in the final cone.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.