Texture mods not showing up no matter what I do

[MissFlapper]

I have a bunch of texture packs installed. NONE are showing up. It's all vanilla textures. I tried installing using a mod manager, installing manually, turning off/on archive invalidation MULTIPLE TIMES. Nothing worked at all. Any help would be appreciated.

[dubiousintent]

When you say "texture packs", do you mean VWD/LOD textures, or those for clothing, armor, or weapons? If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen; or xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first.

Otherwise we REALLY need to see a "load order" as produced by "LOOT"; to include the main game and DLC files. With modded games its the sequence, not merely the list of mods, which is the cause of many problems. LOOT's sort gives a good first approximation, correcting the most obvious issues and is sufficient for most players. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata". Instructions on how to copy it's list for posting are in the "How to ask for help" article, and "Checklist Item #11' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

-Dubious-

[MissFlapper]

When you say "texture packs", do you mean VWD/LOD textures, or those for clothing, armor, or weapons? If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen; or xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL. Also recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article first.

 

Otherwise we REALLY need to see a "load order" as produced by "LOOT"; to include the main game and DLC files. With modded games its the sequence, not merely the list of mods, which is the cause of many problems. LOOT's sort gives a good first approximation, correcting the most obvious issues and is sufficient for most players. You can make minor adjustments to the order and tell LOOT how to remember them. It's in the on-line documentation under "Metadata". Instructions on how to copy it's list for posting are in the "How to ask for help" article, and "Checklist Item #11' entry in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

 

-Dubious-

I should have been more clear. The weapon textures are showing up, but nothing like workbenches, roads, radios, or toasters. I only saw 2 textures from ojo bueno that worked. I am using NMC's, Ojo Bueno, and some smaller packs. Even the textures that I made won't appear. I don't get why it's not working this install. Last install, i did everything the same, and it worked fine. (I had to uninstall because of storage space). I keep a copy of all of my mods in a folder on my desktop so I'm using the exact same mods as last time, except a handful of textures.

 

My specs are:

CPU: Intel Core i5 4690K

CPU Speed: @ 3.50GHz

Graphics Card: NVIDIA GeForce GTX 970 (ASUStek Computer Inc)

Graphics Card Video RAM: 4095MB

Screen Resolution: 1920x1080

System RAM: 8.00GB

Free Hard Drive Space: 68.4 GB

It's not a laptop

 

Some stuff is overclocked, but my brother did that and I don't know how to check the overclock speeds.

 

OS: Windows 10 Pro 64-bit

Folder Path: C:\Program Files (x86)\Steam\steamapps\common\fallout new vegas

I don't run as administrator

Game Version: Latest (Idk how to check the number)

DLC: All

Mod manager: NMM and FOMM (I never had any problems with nexus mod manager and I don't like Vortex's or Mod Organizer's interface

I do have GECK installed and it's the latest version

Helper Programs and Script Extenders: LOOT, NVSE, FNV 4GB, YUP, Mod Configuration Menu, OneTweak, New Vegas Tick Fix

ENB: Yes

The game works, but the textures don't show up.

Steam hasn't verified files

I have "hide known file extensions" disabled

 

Load Order:

0 0 FalloutNV.esm

1 1 DeadMoney.esm

2 2 HonestHearts.esm

3 3 OldWorldBlues.esm

4 4 LonesomeRoad.esm

5 5 GunRunnersArsenal.esm

6 6 ClassicPack.esm

7 7 MercenaryPack.esm

8 8 TribalPack.esm

9 9 CaravanPack.esm

10 a YUP - Base Game + All DLC.esm

11 b Th3OverseerCore.esm

12 c Interior Lighting Overhaul - Core.esm

13 d New Vegas Redesigned 3.esm

14 e Functional Post Game Ending.esm

15 f NVInteriors_Core.esm

16 10 NVInteriors_ComboEdition.esm

17 11 Momod.esm

18 12 SolidProject.esm

19 13 Interior Lighting Overhaul - L38PS.esm

FCOMaster.esm

20 14 Gomorrah Redesigned v2.esp

21 15 World Of Secrets.esm

22 16 NVWillow.esp

23 17 Weapons of the Wasteland.esm

24 18 Bitter Springs Redesigned.esp

25 19 Project Nevada - Core.esm

26 1a Project Nevada - Equipment.esm

27 1b Project Nevada - Cyberware.esp

28 1c NevadaSkies.esm

29 1d Weapons.of.the.New.Millenia.esm

30 1e YUP - NPC Fixes (Base Game + All DLC).esp

31 1f Project Nevada - Honest Hearts.esp

32 20 Project Nevada - Old World Blues.esp

33 21 Project Nevada - Dead Money.esp

34 22 Project Nevada - Gun Runners' Arsenal.esp

35 23 CASM.esp

36 24 The Mod Configuration Menu.esp

37 25 Simple DLC Delay.esp

38 26 New Vegas Redesigned 3.esp

39 27 MojaveExtended100.esp

40 28 MojaveExtended40.esp

41 29 MojaveExtended60.esp

42 2a MojaveExtended20.esp

43 2b MojaveExtended80.esp

44 2c UnderwaterFX.esp

45 2d RocketSouvenirNoLongerAQuestItem.esp

46 2e PerkEveryLevel.esp

47 2f The Weapon Mod Menu.esp

48 30 Max Level 100.esp

49 31 NevadaSkies - Brighter Nights.esp

50 32 NVInteriors Addon.esp

51 33 TLD_Travelers.esp

52 34 EVE FNV - ALL DLC.esp

53 35 RWD-NV v1.3 [Alternative Version].esp

54 36 Project Nevada - EVE All DLC.esp

55 37 A Wasteland in Bloom.esp

56 38 All Weapon Sounds Overhaul .esp

57 39 IMPACT.esp

58 3a Project Nevada - IMPACT.esp

59 3b ArizonaArmy.esp

60 3c Explosive Sounds Overhaul.esp

61 3d Better Burned Man.esp

62 3e TrooperOverhaul-Dragbody.esp

63 3f CoyotePuppy.esp

64 40 Weapon Retexture Project.esp

65 41 Weapons.of.the.New.Millenia.Leveled.Lists.esp

66 42 Weapons.of.the.New.Millenia.Honest.Hearts.Grunt.Patch.esp

67 43 GRA-WRP-Patch-Two_Unofficial.esp

68 44 dD - Enhanced Blood Main NV.esp

69 45 Boacombat2glove.esp

70 46 Snowglobes Redone - DLC.esp

71 47 ILO - PipBoy Light.esp

72 48 ILO - NVWillow.esp

73 49 ILO - Nevada Skies Patch.esp

74 4a ILO - YUP Patch.esp

75 4b Mojave Nights.esp

76 4c ADAM Complete.esp

77 4d ADAM - MAIN.esp

78 4e Project Nevada - Lonesome Road.esp

79 4f ADAM - Nemesis Armor Pack.esp

80 50 NCRTrooperOverhaul.esp

81 51 GasPumpsOfNV.esp

82 52 boa ncrpahelmet.esp

83 53 ADAM - Rangers on Patrol.esp

84 54 Vanilla Intro Plus.esp

85 55 Crashed Vertibird Interior.esp

86 56 Weapons.of.the.New.Millenia.Store.LITE.esp

87 57 Advanced Power Armor.esp

88 58 UHNV.esp

89 59 UHNV-Honest Hearts.esp

90 5a UHNV-Gun Runners Arsenal.esp

91 5b UHNV-Dead Money.esp

92 5c UHNV-OWB.esp

93 5d UHNV-More Mannequins.esp

94 5e UHNV-Brighter Lighting.esp

95 5f UHNV-Lonesome Road.esp

96 60 UHNV - WRP Weapons Patch.esp

97 61 ADAM - Outcast Ranger Armor.esp

98 62 Interior Lighting Overhaul - Ultimate Edition.esp

99 63 ILO - GS Shack.esp

100 64 ILO - NVInteriors Project.esp

101 65 NevadaSkies - Ultimate DLC Edition.esp

102 66 NukaCola-Ojo.esp

(FCO is disabled because the tutorial I followed for New Vegas Redesigned 3 says to disable it)

[MissFlapper]

I just tried validating files through Steam and had no luck. I don't get why a couple of texture mods are giving me so much trouble. I'm using the exact same mods as last install, and am installing them the same way. Last install i had no issues at all. Now its a problem.

Edited July 19, 2019 by DogTheLog

[dubiousintent]

The primary thing I see that may be different from previously, is that you installed into the "C:\Program Files(x86)" folder tree. 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" or "C:\Program Files(x86)" 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. System updates often cause issues with games installed to these folder trees. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

Disabling "User Account Control" (UAC) only stops Windows from prompting you to grant "administrative" credentials to an application that the system says must have a "UAC elevation". Disabling UAC does not automatically then enable the permission for such applications. Instead, (for all intents and purposes) it automatically denies them. (Please read this MS article on how it works in Win10. The basics have been there since the inception of UAC with Vista.)

* Move any "inactive/disabled" plugins out of the game "Data" folder. They count against the "plugin cap" because they get loaded by the game engine if found, and can cause "Missing Master" problems. Please see the wiki "Missing Masters" article if you get that error message. If those plugins without the "mod index" numbers are "deactivated by the "Bash Patch", then you failed to have them "ghosted" by "Wrye Bash/Flash" when you built your "Bashed Patch". Please see the wiki "Bashed Patch file with Marked Mergeables" article.

* You really need to use a "Merge Patch File" with that collection of mods. Please see the 'Third Rule: The Rule of One' and 'Merge Patch File' sections of the wiki "FNV General Mod Use Advice" article.

Don't forget to toggle "ArchiveInvalidation" every time you make a change to your "load order" mix of plugins. That includes after "verifying local files".

 

-Dubious-

[MissFlapper]

I don't think it's a problem with it being in that path because thats where it has always been every install. Also I did a complete reinstall and the only mods I put on this time are the basic stability and patch mods and a texture mod. I did archive invalidation and it's still all vanilla textures.

[dubiousintent]

Every Windows system update has been tightening up the security of the "protected files". Just because something located there worked previously doesn't mean it will continue to do so in the future. That is exactly what happened when MS introduced UAC in the first place. It broke literally decades of "but that's how MS told us to do it" without any retroactive fix except by strict adherence to using it's APIs. (Many games didn't for performance reasons.)

 

Once you have installed a program into a system protected folder, any and all "changes" (such as INI file edits) get stored in a "shadow file" located in the "Users" folder tree. Older games developed prior to UAC have no idea about this and can get confused if they attempt to use any "shortcut methods" outside of the Windows APIs. This is described in the "Installing Games on Windows Vista+" article. (I don't know that FNV did this, but it's likely for competitive reasons.)

 

From what you are saying, I don't see any other reason for you to be having problems with that minimal "load order", except that whatever texture mod you are using is not being installed to the correct location.

 

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", 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 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").)

-Dubious-