If you like this mod please consider endorsing it, It will help get this mod found in Nexus search results so that word is spread of it's existence.

If you want faster support/answers from me feel free to join the xNVSE Discord: https://discord.com/invite/EebN93s and look for my mod under the "forum" section.

Features:
Compatible with most mods that edit navmeshes.
Better pathing, seeks to eliminate NPCs walking into walls and other objects.
More competitive AI, more cover for NPCs to use and better navigation for melee attackers so they don't take long paths to get to you.
Fixes vanilla game navmesh errors.
Fixes sunken nodes which can lead to NPCs being stuck in the ground.
Fixes unfinalized cells and mismatched borders that prevent NPCs from navigating.
Optimized vanilla navmeshes for performance.


Compatibility:
This mod is compatible with most mods that contain navmeshes aside from mods that contain deleted navmeshes or navmeshes in ESP (Recommended to avoid those sorts of mods as they can cause crashing and game breaking glitches). For those who care enough to get maximum compatibility you may
want to use the patching guide below but it's no longer critical. DO NOT use "Navmesh Fixes and Improvements" or other mods that try to fix vanilla game navmeshes with this mod, they will be redundant with this mod as it supersedes them.


Making A Custom Patch:
The following guide will show you how to use this mod properly with most mods that alter the vanilla landscape and is meant to be easy to follow even for casual players: WARNING: It's important you read the mod list at the bottom of the page and set load order BEFORE the patch creation process (Load order tells the GECK how to generate the patch) you can rearrange your load order after you are done. Also disable Special K before following the guide.

Here is an easy to follow video tutorial for making navmesh patches: 




If you are having trouble following the video the written steps for making a patch are here:


TIP: Load order can be changed after the patch is generated (Mod load order matters for the GECK), for example YUP loads after my mod but might end up loading after some mod that conflicts with YUP that is supposed to load before my mod, in such case you can change the load order around after the patch is generated as long as the patch is loaded as low as possible in your load order.

TIP 2: To find out if mods you have need to be added to the patch creation process you can load all your mods in xEDIT right click and apply a filter and check "By record signature" and "Navigation Mesh". Also you can consult the lists down below for mods you may have in your load order.

WARNING: Load order must be set before the patch creation process, failing to do so may result in improper changes being applied.

WARNING 2: Ultimate Edition ESM Fixes MUST be disabled before creating a patch (For TTW use MO2 to hide all of the TTW ESMs that replace vanilla NV ESMs in the filetree tab), will cause in game crashes if a patch is generated with it enabled. (You can reenable the ESMs later after patching)

WARNING 3: The patch must be regenerated every time you update this mod to a new version and always from a clean ESM file. A clean file should also be used any time you need to regenerate the patch.

WARNING 4: Do not generate and use more than one patch at a time (This includes my pregenerated YUP patch and the VNV navmesh patch) , all mods that add load doors and navmeshes to vanilla worldspaces should be loaded at the same time in the GECK.

WARNING 5: If you are using mods that alter navmeshes that are an ESP that is NOT flagged as an ESM in xEDIT then it is highly recommended you uninstall and stop using said mods or contact the mod author and tell them to make the ESP an ESM. Mods that do this will cause severe pathfinding issues and game breaking glitches even when not using this mod.

WARNING 6: Don't load any ESPs in the GECK while generating patches (ESM flagged ESPs can be loaded).

WARNING 7: Disable Special K, ENB and other similar mods before launching the GECK or the GECK could crash.



The following lists will help you determine what mods in your load order need to be included in the patch creation process and what the load order should be in Mod Organizer with this mod. (use ctrl+f to easily search for a mod in this list) These lists are not complete but list some common mods:

List of mods you SHOULD NOT use with or without this mod:
This list is not meant to be an attack against these mod authors but these mods will cause game breaking bugs and need to be fixed before people can use them with this mod and shouldn't be installed even if you don't use this mod:

• New Vegas Uncut - Freeside Open - (Deleted navmeshes, use Simple Open Freeside instead)
• Legion Quests Expanded - (Navmeshes inside ESP)
• Lucky 38 Suite Reloaded v5 - (Navmeshes inside ESP)
• Pleasant Primm (Location Redesign) - (Deleted Navmeshes)
• Nefarious Nipton (Location Redesign) - (Deleted navmeshes) 
• Industrialized Sloan  - (Deleted navmeshes) 
• Mojave Vagabond - (Deleted navmeshes)
• Medical Clinic Expanded - (Navmeshes inside of an ESP with Deleted navmeshes)
• Interiors Improved - Hope Lies (3DNPCs) \\\\\\ Hope Lies - A FNV Companion - (Both have Navmeshes inside of an ESP)
• Strip Walls Restored - (Navmeshes inside of an ESP with deleted objects)
• Mojave Outpost Redesigned - (Navmeshes inside of an ESP with Deleted navmeshes)
• Zion Trail \\\\\\ Zion Trail Enhanced - (Navmeshes inside of an ESP)
• All quest mods by "someguy2000" - (Navmeshes in ESP, use New Vegas Killer LE and New Vegas Bounties I LE instead)
• Every landscape or new location mod made by the "th3overseer" including The North Road Remastered and Headhunting, (Technically compatible with my mod but the Nexus versions always have Navmeshes inside of an ESP and they have dirty edits and deleted vanilla game objects) Use the ModPub versions instead.
  

Example load order for mods:


Note for modders:
To ensure compatibility with this mod and almost ANY other mod that modifies navmeshes, be sure to leave vanilla exterior cell border nodes alone except in cases where you need to cut space for a new object you are adding.