|
PathFinder status
|
05-01-2015, 06:54 AM
Hello, the zombies are really polished now. I can't reproduce the air hanging error anymore, so I think it's fixed. Can you?
They don't freeze anymore, but at daylight, will not charge at you when they're hiding in the shadows unless provoked, this behavior will later be tweaked. 
About the zombies following second best path, the correct behavior would be for the zombie to check if there is a line of sight to the player, and then get the best/second best path (vanilla does that, afaik) as long as the player is in some nearby area.
05-01-2015, 10:33 PM
Update: The new AI and PathFinder branch has been merged and is now part of the official MCServer.
05-01-2015, 11:31 PM
xoft Wrote:Make Step() call the cWorld::DoWithChunk() function, then in the Item() function call the SingleStep() several times, passing the cChunk over to it for direct querying. Note that once you have a cChunk instance, you can simply get its neighboring chunks and thus query the neighborhood rather efficiently. I believe this would be such an improvement that it would invalidate the need for a cache completely. Problem: The A* algorithm is sometimes jumpy: It won't necessarily query one chunk and then its neighbors, it could jump lots of blocks at a time.
05-02-2015, 12:32 AM
It's still faster to do what xoft wrote because the slow bit is DoWithChunk, querying neighbors within DoWithChunk is cheap. The problem with that is that whilst it increases throughput, the depth limit becomes much more important because you hold the ChunkLayer lock for the entire time.
05-02-2015, 01:55 AM
(This post was last modified: 05-02-2015, 02:01 AM by LogicParrot.)
Deleted no longer relevant questions and submitted a pull request here. Please review.
05-02-2015, 02:03 AM
It's not so much about the locks - they are locked during the mob ticks anyway. It's about the chunk lookups. Each DoWithChunk() needs to locate the chunk within the world, which is not exactly trivial; if you do that for each queried block, it quickly becomes the bottleneck.
05-02-2015, 02:12 AM
Oh, ok. You're referring to the name of the commit only, correct?
Is the PR much better performance wise?
05-02-2015, 02:48 AM
I have no idea; I'd expect so, but unless someone actually measures the performance, there's no way to know.
|
|
« Next Oldest | Next Newest »
|
