Greg

You should also go into settings and change the usfvs log setting from debug or verbose back to info.

You make a good point that I think some bad ini settings may cause this as well, but I think BethINI should rectify this if I'm not mistaken. When I set up the guide, I created a new game using only the vanilla DLC and used this saved game to test as I went through each section or each merge. It takes a lot longer to do it this way, but I was to catch most of my mistakes. I still have the wrong version of one of the mods in my profile, but I've forgotten which one and it doesn't seem to be causing any issues (that I've noticed anyway) so I haven't gone back to fix it yet.

Yeah, I think these are different issues. In your case it looks as if GenerateFNISForUsers is either not running at all or it exits before showing the UI. If I'm not mistaken, you'll need .NET Framework 3.5 enabled for FNIS to work. You can enable both .NET Framework 3.5 and 4.7 at the same time, but you most likely don't need ASP.NET. This is used only when doing web development or running web applications locally.

I wasn't aware DirtyWeasel had a tutorial video on Mod Organizer 2 so this is good to know. Thanks! The modding scheme for Skyrim SE has really started to flourish after SKSE and a few other foundational mods were released, so I suspect we'll see a migration to Skyrim SE. It introduces a few new issues, but the memory limits are pretty much gone with the 64-bit version of the game.

I had this issue when I rebuilt the bashed patch incorrectly, but I think it can be caused by a variety of other reasons as well. Kelmych may have better ideas, but I suggest double checking the script extender installation and if this is correct to uncheck plugins in the right pane on section (or small group) at a time from the bottom until the game works.

What you show in the video is correct and it should be as simple as this. The only cases I can think of that might cause this issue is that FNIS detected a pirated copy of the game or moddrop installed on your system and refuses to run, or perhaps the .NET Framework required to run FNIS is not installed. I think you already ruled out moddrop and I'm assuming this is a legitimate copy of Skyrim. I think you stated that it ran at least once so this seems to indicate the .NET Framework is installed and working. Just to cover all the bases, can you provide the link to the version of FNIS you are installing and the version of Mod Organizer you are using? I think you are using Skyrim Special Edition right?

You should not install Mod Organizer 2 in the game folder or the data folder because the virtual file system won't work correctly.

If you are on Windows 10, right click ModOrganizer.exe in Windows Explorer to see if it's blocked. If it is click Unblock and OK to unblock it. Repeat this loot.exe and any other executables that aren't working. This probably isn't your issue since Windows 10 prevents Mod Organizer's virtual file system from working at all anywhere if it's blocked, but it's worth a shot.

I'm not aware of anything similar for Mod Organizer 2 at the moment. I think the best source of information right now is the Gamer Poets videos. The only other difference of significance I can think of off the top of my head is that Mod Organizer 2 can run in portable mode (which is essentially exactly like Mod Organizer 2) or in instance mode. If You run Mod Organizer 2 in instance mode, you can create and switch between as many instances as you want where "instance" can be for different games or somewhat like different profiles for a game. This makes it easy to switch from say Skyrim Legendary Edition to Skyrim Special Edition to Fallout 4 without having to close Mod Organizer.

When you run the game (e.g. skyrim.exe), the game attempts to load all its dependencies and one of these dependencies is the DirectX 9 runtime in d3d9.dll. The DirectX runtime is normally installed in C:\Windows\System32 or C:\Windows\SysWOW64, but Windows uses a search algorithm that attempts to find dependencies in the local folder first; if it doesn't exist in the local folder, it search all folders in the path environment variable until found. Boris just takes advantage of this search order by installing a custom d3d9.dll in the local folder that initializes ENBoost and then loads the real DirectX 9 runtime.

The original video is for Mod Organizer 1.3.x that manages BSAs without requiring the dummy plugin to load the assets in the BSA. This is somewhat of a controversial feature and is very complex to implement, so this feature was dropped in Mod Organizer 2. If you are using Mod Organizer 2, you must place the dummy plugin in your load order in the right pane in order to load the assets in the BSA.

Have you tried running it outside of Mod Organizer to see if you can get the UI? I should also mention that you really don't need fnis.ini so you can leave it named as fnis.ini0. The only reason you'd rename it to fnis.ini is if you want to override any of the settings.

Open the FNIS mod and select the INI-Files tab. Do you have InstantExecute=1 or 'InstantExecute=1 in fnis.ini? If you see 'InstantExecute=1 (the line starts with a single quote), the option is commented out so you can ignore it. If the single quote isn't present at the start of the line, you enabled the option to run GenerateFNIS_for_Users without the UI -- meaning it just runs, tries to generate the animations, and exits. This may not be the issue, but it's a place to start. Do you have moddrop client installed? I just read a note on the FNIS page stating that FNIS checks whether you have the moddrop client installed. If you do, FNIS aborts the first time you run it with an appropriate warning but it refuses to run again until you uninstall the moddrrop client, uninstall FNIS, clean up all FNIS-related data, and reinstall FNIS fresh.

Open the ModOrganizer.ini file and you should see gamePath near the top. Change this to your game path and the scroll through the file to see if anything else is referencing the old game path and change these to the new game path as well. These will likely be workingDirectory or arguments for executables you've added to Mod Organizer. Note that the double backslashes (e.g. C:\\Steam\\SteamApps\\...) are intentional and should be preserved.

Run Mod Organizer 2 that you want to use for Legacy of the Dragonborn. Click the first button and you can select either Portable if you want to switch this one to portable mode or you can click New Instance to create a new instance.

If you click the "Detailed instructions available" link when you get to the Dynamic Distant Objects LOD mod, you'll find all the instructions you need install and run the mod.

If you add a new esm or esp to your load order, you should sort the load order with LOOT and rebuild the bashed patch. I don't remember the rules for re-running Dual Sheath Redux. You should run GenerateFNISForUsers if you add or remove mods containing animations or that affect the skeleton. You should run DynDOLOD if you add or remove mods that affect the landscape or architecture.

Did you download the High Resolution Texture Pack from Steam when you installed Skyrim on this PC? If you browse to the Skyrim/Data folder, you should see these file there. If you don't see them, you can go back to Steam to see if you can get Steam to download them for you or just copy them from your old PC.

No, this should not be normal and it's just as troubling that Properties thinks there are 33 million files in almost 3 million folders. You might reboot and see if you can reproduce this. If you can, I suggest running chkdsk on that drive to see if something's corrupted.

The easiest solution is to use LOOT 0.12.5 with the STEP 2.10 guide.

I would rerun DynDOLOD with the corrected load order to ensure it includes both landscape mods and the master references in DynDOLOD.esp are ordered correctly.

I thought I had remembered seeing these at one point when I was setting up Clear and Present Danger or Fear and Loathing, but I checked all my profiles for Fallout 3 and Fallout New Vegas and I'm not seeing these custom ini files in any of my profiles.

STEP Optimized Vanilla Textures (in the Optional Files section on Nexus) should be near the top right after Unofficial High Resolution Patch. STEP Compilation (in the Main Files section on Nexus) should be after Modern Brawl Bugs Fix and before the Bashed Patch. STEP Compilation doesn't override anything in Leanwolf's Improved Enchanter Candle Meshes and Leanwolf's Better Shaped Weapons is installed after STEP Compilation. Basically everything in the left pane should be in the exact order as in the guide.

I think z may have been tinkering with the servers because the merges page didn't exist yesterday. It seems to be back up today.

Ignore my post and pretend it doesn't exist. @TechAngel85 has the final say on such matters.