Can I ignore these errors during the merging?

[bt4]

Hello,

 

I have merged Immersive Citizens - AI Overhaul with the patches but i get more than 3 errors.

https://pastebin.com/eQdXjYeu

 

[Kelmych]

It's safer to use the mod as is and only merge the patches; I rarely merge a mod and its patches. The mod and its patches often have conflicts.

[Neovalen]

 

 

The mod and its patches often have conflicts.

Isn't that the point? :)

[hishutup]

The issue is the NAVM which is compiled in the CK.

What are the side effects of not worrying about it? I dont know, maybe delete the info map from another mod and observe.

[Neovalen]

The issue is the NAVM which is compiled in the CK.

What are the side effects of not worrying about it? I dont know, maybe delete the info map from another mod and observe.

One would assume that the author of said patches intended the navmesh in the patch to overwrite the one in the main file. I also imagine that is how the final merge ends up without further action (it did in TES5Edit version of the merge script anyway - non standalone).

[Astakos]

Well, from what I have seen it is not exactly this way Neo. The NAVI record of each esp (patch or mod) corresponds to the navmesh mapping of the individual esp and this alone.

So, effectively, when merging various plugins containing navmesh records (which means there will always be a NAVI record), either the patched themselves or the patches with the main mod, the last plugin's NAVI mapping will take effect in the entire merge. This is not right as there are other navmesh records in that merged esp that are not mapped into the NAVI record.

 

Therefore the only solution to this problem (and to also have your peace of mind) is to delete the NAVI record from the merged esp and then open it up in CK and save it. CK will (re)generate this NAVI record taking into account all the added navmesh records and map them properly into the newly created NAVI record. Although it is not a difficult process, things might get a bit tedious if the merged patch has masters that are not ESMs.

Then these plugins need to be esmified in WB, re-dated in LOOT and then Ck will open them up in the right order in order to have the NAVI record generated correctly.

 

I have run into in-game problems in the past when I was not following this procedure. Ever since this is a MUST from me. 

Kudos for this process, reasons behind it etc goes to missjennabee (author of ETaC) who had explained it me very back in time.

 

Hope this helps a bit! 

[bt4]

Thank you for the answers.

 

I will try it with the CK. But I think i will have more questions, Astakos

[Neovalen]

I have removed this merge from the guide. A few more esps, but a lot less hassle. :)

[hazelwolf]

Neovalen, on 12 Nov 2015 - 09:04 AM, said:

I have removed this merge from the guide. A few more esps, but a lot less hassle. :)

Can we at least shave 2 of those plugins off by merging the patches?

[Darth_mathias]

Can we at least shave 2 of those plugins off by merging the patches?

i just tried merging the patches only and still get errors so proberly best not to i've dropped the merge now

[Pretendeavor]

They all have the NAVI record. The resulting merged plugin would instead of having those records merged contain only the NAVI record of the last selected plugin to merge. That means any combination of merge would need to have its NAVI record deleted in TES5Edit and then have it be rebuilt by opening and saving the plugin in the CK, like Astakos mentioned. If the merged plugin retains the masters from the individual patch files (the RRR, CRF and PCS plugins), those masters will need to be esmified (in Wrye Bash) to make sure the CK can load them as masters. After rebuilding the NAVI record and closing the CK you'd need to espify them again.

 

This is all assuming it works similar to the process of merging ETaC patches that contain the NAVI record.