Greg

Mod Organizer 2 should work quite well with Fallout 4, although you may want to use the latest 2.1.4 dev build on discord. The 2.14 dev builds fix a lot of issues related to downloading from Nexus. I'm currently using it with Skyrim LE and Skyrim SE.

The problem may be that you have Skyrim installed in C:\Program Files (x86) so Windows UAC is preventing Mod Organizer from hooking SKSE or the game. I suggest moving Skyrim (and any tools like Mod Organizer) out of C:\Program Files into folder you create like C:\Games\Skyrim so you don't run into issues with permissions. Also note that if you run SKSE or Skyrim as administrator, Windows prohibits Mod Organizer from hooking SKSE and Skyrim so the virtual file system won't work (meaning you won't see any mods in the game). If you are on Windows 10, open Explorer, right click on ModOrganizer.exe, and click Properties. If you see an Unblock checkbox or button, you'll need to click Unblock and OK to unblock the application. If you're still not seeing any mods in the game after going through all of the above, temporarily disable your antivirus software to see if it is interfering. If this is the case, you can add a rule to exclude ModOrganizer.exe to see if this works.

You really shouldn't need to run FNIS or any of the tools as administrator. The basic methodology is to keep everything out of C:\Program Files and any other UAC controlled folder to avoid permission issues. Windows 10 can also reduce rights on applications if the executable is blocked (e.g. downloaded from the Internet or other "unsafe" sources) so it's generally best to unblock archive files (*.zip, *.7z, *.rar) before extracting the files to avoid this issue. (Right click the archive file, click Properties, click Unblock, and click OK to unblock the archive file.) i don't know that this really affects FNIS, but Windows 10 blocks Mod Organizer's virtual file system if ModOrganizer.exe is blocked.

Go back to Mod Organizer and scroll down the list of plugins in the right pane to see if any of them have a flag indicating missing masters. If you hover over the icon, it'll tell you which master(s) are missing for that plugin.

I get a 404 on your video link.

I'll have to wait for DoubleYou to chime in on this one because I don't know if he left this out intentionally for some reason or whether it may be an oversight.

BethINI organizes all sections and settings into alphabetical order and removes a lot of redundant settings so skyrim.ini and skyrimprefs.ini are smaller and easier to navigate. When I run BethINI on Fallout 3, Fallout New Vegas or Skyrim, Disable Screenshots is in the General tab. I assume it should also be on the General tab for Fallout 4 but I don't have Fallout 4 to verify this. I seem to recall this is the way it works when I run it as well in that it updates the INI files in all profiles within the specified Mod Organizer path and the default INI files in your documents folder.

The current version of LOOT dropped priority order in favor of the category tree so you'll either have to use an older version that supports priorities or migrate to the tree structure.

I finally got this installed and and looked at all the changes in a few different places and I think it's a good fit so you get my vote.

I expected as much and screenshot can only go so far, so I really prefer to see how these look in the game before making a decision.

The screenshots look really nice so I just downloaded and will play with it in the game.

When you say you used the classic DEP fix, I assume you mean you tried to disable data execution prevention for GenerateFNISForUsers.exe? It's been many years since I used Vista, but I seem to recall it either has DEP disabled by default or enabled only for core Windows executables by default. Also note that GenerateFNISForUsers.exe is a .NET Framework application and these do not execute code from data areas so the DEP check shouldn't be applicable here. Also note that if you are running GenerateFNISForUsers.exe as an administrator, you must also run Mod Organizer as an administrator. I think even Vista prohibits standard user processes from hooking admin processes. Having said this, you really shouldn't need to run Mod Organizer or GenerateFNISForUsers as an administrator. This is why we recommend installing Mod Organizer, the game, and all tools outside UAC controlled folders like C:\Program Files.

Physics in Skyrim is tied directly to the refresh rate of the display so you should enable vertical sync if you have a 60Hz display or lock it to 60 FPS in enblocal.ini or the video driver.

Are you editing the SkyrimPrefs.ini used by the game? If you're using Mod Organizer, click the INI Editor button at the top and it'll open Skyrim.ini and SkyrimPrefs.ini that you should be editing. I don't know about nvidia, but on AMD cards antialiasing should be set to application controlled. I assume the same is true for nvidia as well. [Display] iMultiSample=4

The red text is normal so don't worry about it.

I assume MOTO is Mage Outfit Texture Overhaul and AAJ is Appropriately Attired Jarls. Mage Outfit Texture Overhaul should be compatible with Clothing and Clutter Fixes. I'm currently using it with Clothing and Clutter Fixes 2.0 in another build and haven't noticed any issues with it. The STEP Compilation for STEP Extended requires Clothing and Clutter Fixes and Complete Crafting Overhaul, so you can try Clothing and Clutter Fixes 2.0 without Appropriately Attired Jarls and Mage Outfit Texture Overhaul if you want.

I think the only time I've ever been able to get in a bow shot at the giant is when I cut in between the mountain and the back of the meadery.

Have the FormIDs for these head parts been renumbered in the merged patch?

I'm just guessing here, but could it be the EITM - Object Effect on the laser rifle in the Blackened mods? I don't remember seeing this effect on the laser rifle, but this may be because I either haven't used the laser rifle or because the RH_FWE Bridge.esp overrides this effect with an empty effect.

The easiest way to is to click the INI Editor button in Mod Organizer. This pops up a dialog containing skyrim.ini and skyrimprefs.ini that are used by the selected profile. DoubleYou also created a guide here that covers all the settings available in skyrim.ini and skyrimprefs.ini.

You might pop over to the Mod Organizer discord channel to see if this is a known issue that needs to be logged and fixed. I assume you are using Mod Organizer 2.1.3 on Nexus. You might also try Mod Organizer 2.1.4 Dev Build 5 that fixes a UVFS issue with paths starting with \, but I don't think this applies to the Papyrus compiler. The 2.1.4 dev builds mostly fix issues related to downloads and the latest version of LOOT.

ENBSeries adds memory management capabilities, offloads some extraneous data used by the game into a separate process, and provides additional graphics capabilities that are used by ENB presets but the additional graphics capabilities are mostly disabled. Follow the Optional Proxy settings instructions only if you are installing an enhanced antialiasing plugin like FXAA for Skyrim. If you are not using one of these plugins, your task is easy... Leave ProxyLibrary alone and set EnableProxyLibrary=false. Note that ENB Series doesn't even look at the ProxyLibrary setting if EnableProxyLibrary=false so you don't need to worry about it.

If you want to install STEP Core or STEP Extended, you should follow the STEP 2.10.0 Guide by installing all of the mods in the guide in the order listed in the guide. The STEP Compilation mod is installed toward the end of the guide.

1. You should generally always select Merge unless the guide explicitly states to install as a new mod. The only time I use replace is when I installing the wrong options and need to start fresh by reinstall the mod using the correct options. Think of the two options this way using Unofficial Patch Plus as an example. You install the Unofficial Patch Plus main file and then install the Unofficial Patch Plus - Project Nevada Patch optional file. If you select Merge, everything in Unofficial Patch Plus - Project Nevada Patch is installed into the same mod folder as Unofficial Patch Plus so you have everything from both the main file and the optional file. If you click Replace instead, Mod Organizer deletes everything in the Unofficial Patch Plus mod before installing Unofficial Patch Plus - Project Nevada Patch so now all you have is the optional file. Only use Replace when you need to completely reinstall the mod fresh. 2. I do not know. I just recently purchased Fallout 3 and Fallout New Vegas from GOG so I'm not really experienced with the mod landscape for these games. 3. Yes, just install the mods in the order listed in the guide. If I remember correctly, you may run across a few plugins with missing masters as you go through the guide, but these are installed later in the guide. 4. If you go to the Mod Organizer 2 page on Nexus, you'll see Mod Organizer 1.3.15 listed as "Mod Organizer 1 Legacy" in the Miscellaneous Files section. This is an updated version of Mod Organizer 1.3.11 that fixes the Nexus download issues. I would use this one with Fallout 3 and Fallout New Vegas for the time being. Mod Organizer 2 should work fine, but I tend to take small steps. 5. See 3.If you are thinking about adding new mods on top of the guide, I suggest getting the basic guide working first. Once you are comfortable with it and it seems to be working fine, copy your working profile into a new profile and add any additional mods into the new profile. One caveat is that any generated mods (like the bashed patch and FNVLODGen output mod) will need to be separate mods for each profile -- meaning you should have say Bashed Patch FLNV for the bashed patch in the guide and Bashed Batch FLNV+ in the new profile. If you do it this way and find yourself in a mess, you can always go back to the working FLNV profile to start fresh. Just delete the profile you are testing with, copy the working FLNV profile to a new profile, and start again with a good foundation.

The script determines which bash tags are appropriate and adds these tags to the header of the mod. Later when you create the bashed base, Wrye Flash uses these tags in the header to determine which mods should "win" the conflict in the bashed patch. The result in a nutshell is that the bashed patch resolves a lot more conflicts more intelligently than it would without these tags.