data files (textures meshes etc) seemingly non existent yet the game works

[xXScaryduckXx]

so when im in my data directory inside the fallout new vegas game files i cant seem to find a fair number of files that are apparently meant to be there, according to mods that require said files copied over to fallout 3 and some other retexturing mods.

 

this issue kinda ties into the issue im having where mods just aren't working despite me following installation instructions, which is mindblowing considering some mods work with same methods

 

thanks for reading, any help is always appreciated. im happy to answer any further questions if there's anything ya need knowing

[dubiousintent]

You don't say, but I am supposing you are using a "mod manager". Many of the newer ones (e.g. MO, MO2, Vortex) work from an "empty Data folder" concept, where they don't place the actual files there. Instead they place "pointers" (symbolic links), that fake the game into acting as if the files were physically present while remaining in their original "install" location (which is outside of the game itself). This way they can use "profiles" to easily change which files are used by different players or for different purposes. (It's not the only way it can be handled, but how they chose to do so for their own reasons.)

 

First, identify which "mod manager" you are using. Please see the 'Mod Managers' section of the wiki "FNV General Mod Use Advice" article for tutorials if you need help.

Then be sure you have selected a "profile" (assuming it uses one) so the manager knows which files you want in "Data". Then "<Alt+Tab>" out of the manager and use Windows "Explorer/File" to examine the actual game "Data" folder. However, that is only for "verification" purposes. Where the mod calls for you to "manually copy files" you need to use the manager's designed mechanism for "overwriting" files. That should be in the linked tutorials.

 

If you are using NMM, then be aware of the following:

 

As of 08 May 2018, the Nexus has changed some site security to come into compliance with the new "European Union General Data Protection Regulation" (EU GDPR) rules. This breaks older versions of NMM and other tools using the older unsecured API. It is usually reported as being "blocked by the Windows firewall" or causing a "script" or "W3C XML Schema" error installing mods. You will need to update it from NMM on GitHub. Check the version numbers between those sites and use the latest release. Please see this Nexus site news article for details.

As of 13 May 2019 all "workarounds" that depend upon continued use of the old API will no longer function. That API has been removed, as previously announced more than two years ago. This includes but is not limited to:
* Nexus Mod Manager v0.65.11 and lower
* Mod Organiser 2 v2.1 and lower
* Mod Organizer 1
This only affects their ability to login to and automate the download from the Nexus site.

Some people are finding that even after updating NMM to v0.65.4 they still get a "script exception" message when installing some mods (such as UIO and MCM). This seems to be resolved by this suggestion from user ElysianMod:
* Run NMM as an "Administrator privileges" account.
* Go to NMM "Settings".
* Enable "Add Shell Extensions for Supported File Types".
* Then restart NMM. (You should not need "Administrator privileges" this time.)
(Supposedly this fix is included in "unofficial" update v0.65.7 and later to NMM on GitHub.)

-Dubious-