Integrated Path Planning issue

[happygreenfrog]

Hey, Mokhtar, do you think you could perhaps port the integrated path planning to other runtimes, by any chance? That's the one thing that all of the existing pathfinding objects have lacked so far (being available for all runtimes (though there is one pathfinding object that is available for Flash, it doesn't work in Windows, which means that, if you want a Flash version and an EXE version, you need to maintain the two separately as of now)), which is why I'm wondering.

A Flash port would be a good start, if you do end up porting it to other platforms, since it shouldn't be too hard to do if you know ActionScript (and, if you don't, it shouldn't be too hard to learn it), though, if there is another port that you think would be easier, you can port it to that runtime instead (E.G. If you don't know ActionScript, and you know Objective-C incredibly well, then an iOS port would probably be easier).

[Mokhtar]

OK, I'm finally back. I see what's happening now, it's crossing the node for a moment and the event to orient triggers before the path is updated. This could be fixed by setting a larger grid tolerance in the extension properties. But a more direct fix would be to simply slow down the orientation event a bit, it worked fine with a 5/100 of a second condition.

Of course, the ideal solution would be to have an invisible marker jump to the nodes until the agent collides with it, as that would allow for smother paths.

[Mokhtar]

Hey, Mokhtar, do you think you could perhaps port the integrated path planning to other runtimes, by any chance?

Technically it's doable of course. I would say the XNA port would be the easiest (but probably least needed). Porting the advanced features may be difficult, but a subset of the most common may be feasible. There hasn't been much demand for a port so far though. The main problem is my severe lack of time. However, if any of the extension developers has the time and is interested in porting it, I can definitely help them out.

[Panchos]

OK, I'm finally back. I see what's happening now, it's crossing the node for a moment and the event to orient triggers before the path is updated. This could be fixed by setting a larger grid tolerance in the extension properties. But a more direct fix would be to simply slow down the orientation event a bit, it worked fine with a 5/100 of a second condition.

Of course, the ideal solution would be to have an invisible marker jump to the nodes until the agent collides with it, as that would allow for smother paths.

Thanks for taking a look. I did try your first two solutions but they didn't solve it for me

I increased the grid tolerance from 8 and tried all the way up to 100 and the problem still occured. I tried it into the minus too just to check.

The second solution about slowing the orientation, do you mean adding a restrict action for 0.05 sec to the event? I did that but it didn't fix.

I've not tried the third one yet, just checking I've tried the first 2 correct before I go the marker route.

Thanks

[Mokhtar]

For the second solution: not restrict, just add an "every 0.05" condition to the orientation event.