zzz

Does the pathing for some reason prioritze walkable coordinates based on Z coordinate being relatively-extremely high or low compared to most of the path?

This path has only very slight detour (not really even a problem or something I would complain about), but it for some reason really wanted to go up that little mountain.

Most (if not all?) of the detouring paths I have seen have had one thing common: either relatively-extreme drop or increase in Z coordinates.

Droidz, could this be it? relatively-extreme change in Z coordinates compared to other waypoints on the wrobot generated paths?

I'll just throw these in here.

Ignore the mess, there just was a lot of mobs hotspotted in this quester, the random detour through the sea just shouldn't exist, no hotspots are there, yet it still wants to go there.

More detours that shouldn't exist

20 minutes ago, Droidz said:

Hello,

You have tried solution given for thousand? she works and resolve your problem (even if is it offmeshesconnections) (I'll add these offmeshesconnections by default to WRobot in next updates) , and I told for booty bay to wait than I add new offmeshesconnections feature to resolve this issu (I'll add by default to WRobot this offmeshsesconnections too).

And change maxclimbheight is not solution, this will probably resolve problem in thousand but will add a lot of bugs in others zones (I work on it since several years, I know what I said).

You never say hello, thank you, ..., I give you solutions that you do not even test, you talk badly about me, and you're there for only 1 month ... Tell me why if WRobot has so many problems, and I deserve so little respect because what I give you is so bad you have bought WRobot (there is the trial version for tested before purchase), and why do not you go to the competition?

I know than WRobot is not perfect, and I work on it every days, I appreciate people who help me to find bugs and than suggest solutions (if WRobot still here it's thanks to them), but stay polite, and when I give a tested solution before you complain.

I am sorry if I seem rude, that is not my intention. this pathing problem is just frustrating to everyone.

thank you for the thousand needles fix, that solves the specific issue. Good work!

But, it is non satisfactory solution in general related to this issue.

Or am I not understanding this offmesh thing? I understood that all these offmeshed are hand crafted, is this something automated? if it is manual thing, it is not a solution.

I'm hoping other people would pitch in on this issue, otherwise this will stagnate on me trying to convince you that the pathing is broken and that making offmeshes is not the solution.

Its great that you made that for the specific 1k needles case, but why is it not already part of the meshes, the clipheight is static number afterall and recast/detours supports this (maxclimbheight).

^ This could also work if you loaded the fence doodads in recast and applied the clipheight to those! But that would be just a nice-to-have-feature, the unstuck can handle fences right now just OK, so not saying more about that!

The creator of recast/detour has also helped other people fix the stupid detours that wrobot is facing:

https://groups.google.com/d/msg/recastnavigation/vDrxqlUl1B4/zIY72aHxXK8J (this looks exactly like some of the paths wrobot does, wrobot just takes much longer detours)

How can we help you make the paths actually not do stupid things Droidz? Is this a math problem? Triangle extraction problem? Please, we all just want the pathing to work, share the problem, we will help.

4 minutes ago, Droidz said:

Thank you, can you share positions (from/to) (or your log file of sessions where you get this problem)

It's all in this bugreport, but this is just one specific case, there are thousands of these problems all across the world.

I'll just post some screenshots, bot is ignoring Z coordinate completly.

Edit these are part of the problem, but these are what I can 100% replicate every time.

1 minute ago, Droidz said:

if you get bugs in 100% of the zones, try how I said to disable all wow addons and reinstall WRobot in new folder.

Please read my edit on the post, I improved my reply on there.

Quote

EDIT:

I am going to mention, this isn't installation problem / addon problem / plugin problem / profile problem / or because of angry kittens.

I am not the only one having these problems, everyone is.

Everyone agrees that the pathing is bad and it should be at least at the level where you can safely AFK from your bot. And not come it being stuck in some random place unable to generate path up stairs, navigate around a cliff, not take 3000 yard detour for 200 yard path, getting stuck in the only water puddle in a zone, whatever the case might be.

7 minutes ago, Droidz said:

We do not have the same vision of the word "BROKEN", pathfinder needs improvement, and it is not perfect, but it works in more than 90% of cases, avoid zones where it does not work correctly if you do not want to have strange behavior.
Tell me the name of bots with a better pathfinder than WRobot (all games)? Except HB I do not see it.
I repet, pathfinder is not perfect, I need to improve it and I'll do that.

I do understand that its not perfect - I'm not looking for perfect pathing, but 100% of the zones have bugs like this - every single zone -.

Can't you at least take look, spend day or two improving the pathing? Making offmeshing better does not help at all.

EDIT:

I am going to mention, this isn't installation problem / addon problem / plugin problem / profile problem / or because of angry kittens.

I am not the only one having these problems, everyone is.

Everyone agrees that the pathing is bad and it should be at least at the level where you can safely AFK from your bot. And not come it being stuck in some random place unable to generate path up stairs, navigate around a cliff, not take 3000 yard detour for 200 yard path, getting stuck in the only water puddle in a zone, whatever the case might be.

1 minute ago, Droidz said:

Add offmeshesconnection for successfull path will resolve your issue, problem in booty bay is that pathfinder don't know than he can use tunel to enter/exit (I forget why, but I cannot change that), but pathfinder found another path (by the water) current offmeshesconnection don't works, with next features, you add offmeshes connection to the tunel and WRobot will use it to enter/exit of booty bay.

Ofcourse this will not resolve all bugs

No, no - you don't understand!

We should not be responsible for fixing the paths. I have Profiles that will walk everywhere in the current world, why should I (or any other user for that matter, I am not speaking for only myself here) spend hundreds, or even thousands of hours on MANUALLY making meshes to the world?

The pathing is BROKEN do you not understand this?

Do you use your own product? It's generating these horrible paths everywhere very often, and its not right.

5 minutes ago, Droidz said:

Hello, in the ownedcore link its me. WRobot pathfinder is more advanced than your links. I'll add in few weeks new features at the offmeshesconnection to be used even if path return success result (this will resolve problem like you have in your first screenshot).

Yeah, I know.

Improving offmesh does not help this issue, the issue is the fucking horrible pathing that seems to be getting worse and worse constantly.

Just now, Droidz said:

When way is correct, you get stucks or strange path?

• "strange" (read this as: idiotic bottish) paths (see the first post)
•  static paths (mailbox -> auctioneer) changing (see the first post)
•  bot taking huge detours (see the first post)
•  

7 minutes ago, Droidz said:

Hello, in the ownedcore link its me. WRobot pathfinder is more advanced than your links. I'll add in few weeks new features at the offmeshesconnection to be used even if path return success result (this will resolve problem like you have in your first screenshot).

I know.

adding improvements to the offmesh does not help with the pathing being horrible and constantly degrading on quality.

I was told that I should give you links to fix things faster.

I was told that all this pathing poop is broken meshes, I'm leaning towards some wrong optimization on your end (as the paths have been better in the past). But people insisted that its just broken mesh generation, so here goes:

stock go-to guide for everyone who intends to work with meshing recast detour: https://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-bots-programs/wow-memory-editing/317944-path-generator-recast-detour-wowmapper-step.html

Unfinished project from a friend of mine to generate meshes, end goal was to generate meshes for sharpnav (c# recast/detour clone): https://github.com/miceiken/WoWMap

Older project to generate meshes, should be relatively easy to port for different expansions if you have original MPQ's (not the pserver modified ones) : https://github.com/stschake/meshReader

--

Need more help or resources? Give a shout on discord, we have people who will happily assist you to fix this pathing problem.

adding more details - bot seems to be unable to path to any of these three gears in this picture (quest is grimtotem spying)

specific coordinates ( try to navigate these from anywhere outside of these three big rocks/mountains, the problem will occur)

          <Vector3 X="-4922.240" Y="-1831.890" Z="80.820"/>
          <Vector3 X="-5139.710" Y="-1918.910" Z="89.188"/>
          <Vector3 X="-5184.790" Y="-2164.450" Z="94.634"/>