Missing textures on Millenia's weapons

[Alwitus]

So I recently got back into Fallout New Vegas and I wanted to install some mods into the game I started with Asurah's reanimation pack and it worked perfectly, so I installed several more until I was forced to stop when textures for Millenia's supported weapons (The ones that asurah supports) I don't know if it's my mod order or maybe I installed them incorrectly.

Also, for some reason I cannot get Project Solid to work, I tried installing it via NMM but i doesn't work.

Here is my mod order:

FalloutNV.esm

DeadMoney.esm

HonestHearts.esm

OldWorldBlues.esm

Lonesomeroad.esm

TribalPack.esm

MercenaryPack.esm

ClassicPack.esm

CaravanPack.esm

Gunrunnersarsenal.esm

The Mod Configuration Menu.esp

All Weapon Sounds Overhaul.esp

DYNAVISION 3.esp

AK74.esp

CM4A1.esp

DEagle.esp

M37Ithaca.esp

B92FS.esp

Asurah_ranimation.esp

P.S.

I forgot to install DLC support for asurah, maybe that's causing it? Also I installed Millenia's weapons BEFORE installing asurah's support for these weapons.

Edited August 2, 2018 by Alwitus

[dubiousintent]

I think you will find the wiki "FNV General Mod Use Advice" article answers the majority of your issues. You are missing some "essentials".

 

As for "Solid Project", suggest you re-examine it's requirements and check it's comments tab.

 

If you still need assistance, Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

-Dubious-

[Alwitus]

I think you will find the wiki "FNV General Mod Use Advice" article answers the majority of your issues. You are missing some "essentials".

 

As for "Solid Project", suggest you re-examine it's requirements and check it's comments tab.

 

If you still need assistance, Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as NVSE and it's related plugins, texture replacements (specifically their larger image sizes: 1024x1024, etc.), and "post-processors" like ENB or SweetFX.

 

-Dubious-

Well, I decided to get rid of Dynavision 3 to see if that caused the problem and when I loaded my game the textures for these weapons were still missing. Also, does Asurah have any incompatabilities with other mods such as Dust? I'm noticing that a lot of new armors are missing and face textures appear as purple.

 

P.S.

I got rid of the weapon mods as well to see if they were the cause of these purple textures but it doesn't seem that way

 

Specs:

CPU: AMD Phenom X4 955 BE (3.2 GHz)

GPU: GTX 1050 2GB

RAM: 8GB

OS: Windows 10

 

 

Edited August 4, 2018 by Alwitus

[dubiousintent]

"Solid color" textures (usually purple) indicate the texture file pointed to by the mesh is not being found.

 

Because "Texture/Mesh" replacement mods replace vanilla versions of those files, you absolutely have to toggle "ArchiveInvalidation" off-and-then-on again after installing or removing one of them so it recognizes that there are loose files (added by the mod) which have to be used in place of the vanilla files in the BSA files or are no longer there and the BSA files should be used instead. That failure to toggle is the most common reason behind most "not working problems". This is usually evidenced by red "!" icon for missing meshes, and solid colors for missing textures. Please see the 'ArchiveInvalidation (by Manager)' section and also see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

The only other reasons for mods to have these "missing element" error indications are that you failed to install all the necessary files (such as an ESM or BSA file), or they aren't in the correct location.

In the case of (for example) "Weapon Retexture Project" (WRP), the package has a "non-standard" folder structure. (Not an uncommon mistake by mod authors, so learn from this.) The game (to include most mod managers like NMM, MO, and FOMM) is expecting the top level folder of an archive package to be standardized, folder names such as "Textures" or "Meshes", or ESM/ESP/BSA files. It assumes they are being placed under the game "Data" folder. This example package starts with a "RLS" folder, which the game does not recognize, and so it places that as the "top level" under "Data". (Sometimes this is the author's name or initials, other times it's the mod name and version, but anything unexpected is treated the same way: as a new folder or file.) Most likely when the files are "installed" but aren't found correctly, something similar to this is your problem. Unpack the mod archive (WRP in this instance) to some other location and then either rebuild the archive so the top level folders are "Textures" and "Meshes" (in other words, without the "RLS" folder from WRP at all), and then install with your mod manager, or manually drag those two folders into the game "Data" folder.

The text file under the WRP "RLS" folder is a documentation file. If you want to keep similar in the package, just place it in the top level along with the "Meshes" and "Textures" folders. Personally, I rename such to "<mod_name>_ReadMe.txt" so I know which package they came from. (Many author's act as if their mod's text file is the only one that might possibly exist in the same location or use the same common name (i.e. "Readme.txt").)

-Dubious-