• You've discovered RedGuides 📕 an EverQuest multi-boxing community 🛡️🧙🗡️. We want you to play several EQ characters at once, come join us and say hello! 👋
  • IS THIS SITE UGLY? Change the look. To dismiss this notice, click the X --->

Plugin - MQ2Nav Beta [Deleted] (1 Viewer)

Status
Not open for further replies.
You can also visit the release page on github: https://github.com/brainiac/MQ2Nav/releases/tag/1.3.0.90

MQ2Nav 1.3.0 Beta

This is a major release of MQ2Nav

Highlights & New Features
New Off-Mesh Connections tool (#52, #65)
Using the new MeshGenerator connections tool, create short connections between two points on the mesh. The distance is limited to adjacent tiles. Connections can be one-way or bi-directional, and pathing costs are calculated.

Off-Mesh connections can be used to bridge gaps in the mesh when certain areas are obstructed, allowing MQ2Nav to follow a path that spans a segment that lacks navmesh. While following a path, connections are represented as a purple line segment.

Navigation Command Options (#49, #53, #63, #64, 1323b04)
Navigation commands can now be modified with options that modify the navigation behavior. For example, you can use the following command to get within 30 distance of the target: /nav target distance=30. The following options have been added:

  • distance=x Move to within the specified distance to the destination. Using this command will enforce a line-of-sight check to ensure that the destination is visible before ending. shortcut: dist
  • lineofsight=off Disables the line-of-sight check when using distance. shortcut: los.
  • log=level Sets log level during navigation. Use log=off to completely disable navigation logging while the command is active. Valid options: trace, debug, info, warning, error, fatal, off. The default is info. Specifying a level limits logging to the given level or higher.
  • paused Starts navigation in a paused state.
  • notrack Disables tracking of spawn movement. When navigating to a spawn (via any of the various methods), the destination will be updated to track the spawn's movement. If you prefer not to update the destination when the target moves, specify this option.
Navigate from MQ2Map (#15)
Use MQ2Map click feature to navigate to a specific location using the locxy navigation command.

Activate this feature by setting a MQ2Map click command: /mapclick left ctrl+shift /nav locxy %x %y and then ctrl+shift+leftclick anywhere on the map to go there.

Path Planning Improvements
Moving off of the navigation mesh will no longer cause the path to fail. Additionally, trying to navigate to unreachable destinations will no longer try to navigate with an incomplete path.

Enhancements
  • Areas marked as unwalkable can now be overwritten by walkable areas. This is useful for blocking out a large area as unwalkable, and then carving an area within it as walkable. Areas are applied in the order specified in the MeshGenerator, so specify your unwalkable areas first and your walkable area after. (#16)
  • Areas tool now supports reordering areas. (fab89ca)
  • Navigation is no longer affects by keyboard state. It is now safe to type while navigation is active! (#56)
  • Added command to list saved waypoints: /nav listwp (#40)
  • Added ${Nav} alias for ${Navigation} (#57)
  • Added two new default area types to assist mesh creators: Prefer and Avoid. These areas can be used in association with the areas or connections tools to mark areas of the map as preferred or avoided when creating paths. (57f4663)
  • Added log=off option to disable logging of navigation commands. (#49)
  • Added new, official plugin exports for other plugins to integrate against. Old, unofficial exports still exist, but will print a warning when using them for the first time. See this wiki page for more information: https://github.com/brainiac/MQ2Nav/wiki/MQ2Nav-Exported-Functions (#13)
  • Navigating to a spawn will now dynamically update the destination if the spawn moves. add the notrackoption to disable these updates. (#64)
  • Improved the display of instructions in the mesh generator. These helpful little hints are now rendered as an overlay with a grey background to make them more visible in the bottom right corner. If this gets in the way it can be disabled from the menu. (28c8994)
  • Settings used to generate a navmesh are now saved with the mesh. Opening the mesh again will bring back the original settings, allowing to make additional changes without causing problems. (#66)
  • Zone shortname can be passed to MeshGenerator.exe via command line. This will also load the navmesh if available. (64818bd)
  • MQ2Nav and MeshGenerator now use a logging system to provide consistent and uniform logging. In addition to logging to the screen, logs can also be found in MQ2Nav.log or MeshGenerator.log, even if logging is silenced in the UI. (#55)
  • Revamped main content area of MQ2Nav UI, giving priority to current navigation state.
  • Various other UI improvements made to MeshGenerator and MQ2Nav. Feedback is welcome!
Bug Fixes
  • Logging out should no longer confuse the current zone id. (#37)
  • ${Navigation.PathExists} should no longer return true if the destination is not reachable. (#48)
  • Fixed several crashes including ResetDevice, RenderHandler::InvalidateDeviceObjects, and a few others. (#36, #62 101789b, d849894)
  • Moving off of the mesh will no longer cause navigation to stop. (1323b04)
  • Trying to navigate to an unreachable destination (or one that exceeds the memory limit for length) will no longer product an incomplete path. Instead, it will fail. (#41)
  • Typing into text fields in the mesh generator will no longer also move the camera (6c6d04d)
  • Modifying the x or z coordinates of the bouding box should no longer cause problems with using the mesh. (#32)
  • Fixed path length assert failure
Packaging Notes
VolumeLines.fx is no longer needed to be bundled with the plugin. It can be excluded from redistributions moving forward. (#43)

Updated Dependencies
  • ImGui upgraded to 1.67, comes with various bug fixes and new color scheme. (#60)
  • SDL2 upgraded to 2.0.9

MQ2Nav 1.3.0 beta 2
This is a minor update to the 1.3.0 Beta release of MQ2Nav

Improvements
  • Added a way for /nav spawn to work with options. Separate the spawn search query from the nav options with a | pipe symbol. For example: /nav spawn npc banker |dist=30 (#68)
  • Waypoints names are now case insensitive when used for searching. (#70)
Bug Fixes
  • Fixed /nav spawn handling, the first search argument should no longer be ignored (1c2de7e)
  • Fixed keyboard input in overlay ui in MQ2Nav (#71)
  • Fixed log level not properly being set during macro data queries (#67)
  • Fixed a shutdown crash (a022f86)
  • Fixed a crash on plugin load (#69)
MQ2Nav 1.3.0 beta 3
This is a minor update to the 1.3.0 Beta release of MQ2Nav

Improvements
  • Added command to change option defaults (#58)
    • /nav setopt [options] will set option defaults that other navigation commands will use.
    • /nav setopt dist=30 will set the default distance to 30
    • /nav setopt log=off will turn logging off
    • Option defaults can be reset with /nav setopt reset
  • Added nav ui to show and modify default options.
  • Updated help text for other navigation options.
Bug Fixes
  • Fixed an issue that caused navigation path indicator to stop appearing after a number of paths. (#74)
 
Last edited:
There are no words that can describe how much I love this plugin, so I’ll just say Thanks for these updates, every single one is completely awesome. Building this today.
 
I'm apparently illiterate, but I'm able to CTD trying to follow the new nav directions. I plead ignorance of the appropriate syntax however, and that may be my issue here. I've not utilized nav as a direct command much at all.

I targeted a far away pc and typed /nav target distance=30 <-Exactly that way, word for word, and it gave me a CTD. Didn't send it to Mule, but thought I'd let you know.

The reason I did this is because I'm trying to figure out how to nav to a target, but almost every nav command I enter is giving me an "invalid nav destination"

I was trying to get the right syntax to nav to one of my alts with a stand-off, or to franklin teek for instance. I tried this:
/nav spawn npc franklin teek distance=30
/nav franklin teek distance=30
/nav 'franklin teek distance=30'
/nav "franklin teek distance=30"
/nav "franklin teek" distance=30

none of those worked, and several other versions I tried as well I think.

/nav spawn franklin teek does work
as does the same when naving to my alt as above, but not with a distance command at the end. As a matter of fact none of the "Navigation Options" are accepted if put at the end of the nav command. So, perhaps I'm using them wrongly? I cannot find other directions on the original or current discussion to show me an alternate method however.
 
omg, thank you for this update, I hope off mesh pathing works for the TBL and old zone crazy pathings.
 
toadwart said:
I'm apparently illiterate, but I'm able to CTD trying to follow the new nav directions. I plead ignorance of the appropriate syntax however, and that may be my issue here. I've not utilized nav as a direct command much at all.

I targeted a far away pc and typed /nav target distance=30 <-Exactly that way, word for word, and it gave me a CTD. Didn't send it to Mule, but thought I'd let you know.

The reason I did this is because I'm trying to figure out how to nav to a target, but almost every nav command I enter is giving me an "invalid nav destination"

I was trying to get the right syntax to nav to one of my alts with a stand-off, or to franklin teek for instance. I tried this:
/nav spawn npc franklin teek distance=30
/nav franklin teek distance=30
/nav 'franklin teek distance=30'
/nav "franklin teek distance=30"
/nav "franklin teek" distance=30

none of those worked, and several other versions I tried as well I think.

/nav spawn franklin teek does work
as does the same when naving to my alt as above, but not with a distance command at the end. As a matter of fact none of the "Navigation Options" are accepted if put at the end of the nav command. So, perhaps I'm using them wrongly? I cannot find other directions on the original or current discussion to show me an alternate method however.
Click to expand...

See the beta 2 update notes. Since "spawn" option takes a variable number of string parameters, you need to use | to separate, so /nav spawn franklin teek |distance=30

Also, there is a crash I'm chasing down with distance, so if you are CTD it is not just you.
 
See? Illiterate, I didn't read down to the beta 2 notes. Apparently, I just saw the first reference under the 1.3.0 notes. Sorry about that, and thank you.

My crash was related to the use of the word "target" in the string I thought, but if you're getting other distance crash problems then maybe not.
 
thanks for the quick fixes, tried beta 3, and crashed multiples times, tried to go back to feb 2018 built, and that cause many problems too. Settled on beta 2. Will try beta 5 soon!
 
Plugin - MQ2Nav Beta [Deleted]
Status
Not open for further replies.
Next unread thread 🦁

Users who are viewing this thread

Total: 2 (members: 0, guests: 2)
Back
Top