ESM files messing with textures?

[TheGhoulKisser]

Since I didn't find a thread concerning my problem, I've decided to start one.

 

Where should I start? I’ll try to star with the beginning… OK, so I’ve started modding my games since a couple of months. One thing I really like is to install textures. I’ve installed Tapiok’s textures and some other and they all looked fine in my games. However, I’ve installed some new mods and most of these textures reverted to vanilla or didn’t show up properly. Some of these mods are using ESM files and I assume that those files might be messing with the textures I’ve installed. I don’t know how, but once I deactivated some ESM files, the installed textures were back in my game.

 

So, if it’s really the case, is there a way that I can fix that? By the way, I’ve been using ArchiveInvalidationInvalidated to get my textures to work and I’m sure that I’ve installed it according to the given instructions. If the textures worked *before* I’ve installed certain ESM files, I don’t know why they stopped showing up after.

 

Please help me, fellow modders. You are my only hope.

 

Otherwise, what else could have messed with my textures? :wallbash:

[davidlallen]

It is possible your texture mod changes one texture, and then some other mod you install changes the *same* texture. This is called a mod conflict. Sometimes, you can fix this by changing your load order to put the texture mod last. Use FOMM to change your load order if you haven't done this before.

 

Here's how you can find and resolve a simple mod conflict, where turning off the other mod makes the problem go away. Find one specific texture you like where you have noticed this behavior. Turn off all the mods except the texture mod where it comes from; make sure you see the texture in game. Now turn on a few mods at a time until the texture you like disappears. One of these mods is causing the conflict. Once you find which exact mod is causing the conflict, you can post on the mod thread for that mod to ask, or if there is no reply, PM the author.

 

Of course there are tools you can use to track down the conflict yourself; probably you would need geck and fnvedit. Apply a filter in fnvedit to see what is changed in the conflicting mod, and then use geck to remove it.

[TheGhoulKisser]

After checking out my ESM files, I came to the conclusion that it wasn't those that were messing with my textures... By the way, I installed the textures via a FOMOD file...

 

[ EDIT ] It's alright. I've figured out what my problem was. It also fixed the mixed skintones problem that I had with some NPCs. Apparently, if you add the ArchiveInvalidationInvalidated!.bsa to the SArchiveList list in Fallout_Default INI files, you must do it as well in Fallout.ini and FalloutPrefs.ini in My Games/FalloutNV. I did that and all the marvelous textures that I've installed were finally showing up. Thanks to ViralDust, who was kind enough to post that tip in the ArchiveInvalidationInvalidated forum thread. I can stop bashing my head against the wall now.

Edited July 10, 2011 by TheGhoulKisser