-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Problem - MQ2Nav issue
- Thread starter EQman0311
- Start date
- Joined
- Mar 9, 2017
- RedCents
- 13,167¢
If it's during Pull and an indoor zone like Chardok or Howling Stones, that seems to be an ongoing issue. Per another post, KA is picking a mob by approximated pull path but not real-world pull path. MQ2Nav seems to think it can jump off the mesh (via a wall as if it was a cliff) and land back on the mesh near the mob it wants, thus a calculated short pull path.
Reloading or remaking your mesh alone won't fix it.
Some related posts:
I find changing my pull radius or pull z radius in your puller ini fixes quite a few. After that I look at the map for a camp that is as far away from the problem area as possible, while still letting me pull the mobs I want. Use MeshGen to manually block out the problem walls is probably the best fix, though I can't do that myself as MeshGen runs too slow on my system.
My laptop has a nice "feature" when the puller is having this issue. It starts audibly clicking as my puller slams his head on a wall then spins takes a step back and charges the wall again over and over. I think it actually raises the cpu temp too hah.
Reloading or remaking your mesh alone won't fix it.
Some related posts:
- Kaen01's 10 awesome step instructions for puller acting up.
- Pulling with MQ2Nav in dungeons, puller runs into walls
- A fix for off mesh issues with MQ2Nav (code snippet for puller being off mesh, diff issue)
- MeshGenerator.exe tutorial dropbox link for video. (comments about manually fixing wall areas)
I find changing my pull radius or pull z radius in your puller ini fixes quite a few. After that I look at the map for a camp that is as far away from the problem area as possible, while still letting me pull the mobs I want. Use MeshGen to manually block out the problem walls is probably the best fix, though I can't do that myself as MeshGen runs too slow on my system.
My laptop has a nice "feature" when the puller is having this issue. It starts audibly clicking as my puller slams his head on a wall then spins takes a step back and charges the wall again over and over. I think it actually raises the cpu temp too hah.
- Joined
- Dec 29, 2017
- RedCents
- 23,976¢
Usually this is caused by not verifying that the ${Navigation.PathExists[search info]}
Without that check, it'll try to get as close as it can, even though it can't make it all the way to the target.
Without that check, it'll try to get as close as it can, even though it can't make it all the way to the target.
- Joined
- Jun 12, 2015
- RedCents
- 58,244¢
if often related to a pathlenght bug in mq2nav, a fix is coming for it in kiss once maskoi redoes the pull sub.
but basically as eqtrader74 said, at some point the pullpathlength becomes long, and then mq2nav bugs out, and just creates the shortest path it can to your mob, and that is often through a wall or over a mountain it cant go.
the fix is basically checking the pathlenght against the distance of the mob, and if its smaller, since mq2nav only counts the bit after it warped past the wall or mountain, its a bugged path.
but basically as eqtrader74 said, at some point the pullpathlength becomes long, and then mq2nav bugs out, and just creates the shortest path it can to your mob, and that is often through a wall or over a mountain it cant go.
the fix is basically checking the pathlenght against the distance of the mob, and if its smaller, since mq2nav only counts the bit after it warped past the wall or mountain, its a bugged path.
- Joined
- Feb 9, 2017
- RedCents
- 1,377¢
MQ2NAV was working great a few months ago. Seem to have this issue now. Selects a mob goes a couple feet and says stopping navigation.