Does this service throttle pathfinding requests? Because after 100-150 requests in about a minute and the service starts to almost always return a path containing 0 waypoints from there on.
2 Likes
1 Like
If it’s so easy to trigger, it should be just as easy to create a simple demo file. Please include a repro file regardless.
2 Likes
I assume its the clearance area around the corner being around 2 studs. When there 2 pillars are closer together, the 2 clearance area overlaps, rendering the area undetectable.
Are we getting mesh support for this? Having a difficult time applying this to meshes.
1 Like
It’d be awesome if we could get more options in the future. Like:
- Configurable speed: The speed of the actor affects when Jump actions will be successful or not. Higher speed means longer jump.
- Configurable size: Maybe you have some giants in your game that you want for NPCs, but you don’t want them to try to fit themselves under small ceilings like smaller characters.
- Part blacklist: It’d be awesome if my NPCs could walk through closed doors. Opening doors for NPCs is easy enough, just wait til they get close enough. The hard part is making the path ignore the actual moving door part. It’d be awesome if we could tell the algorithm to ignore certain instances and their children.
- Built-in Humanoid support: A method on Humanoids that accepts a Path and possibly returns an object similar to a Tween object, that indicates the current status and have events for when the humanoid is done walking on that track. This is mostly just a time saver, but convenience methods are basically half of all methods nowadays!
- Ability to define custom “moves”? : In addition to “walk” and “jump”, we could define different actions the actor could take to mutate themselves in some way. Examples: Duck (to go under a low ceiling), Crawl, Super-jump (Superhero NPC?), Run (as a precursor to Jump, which would then create a running jump to get more distance), etc.
20 Likes
Not only that but those jump nodes that are literally on the surface of the doorway blocks are going to prevent a humanoid from getting past the door at all
YES! Thank you so much for this!
Was the issue able to be resolved by any chance?
1 Like
According to your code, the path starts at the top and finishes at the bottom.
So that yellow region isn’t a “jump” but a “fall”.
If I switch them, the path is more correct but still a little weird.
1 Like
Oh, I was playing around with the code from the wiki, I didn’t realize I was doing it backwards. Aha.
The nav mesh doesn’t update when a part becomes CanCollide = false or CanCollide = true to calculate a new route.
Is this also going to be fixed?
1 Like
How soon is that as for now?
Soon™
9 Likes
when are updates and fixes coming to this…
2 Likes
I would like to see an update with jumping as it isn’t accurate based off of the characters speed and jump height. Usually resulting in a failed jump most of the time.
2 Likes
Only since there has already been a bump, I think there should be some support for non-humanoid pathfinding, such as cars and objects with large dimensions. A wide car couldn’t fit down a narrow alley, but Pathflinding Service at the moment would still recommend it as a path.
Also @tomgie, in the future try not to bump very old threads. Feel free to post your thoughts in #platform-feedback:engine-features for feature requests that effect the in-game experience.
2 Likes
Have you worked with the newer agent-parameter API?
5 Likes
Please use the Platform Feedback category.
1 Like