Greg

These are the settings I have for [Fonts] and [RenderedTerminal]. I don't know the definitive answer, but I think it's safe to say that if the default value for fRenderedTerminalZoom is 33, BethINI may have removed it because it's redundant. The actual value used may also depend on your screen resolution and your preferences. You can discover the default setting by leaving fRenderedTerminalZoom out of fallout.ini, starting a new game, and entering this into the console: getini "fRenderedTerminalZoom:RenderedTerminal" [Fonts] sFontFile_1=textures\fonts\darn_frankleinbold_14.fnt sFontFile_2=textures\fonts\darn_frankleinbold_16.fnt sFontFile_3=Textures\Fonts\Glow_Monofonto_Medium.fnt sFontFile_4=textures\fonts\darn_sui_generis_otl_10.fnt sFontFile_5=Textures\Fonts\Fixedsys_Comp_uniform_width.fnt sFontFile_6=textures\fonts\darn_sui_generis_otl_13.fnt sFontFile_7=textures\fonts\darn_libel_suit_otl_24.fnt sFontFile_8=Textures\Fonts\Glow_Futura_Caps_Large.fnt [RenderedTerminal] bDoRenderedTerminalScanlines=1 bUseRenderedTerminals=1 fRenderedTerminalFOV=0.15 fRenderedTerminalHPos=0.0 fRenderedTerminalScanlineScale=130.000000 fRenderedTerminalVPos=0.38 fRenderedTerminalZoom=36 fScreenLightBaseIntensity=1.2 fScreenLightColorB=0.62 fScreenLightColorR=0.68 fScreenLightColorG=0.74 fScreenLightRadius=80EDIT: Take the RenderedTerminal section with a grain of salt. I just remembered I customized the colors so I can see the markers on the map so the colors above may not be the defaults.

This doesn't seem quite right to me. You should run the launcher if you haven't already so that it creates the default INI files for the game with the correct resolution set for your display. After you've done this, run BethINI, select the appropriate game and folder for your INI files (and this can be a Mod Organizer profile), select the appropriate settings, and you're done.

It's rather unfortunate that a lot of places in the 'net recommend installing Mod Organizer in the game folder. This used to work fine with Mod Organizer 1.x even if it cluttered the game folder unnecessarily, but Mod Organizer 2's virtual file system doesn't work quite right if it's in the game folder. This may eventually get fixed, but I still prefer keeping the game folder as clean as possible..

You may need to extract files from the BSA archives that aren't associated with an ESM or ESP if you are using Mod Organizer 2. The guide depends on Mod Organizer's BSA management functionality so Integration - Couriers Stash.bsa in Gameplay Mods Merged works fine with Mod Organizer 1.3.x but the game will never see this archive with Mod Organizer 2. I think there are several other BSAs in Advanced Recon Stealth Armor, Advanced Recon Thermal Nightvision, and Yuki Mods Merged that aren't associated with an ESM or ESP as well. You might also verify you have archive invalidation enabled.

I thought modding was the game?

I know Mator has stated a few times on discord that it requires portable mode so I never tried it in instance mode either. If this is the only issue, I wonder if Mod Organizer's "Create Files in Mod instead of Overwrite" may work around this issue? Perhaps not if Merge Plugins isn't writing to the Mod Organizer folder structure at all unless it's pointing to the Skyrim data folder and MO's usvfs takes over.

If your profiles are in e.g. C:\ModOrganizer\Profiles and your mods are in C:\ModOrganizer\mods, you are in portable mode. I think if you click the first button at the top left and you see "This will restart MO, continue?" you are in portable mode. Otherwise your stuff is stored in C:\Users\\AppData\Local\Modorganizer and clicking that button brings up a list of instances.

Does Wrye Bash work normally if you run it from a command line or from Windows Explorer?

I don't recommend setting VideoMemorySizeMb above 10240 as per the comments. You might also changing EnableCompression=true to false in enblocal.ini to see if this has any effect on the stuttering.

In theory the skyrim.ini and skyrimprefs.ini files should be set to use the appropriate video adapter I think these are as follows: skyrimprefs.ini [Display] sD3DDDevice="AMD Radeon R9 200 Series" and skyrim.ini [Display] iAdapter=0 You may have already done this, but open the INI editor in Mod Organizer and verify these settings match the settings in the INI files in the My Games\Skyrim folder. Also note that if you are using "instances" with Mod Organizer 2, your INI files are in \users\\AppData\Local\ModOrganizer instead. If this doesn't solve the problem, stop by the Mod Organizer discord channel to see if the devs can figure out what's going on. You'll want to post in #issue-reports.

Interesting... it looks as KS Dragon Overhaul 2 fixes the issue with dead dragons landing perfectly before falling over. I think this is the translation of what he's trying to write: This particular behavior has always bugged me because it seems as if a dead dragon in the air should pretty much drop straight to the ground.

If you are using Windows 10 and download the ZIP file, make sure you unblock the ZIP file before you extract the files. If you omit this step, Windows 10 prevents the usvfs virtual file system from working. Open Windows Explorer Browse to the folder where you downloaded Mod Organizer Right click the ZIP file Click Properties Click Unblock Click OK

Ooooh... I hadn't considered this. If you installed this on an existing save, a lot of stuff gets baked into the save file and you may not be able to do anything about it. It's just Bethesda being... Bethesda with a rickety old game engine.

Are you using the Skyrim SE or the Skyrim LE version of Immersive Armors? Are you starting a new game or using an existing save?

I don't see anything in the logs you included that indicate anything is wrong so I think we can rule out Mod Organizer as well. One point I find troubling is that "everything is set to run in admin mode"? I assume this includes Mod Organizer because Windows prohibits Mod Organizer's virtual file system from hooking admin processes and it looks as if the usfvs hooks are working. You really don't need and should not run everything as administrator, but this isn't really relevant to your issue. What I would do is to disable all mods you have installed. You don't need to uninstall and start from scratch, just uncheck them so they won't be used by the game. Now run Skyrim to verify everything works with a vanilla game. I think you've already done this and it works fine. Now enable a few mods starting from the very top of the list -- no more than 5 or 6 at a time -- and try starting a new game again. If everything works as expected, enable a few more and try again until you reproduce the issue. This may be a bad smashed or bashed patch so you may want to disable any patches you created first. I know I've run into this crash a few times when rebuilding the bashed patch. In my case I had built the bashed patch and realized I had installed the wrong version of a mod. I replaced the mod with the correct version, rebuilt the bashed patch, and crashed. To fix it, I had to delete the bashed patch and rebuilt it from scratch.

These screenshots seem to indicate you have Depth of Field cranked up to 11 or you've installed the Extreme Blurry version of some mod. Edit your skyrimprefs.ini and set bDoDepthOfField=0 to see if this helps: [Imagespace] bDoDepthOfField=1EDIT: I forgot to mention but you may also consider running BethINI to optimize your INI settings.

Run FNVEdit from Mod Organizer and you should see the "Master/Plugin Selection" dialog containing a list of all masters (*.esm) and plugins (*.esp) you've installed and activated so far. Right click anywhere in the list of mods (e.g. right click on FalloutNV.esm) and you should see options to Select All, Select None, or Invert Selected. Click Select None so none of the files listed are checked.

Have you tried using Mod Organizer 2? This one supports both x64 and x86 executables.

Nah... I think you had it pretty much well in hand. I just threw those extra pieces of information in just in case they may help and because it's all too common today. It's rather unfortunate that most of these issues boil down to UAC by installing stuff in C:\Program Files or C:\Program Files (x84), Windows 10's overly aggressive UAC controls, or antivirus software's overly aggressive lunacy. I know some of us have been lulled into the days of downloading a ZIP file, extracting it somewhere, and running it with no issues. Windows 10 changed that game. If ModOrganizer.exe is blocked by Windows, the virtual file system flat won't work. I don't have Windows 10 so I don't know how far Microsoft has taken this. Some antivirus software is also getting really aggressive by treating the virtual file system as rogue malware. I don't remember which package, but one poor user found his antivrus software was deleting usvfs*.dll without notification every time he tried to play the game.

A couple of other points that may come into play with Windows 10... Open Explorer, right click on ModOrganizer.exe, and click Properties. If you see an Unblock button or Unblock checkbox, click it to unblock the executable and click OK to close the dialog. If you don't do this, Windows 10 will not prevent Mod Organizer's virtual file system from working. Do the same thing for Wrye Bash.exe to unblock it as well. If you still have issue, you might temporarily disable any antivirus software to see if it is interfering.

I'm confused by the question as well. I can't tell if he means Mod Organizer is saying a plugin is missing a master, the mod won't install, or Skyrim is saying the save depends on assets that are no longer available.

It looks as if something is killing the hooking process. If you are on Windows 10, run Windows Explorer, right click on ModOrganizer.exe, and click Properties. If you see a block button or checkbox, click it and click OK to unblock it. You might also do this for LOOT.exe. This may not really be the issue though because it seems Windows 10 blocks the hooking method for everything if ModOrganizer.exe is blocked. It's a bit strange that this is only happening with LOOT. Have you tried running LOOT by itself from say Windows Explorer instead of Mod Organizer?

I imagine it doesn't make much difference because Windows caches the files on first load so the plugin is really only saving the time to parse the entries, and the logic to parse the file isn't really all that slow.

You should first run Fallout4Launcher.exe by itself (not from Mod Organizer) so it creates the registry entries and INI files required by the game. After you do, you should be able to run Fallout 4 from Mod Organizer. Note that running Mod Organizer and games should not be necessary and is not required. It's rather unfortunate that Steam defaults to installing everything in C:\Program Files or C:\Program Files (x86) because you'll run into all kinds of UAC issues. We recommend installing Steam and Steam games into a separate folder to avoid these UAC issues.

One notable difference I see is that you don't have have FO3 Wanderer's Edition - Main File.esm. You have the esp, but I think should have both the esm and the esp.