Fallout 3 will not detect custom .dds textures, which load up and work fine in GECK.

[Plamenator]

So, to keep things as short as possible, I'm working on a custom interior cell.

 

I want to add a custom flag to it so I duplicated the usflag01 model into a new form, created a custom texture set, assigned it to the new flag and placed said flag into the interior cell. All works perfectly in GECK, as illustrated below. It also works in the render window, but I forgot to make a screenshot and have since deleted the flag (work files still available):

 

http://i.imgur.com/Uk5tP9Q.png

 

The problem is that whenever I load the game, the textures get replaced by something like this:

 

http://i.imgur.com/44WSHAW.png

 

Or more recently, the black scan line background of a terminal.

 

I have no idea why that happens. The custom textures are in the /data/<my_exact_esp_name>/textures/clutter/flags/ folder (exact naming. Could it be wrong?). I also tried putting them directly into the textures folder (/data/textures/), but to no effect. They're in the right place (I think), but the game doesn't seem to be able to find them and just replaces them with the next thing on the list of textures.

 

Just to humour myself, I copied the usflag01 diffuse and normal maps as they were, without editing, without any modification, just copied them, renamed them accordingly and put them in the same folder, just to see if the editing software I use is corrupting the files, but it isn't. Same files in two different places, the ones in the textures folder just won't load.

 

What could be the problem?

 

I've been into GECK modding a whole ONE DAY, and I've come up to my first unsolvable problem. That can't be good. :D

[uhmattbravo]

If you're using some form of archive invalidation, try disabling and reenabling it.if you're not using some form of archive invalidation, that's likely the problem and you should get some form of archive invalidation. I just use the one included with MO, so I don't know enough about standalone types to recommend one.

[Plamenator]

If you're using some form of archive invalidation, try disabling and reenabling it.if you're not using some form of archive invalidation, that's likely the problem and you should get some form of archive invalidation. I just use the one included with MO, so I don't know enough about standalone types to recommend one.

 

I'm afraid I'm not familiar with archive invalidation. I did see it mentioned and tried running it in FOMM, but it crashed the program repeatedly. I guess I'll focus my web crawling on that term though. Thanks.

 

EDIT: The problem has been resolved. My game simply wasn't patched. 1.7 solved the problem. Although it could also be the automatic archive invalidation of MO. I should have done them one by one to see what helps. Anyways. Thanks for the info :)

Edited November 2, 2016 by Plamenator

[Plamenator]

Alright final clear up post. It turned out to be FOSE. Without it, Fallout would not recognise the textures, but with it, it worked flawlessly, as evidenced by this:

 

http://i.imgur.com/N9gSatr.png