All custom textures broken and change depending on angle/distance

[QuentinVance]

Hello all!

So, just like the title says: I have several objects that I made new textures for (eg. different books, new terminals, etc.) and everything was fine last time that I worked on my mod. Then, after a long hiatus, I came back to find that all the custom textures in my mod have stopped working. I can see them just fine in Nifskope and the GECK (so I know there are no missing textures on the .nif, and the mipmaps are also fine), but when I start the game itself, all the custom textures break, reflecting the textures of whatever is on the other side of the object based on the player's current position.

 

I had the same problem a long time ago, but I remember fixing that by changing the texture path in Nifskope, from the main drive folder/steam folder path, to just textures\quentinvance\mod\texturename so that the the game automatically knows to search relative to Fallout 3's own folder. When I did this the first time, the new textures in Nifskope turned white (like they always do) and they worked in game.

Now they turn white, but then don't work in-game. I know for sure that the path is correct, so that can't be it.

What else could be causing this?

[Shabdez]

this might be too obvious, but did you toggle Archive Invalidation?

[QuentinVance]

this might be too obvious, but did you toggle Archive Invalidation?

 

This was actually a good question. I did not toggle that, nor did I even know I had to. They always worked without me doing anything like that. Where is that option?

[Shabdez]

You would either need this
https://www.nexusmods.com/fallout3/mods/944?tab=posts

 

Or depending on the Mod Manager you use, it might have a switch somewhere to toggle it on and off. I think FOMM has one, MO2 definatly does (part of the profile settings), not sure about Vortex.

[QuentinVance]

I honestly don't think this is going to have much impact on the issue. My mod always worked by just placing the files in the Meshes and Textures folder and the game never had a single issue, plus they work fine in the geck.

I will try it regardless and let you know, but I really don't think that's going to work.

 

EDIT: I tried it, nothing changed at all. It has to be something else.

Edited February 22, 2022 by QuentinVance

[QuentinVance]

UPDATE: I solved the issue.

I had originally tried with the file Shabdez had posted, to no avail. Today I had a little more time and I went through FOMM, activated Archive Validation from there, and it immediately worked. I'm a bit confused as to why it worked through FOMM but not the other method - usually it's always the most laborious way that solves the issue - but as long as it works I can't complain.