I am just starting to merge in navmesh records with version control, but I've run into an odd problem I want to see if there is a solution to. I've followed http://www.darkcreations.org/forums/topic/1870-ck-version-control-discussion/?p=162900tutorial on checking out Skyrim's NAVI record and checking it in with the navmesh records of a plugin to our master file. However, the plugin, in addition to having the navmesh record for the location it contains, seems to contain references to every single interior navmesh in Skyrim. This is an issue, as it will cause conflicts with anything else that touches vanilla navmeshes (right?). I tried cleaning out the cell references, but it seems that just by having the NAVI record referenced, the Creation Kit still thinks I need to check out literally everything listed under it.

Do you think it is possible to check out the NAVI record to get it into our .esm, change the formid of it in TES5Edit, strip out the references to vanilla cells, and turn it into a NAVI record unique to our .esm to prevent any potential conflict? It seems like Bethesda did something similar for Dragonborn.

If I did something like that, how would the Creation Kit know to reference our NAVI record for new navmeshes rather than Skyrim's? Has anyone created a navmesh record dependent on the NAVI entry for Dragonborn? I know that .esms NAVI record has a different formid than Skyrim's.

Last year I was working as part of a team and we were also experiencing difficulties merging navmesh into an esm with version control. We decided that the best bet was to release as an esm+esp pair, with the esp containing all the navmesh (plus any last minute edits).

- Hypno

Hmm. Well, I'm really hoping that Bethesda fixed the issue with Dragonborn. Dragonborn has a unique NAVI record unlike previous Bethesda DLC. I'm pretty sure that both Hearthfire and Dawnguard utilize the vanilla Skyrim NAVI record, but I know that the engine can handle multiples. Not sure on the upper limit, though.