Textures replacer not working ?

[Blooshe]

Hello,

I'm trying to install this mod : https://www.nexusmods.com/newvegas/mods/62989 , but I can't make it work I don't know why.

When I'm using a mod with an esp file it works fine but if there are only texture files it seems like it's not even recognized, it just load vanilla texture everytime.

Can anyone help ?

[M48A5]

How are you trying to install the mod? What mod manager are you using?

 

After you installed the mod, did you toggle Archive Invalidation in your mod manager?

 

Do you understand that this mod only changes some effects, not all the graphics?

[Blooshe]

How are you trying to install the mod? What mod manager are you using?

 

After you installed the mod, did you toggle Archive Invalidation in your mod manager?

I'm using Fallout Mod Manager, I'm trying to install it by going into "Package manager" > "add FOmod" > selecting the .rar file from the download link > "Activate".

 

Archive invalidation was already on, after uninstalling then installing the mod I tried to put archive invalidation off then on again but nothing changed.

 

 

 

 

Do you understand that this mod only changes some effects, not all the graphics?

Yes I do.

Edited February 6, 2021 by Blooshe

[M48A5]

FOMM is a very good tool to add FoMods. It does not install mods that do not have an installation script or an .esp.

 

You should manually install the mod by dragging and dropping the mod texture folder into the game data folder.

 

Toggle (turn off/turn on) Archive invalidation after you install the files.

[Blooshe]

I tried putting it manually then toggle archive invalidation but still doesn't work. I'm really confused :confused:

[M48A5]

If your game is installed in "Program Files", you will not be able to make the change. The Program Files folder is controlled by Windows User Account Control which prevents any changes to be made to any file that is in the Program Files folder. The only solution is to move the game to another location on your hard drive. There are instructions on Steam on how to do this.

[Blooshe]

It is already in "E:\SteamLibrary\steamapps\common\Fallout New Vegas", is this location right ?

[dubiousintent]

That location should be fine, as long as you have set the "permissions" on the folder tree correctly.

 

" If you did move Steam out of the default location, then likely any access privilege problem is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then (while logged in as an "Administrator Account") need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders."

 

The usual reasons why a texture is not found or ends up displaying as a solid color such as black (other than failing to toggle AI) are:

1. It was packaged in such a way in the archive that when it was unpacked into the "Data" folder it got placed where the engine isn't looking for it. You can manually drag the folders to the correct locations, or repackage the archive to avoid that problem against the next time you need to install it.

In the case of (for example) "Weapon Retexture Project" (WRP) v1.95, 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; with folder names such as "Textures" or "Meshes" (etc.), 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. Sometimes it's "Data" so you end up with "Data\Data" which is also unexpected.) 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 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. Recommend renaming such to "<mod_name>_ReadMe.txt" so you know which package they came from, and place them all in a "Docs" folder for easy access, but it's not a requirement. (Many authors 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"), so consequently only the last installed exists.)

2. The texture path embedded in the NIF mesh file is not valid as your game is not installed in the same path as the mod creator. This is the fault of the mod creator, but something you can fix yourself. Please see the wiki article "How to fix hard-coded texture paths in NIF files" for the procedure to locate the texture file entry within NifSkope. (The path needs to be "relative" instead of "absolute"/"hard-coded" in order to be found on various installation locations, which is what that article covers.)

3. The "garments" (clothing and armor, etc,) are not using the same "UV Map" (AKA "texture coordinates") as the body replacement. If the texture coordinates are not compatible with the underlying "body type", the UV Map can throw off the engine. Your problem might be due to an update to the body replacer rendering it incompatible with the "garment" from the mod used.

For further, please see the 'Solutions to Graphics problems' and 'Solutions to Mesh (Red "!" icon) or Texture (solid color) problems' sections of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

-Dubious-