Sierra Madre Glitch

[JonesenoJ]

https://imgur.com/a/rZNlcEs

You can see the file sizes and that they haven't been modified, except the .NAM

[AusAllerWelt]

Hmm, comparing it to my Dead Money.esm, your file seems to be smaller. I'm not accusing you of anything. I think that you could try and delete the .esm and verify your game files, provided you have the game on steam, I don't know how it works for the GOG or Bethesda.net versions.

Edited July 16, 2020 by AusAllerWelt

[dubiousintent]

I see this is a "notebook" computer with an "onboard" graphics chip. You have 4GB of system RAM, but the graphics card has to use that memory as well (having none of it's own), so you are "graphics constrained" to less than 4GB even with the 4GB Patch. That can produce the sort of problem you display. Regarding that Intel HD5500 chip in particular I found: "However, even a low-end dedicated GeForce 820M is about 10 - 30 percent faster than the HD 5500. Games as of 2014/2015 will usually run fluently only at (very) low settings." FNV is a 2010 game, so not quite as demanding as later ones, but still ... You may need to at least try a lower graphics setting.

 

I also notice you have Steam installed to the default location of "C:\Program Files (x86)\Steam". This alone will cause "weird" problems because that is a "system protected" folder path and Windows doesn't let even programs installed there to alter files once they are installed. 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 but didn't change it for older games); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. Among other things, later versions of Windows (since the game was released) force files in "system protected" folder trees to be "read only" regardless of how you set them.

Don't move it to "User\Documents" either, as "executables" are not permitted to run from there for similar "anti-malware" reasons.

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. With the game moved out of the default location you will not need to be running it as an "Administrator Account", which is safer. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.

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.

At this point, I don't see anything else to suggest that offers a better likelihood of improving the situation, with the possible exception of removing (or at least disabling) "ClarityDarkNights" just because such "environmental overhauls" (sky, weather, landscape, etc.) with a broad reach can cause issues with some DLCs, even if they didn't on the author's setup.

-Dubious-

[JonesenoJ]

Quick update, I had to re-download the DLC to get it to function properly, nothing else worked.