Jump to content
  • 0
Sign in to follow this  
bt4

Can I ignore these errors during the merging?

Question

10 answers to this question

Recommended Posts

  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites
  • 0

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).

Share this post


Link to post
Share on other sites
  • 0

Thank you for the answers.

 

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

Share this post


Link to post
Share on other sites
  • 0
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?

Share this post


Link to post
Share on other sites
  • 0

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

Share this post


Link to post
Share on other sites
  • 0

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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.