http://i27.photobucket.com/albums/c171/RobLocksley/ScreenShot10.jpg

Now what causes this, I have forgotten?
I can give a hint - it has to do with the .esm files.
But what the problem was - I can't remember...

Have fun :hehe:

Didn't someone just post about this, or was that another forum...nope. Check for esmified ESPs, or ESPs that were converted to ESMs but need to be changed back. The former will be blue in Bash and the latter will appear black.

Thanks for answering.
Well, it does not show as neither black or blue.
I tried cleaning the esm. But that does not help me understand why, besides it didn't help

I know I know something about why it happens but so far my searches has gone bad, I am not sure I am searching for the right words. It is a fairly common problem with working with esm. Sometimes it is load order dependent some times world children, I just don't know enough about these things to pin it down. And I rather know then just fix it, since I am working with esm myself and don't want to fall into that trap, what ever it is!

Cheers!

I would not clean the ESM. That problem sometimes occurs when users forget to revert their esmified ESPs or converted-to-masters ESPs.

Please, post your load order: http://tesivpositive.animolious.com/index.php?page=know_how_to#PostYourLoadOrder

Which plugins does BOSS not recognize?

Stuff like that can happen if Oblivion.esm is not loaded first.

Why is this? I tryed to esmify a mod earlier and ended up with loads of missing ground. Is there a workaround?

All you have to do is use the Espify command to revert it back to its original state.

Yeah, I returned the original when that didn't solve anything.

Even if it would work after moving the esm in the load order (which I did to get more info if it was load-order dependent, then I could search for a fix there), it is not to get it to work that is most important but why. What is it that makes an esm behave badly in this manner? I just know there is a thing one shouldn't do when building esm because it can lead to just these things - and I can't remember!

I haven't bug hunted any more on this, but if someone knows the answer of have some ideas about issues around building esm and there troubles please post.

Cheers!

So there's no way to resolve the error without making it an esp again (sorry to thread-jack).

Yes. The file is "supposed" to be an ESP. You can use TES4Gecko to convert it back to an ESP if you actually converted it to an ESM, as opposed to using the esmify function.


Edit: If the problem is that you need to then make some other plugins dependent on the reverted ESP, you can quickly do that with TES4Edit or TES4Gecko or, even simpler, Bash. In Bash, just right-click on the ".esm" version in the plugin's masters list, and point it to the reverted plugin.