Sarcasm

I cannot get Archive Invalidation working for Fallout New Vegas in MO2. It works fine in MO1, but MO1 lacks functionality for the JIP LN custom ini's in its INI Edior, and I'm not sure if those ini settings are working at all from the profiles folder. My problems are: I have "Automatic Archive Invalidation" checked on the profiles page, but this does nothing at all.Archive invalidation mods do not work because they are all done through .bsa archives, and MO2 does not handle archives. Thus it is impossible to enable the AI .bsa. AI work fine in MO1 since that manager can handle archives and the checkboxes in the Archives tab work. "Automatic Archive Invalidation" still does nothing in MO1. I would be thankful for any suggestions on gettnig AI to work in MO2 with a method that doesn't involve .bsa's.

Not that I know of, I right click on a folder and click Properties. What gets to me is that it only happens with Skyrim.

It's some weird stuff going on in the Skyrim and Steam folders. Here is a screenshot of steamapps/common with all installed games shown. It's reporting as only 75.7GB which is obviously wrong. TWW2 and Vermintide2 are almost 60GB each, and both Skyrim installs are over 100GB each. Every game in the folder reports its correct file size except for the two Skyrim installs. The first Skyrim install is a 2.2.10 STEP game, the other is an older 2.2.9.2 install that I keep around due to it having old mods no longer available like final version of Wyrmstooth. Here is the base folder for the 2.2.9.2 install reporting at only 33GB, which is probably lower than a standard full STEP install. Inside that Skyrim's Mod Organizer folder, here is the mods folder reporting at only 17.7GB. Inside the mods folder itself, if I do a Ctrl+A to select all mod folders, they report correctly at 122GB. Seems like it's a problem with the drive reading my Skyrim folders, which in turn is messing its ability to read the full Steam folder size. But I don't know much about this stuff myself. How would I check for firmware corruption?

This is 100% reproducible, every time restart or not. Just takes a good 15min to finally add everything up to 28TB. I thought this to be a Skyrim/MO issue since every other game folder in my steamapps/common is reporting the correct file size. However, my steamapps/common folder itself it reporting as only 75.5GB which is a lie. Skyrim alone is more than that, and there are several other apps installed that total well over 75.5GB. It should be at 600GB+. I errorchecked the drive in Properties/Tools and it found no problems. I'm not familiar with Windows file history, actually I've never heard of it. I've searched my system and it doesn't seem to have it set up at all, it looks like this is a tool for backing up a drive's contents via a connected external hard drive, which I do not have. I haven't reformatted in over a year now, so it looks like the time has come to light the purging fire.

My STEP install for Skyrim is showing up with an unbelievably large file size on my SSD. As you can see in this screenshot, the total size of the drive is 931GB but the file size of my Skyrim folder is being reported as an outrageous 28TB. Is this because of Mod Organizer's virtual drive and MO profiles? I don't have enough profiles for the folder to be multiplied to even a fraction of this size. Is this normal?

It is. I have two Skyrim folders in the common\ Steam folder. An old version using STEP 2.2.9.2 and the new one using 2.10.0. By simply renaming the folders I can switch between the two.

Hello again, this is caused by the ENB 0.319 d3d9.dll binary file. My old install uses the binary file from 0.262; if I copy this d3d9.dll into my STEP 2.10.0 install folder then the game works fine. If I restore the 0.319 binary then the crashes resume. I downloaded some of the ENB binaries from the dev site. The two latest versions, 0.319 and 0.292, causes these crashes in the same way. 0.262 had no problems. I downloaded an even older version, 0.236, which also had no problems. I didn't go through the rest of the older versions but I assume they work. Something in these newer binaries is causing a serious problem. I don't know much about this sort of thing, so hopefully someone reading this does.

I'm using old fashioned Windows Defender, nothing fancy. I added common\Skyrim\ to the exclusion list anyway. It can't be that because if I rename my old 2.2.9.2 folder to Skyrim, then the game works with its old files. It's the new 2.10.0 folder that doesn't work with its new files, and the ENB ini's have the same names in each folder.

ENBoost is causing this to happen. If I delete d3d9.dll then everything works fine. Having followed the directions for it twice now, I'm not sure why this would happen.

I've done as you said. I repeated the BethINI and ENBoost parts of STEP. I'm not sure why, but despite the fact that I did exactly as specified originally, my BethINI settings were totally different from what was recommended. Still it made no difference. So, I anticipated problems like these and I made sure to carefully organize my installation by making a profile for each section of STEP and using empty mods as section dividers. I thought it would help me isolate a problem, but the results are confusing to say the least: Every profile crashes upon returning to the main menu from in game, even the default profile with no mods active.Every profile can load old saves from other profiles, but when creating a new save on that profile (using coc qasmoke to skip intro) the game crashes on load every time even on the default profile with no mods active.Upon activating Alternate Start - Live Another Life, the game crashes while loading old saves as well when DynDOLOD is active.Edit: I should add that the same holds true when starting the game up through Steam without MO. Can load old saves, crash loading new saves, crash on return to main menu from in-game.Based on what I see, it seems the problem is with Skyrim itself, probably in the base common\Skyrim folder. Alternate Start and DynDOLOD crashing when active together is a mystery to me but I would think it is related to whatever is causing even the default, unmodded game to crash when loading saves or returning to the main menu. However this is a guess based seeing something that I have never seen before. Has anyone seen something like this before?

I decided to experiment by copying my mods\ and profiles\ folders from the STEP 2.10.0 install into the Mod Organizer for my STEP 2.2.9.2 install. The game works just fine this way. I can save, I can load, and I can quit to main menu from in-game (which also caused a crash previously). It doesn't seem to be an issue with system files like DX. It seems to be a problem with the installation itself and what is inside the Skyrim folder. I've already verified cache to no avail. Any suggestions on how to proceed? I'm about to simply go back to 2.2.9.2, but I'd very much like to use the updated order.

I've done as you commanded and it seems to be working. I'm not sure why, since I installed the DX9 runtimes back at the beginning of STEP since it is part one of the ENBoost install. Thanks for this suggestion, I'm not going to mark it as solved yet though since I have a feeling the crash may return. On a related note I should point out that DynDOLOD kept failing with an error when I tried to run it with the Bashed Patch active. I found this strange since the STEP install for DynDOLOD does not mention disabling the Bashed Patch. edit: Okay, nevermind. It's back to crashing. I reinstalled DX9 runtimes, reinstalled DynDOLOD from nothing, and the game was working. Then I came here to write this post. Now 30 seconds after posting, I start the game up again and it's crashing on load. I have no idea what to say about this...it was just working 2 minutes ago and I've made no changes in the meantime.

Hello, I have just finished installing all of STEP Extended and all was well in my world. However, I then set out on my own modding adventure away from my STEPparents and started by shopping for an ENB to use. In order to do this I need to reverse two of the STEP instructions for ENBoost: With these two settings this way, ENBs do not work as the graphics injector is turned off. However upon reversing these values to false and true respectively to make ENBs work, the game now crashes constantly on loading a save game. I don't even get to see a loading screen, I press enter to load, enter again to confirm, and now I'm looking at my desktop. Strangely, turning off DynDOLOD fixed the crash. Then I installed Alternate Start - Live Another Life to start a new character without having to coc or sit through the 20 minute intro, and I find more complications. DynDOLOD seems to now causing the game to crash anymore, but having both DynDOLOD and Alternate Start active simultaneously causes the game to crash on loading a save. Loading one or the other works, but both does not. Even so, with only one or the other active, upon activating a few more mods I'm back to crashing on load. However if I set the two ENB settings quoted above to their STEP values of true and false, the game loads just fine. I cannot explain this. Obviously this is a problem as I cannot play Skyrim without an ENB, and one cannot play Skyrim with an ENB using those settings. It may or may not be relevant but I have an old 2.2.9.2 version of STEP laying around, and that works just fine with ENB active. Tips on how I can progress would be by me appreciated, thank you.

I thank you for this reply. However I solved it myself by simply installing the Core Patch esp alone so I could see which master was missing. It was aMidianBorn_contentaddon.esp. Looking at the Install page I see why - the massive Book of Silence installer guide takes up much of the page, with the content addon barely visible below. I completely missed it !

Despite meticulously installing according to the STEP guide, the STEP Core patch is inaccessible in the installer. As far as I can tell, there is no way to efficiently troubleshoot this because the Guide itself no longer puts CORE tags on the main page of the guide, I would have to go through every mod's wiki page one by one. This would take hours. The possibility of it still not working after all those hours is discouraging, and brings me here. How do I force the Core Patch to install manually, without the installer? Do I only need 00 Core and one of the 04 STEP Core Patch folders? Is this all that is required for the STEP Compilation? I'd very much like to dissect this and piece it together correctly. For the record, I think the reason it is not accessible is due to contradictions within the guide itself. i.e., listing ENBoost as absolutely required for any STEP install, then listing SKSE-Elys-AltF4 as unnecessary if you ENBoost already. Why is this mod listed at all if one of the very first absolute requirements invalidates need for it? There were other confusions that I would have to fish through the guide to find, but that would take a great deal of time.