Jump to content
  • 0
Sign in to follow this  
Deathwing514

Deus Mon Wrye Bash Error Help

Question

Hey everyone,

 

I am currently having a problem installing this incredible mod.

 

Every time I activate the mod from the installer, I keep getting this error:

 

"Warning:Corrupt/Unrecognized Files"

 

Unrecognized Versions

Deus Mons.esm

 

If anyone can help me out with this problem, I would be very grateful.

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0

do you mean that when you select the mod in the Mods Tab?

 

This likely means that there is a discrepancy with this mod's masters (inconsistent records between the plugins and this master or this master and Skyrim.esm)

Share this post


Link to post
Share on other sites
  • 0

Yeah header files for esm's changed in 1.5.26 so if you have an early version of bash and a new esm version they don't play well, vice versa is also true. So you will either need to update your bash or the author will need to update the mod depending on which is outdated.

 

Also remember that all esm's are hacks, bethesda does not support creating an esm with the creation kit, so it may be an actual error or omission in the file besides just the header change issue. Here is a very short summary of esm .

 

Wrye bash is very diligent about verifying file integrity :D

Share this post


Link to post
Share on other sites
  • 0

Thanks for the info frihyland,

 

Just wanted to Update my situation with people who had similar problems.

 

The mod is working perfectly fine, I went to Deus Mons and

everything seemed to be working as ordered. I guess the Wrye Bash error

can be ignored as it does not in any way mess up your mods or Deus Mons.

So everyone who had similar problems, install the mod and ignore the error.

 

PS:My wrye bash is already updated to the latest version of 296 SVN and Deus Mons seems to be updated to the latest 1.5.26 version also. So I am clueless why this error still appears, I am guessing this is one of the few bugs (or many) of the new version of wrye bash.

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.