No textures will load from any mod.

[Striderofxir]

So I got a bunch of mods after downloading new vegas on to my new computer and anything that has to do with visuals being changes results in error messages and icons. The functions work, but all I see anywhere is red exclamation marks where mods should be. I think it has something to do with file locations, but I have no clue what i'm doing, I'm positive it isn't a load order issue because I've seen the same thing even when mods are singled out and played.

[dubiousintent]

Did you install Steam to it's default location? If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" folder tree was bad (they learned better, and don't do that any more); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

"Texture packs" don't usually show up in the "load order". (They are replacing vanilla assets; thus they overwrite existing files.) And the issue with them is what size/resolution of the images you are using. Larger/"hi-rez" textures require more pixels, and larger screen display monitors multiply that requirement in a non-linear way. While your hardware may technically be able to handle it, the game is 7 years old, designed for Windows Vista with maximum screen displays of 1920x1080, with default image sizes of 512x512 pixels. The game engine texture cache tends to be the bottleneck.

"Texture/Mesh" replacement mods replace vanilla versions of those files. You absolutely have to toggle "ArchiveInvalidation" off-and-then-on again after installing 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. That failure to toggle is the most common reason behind such "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 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 mod managers like NMM and FOMM) is expecting the top level folder of an archive package to be expected, recognized folder names such as "Textures" or "Meshes", or ESM/ESP/BSA files. It assumes they are being placed under the game "Data" folder. This 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") after installation.)

-Dubious-

[Striderofxir]

Thank you so much for such an in depth answer that no one else could give close to. But just after a full deletion of everything new vegas and a reinstall I got the mods meshes loading right, I hope your post is saved for anyone else who would ever run into a texture or mesh loading problem.