Greg

This shouldn't affect Mod Organizer's ability to run because Mod Organizer is a portable application that includes pretty much everything it needs to run (including Python 2.7 and Visual C++ 12.0 runtime) and Python is not used when starting Mod Organizer. Python is required to run some of the plugins, but this comes into play only when you run these plugins.

MO 2 is a 64-bit application primarily targeting Fallout 4 for the time being.

I think seeing high GPU usage and low CPU usage is fairly normal for Skyrim with even a half-decent CPU because Skyrim isn't really CPU bound. Change these settings in enblocal.ini: [ENGINE] EnableOcclusionCulling=false [THREADS] DataSyncMode=0 If you are using an AMD video card, change DisableDriverMemoryManager=true in the [MEMORY] section.

If you let Mod Organize manage the bsa archives and both bsa archives s are checked in the Archives tab, you can move the two dummy plugins to the "Optional ESPs".

I see the bulk of the links on the STEP Nexus page are to the general wiki pages (mod pages for mods bundled in the STEP compilation and the change log page), so users are most likely to land on the wiki page and then see the register link on the wiki. I see one link to the STEP forum on the STEP Nexus page and it's under User Contributions just before the STEP Compilation Credits.

You should have one and only one bashed patch that is created near the end of the guide. The only information I remember mentioning multiple bashed patches is when you have multiple profiles in Mod Organizer. Let's say you create a profile for STEP Core and a second profile for STEP Extended. In this case you will need one (and only one) bashed patch in each profile, but the bashed patches must have unique mod names in each profile (say STEP Core Bashed Patch for the STEP Core profile and STEP Extended Bashed Patch for the STEP Extended profile).

I'm not a big fan of the killcam so I usually keep it disabled.

The lighting in that screenshot looks about right to me.

Moved to Skyrim Revisited Support

Do you see anything relevant in Event Viewer that might explain why Mod Organizer isn't starting?

In the right pane click the Archives tab and then check the box labeled "Have MO manage archives". Also make sure all the *.bsa files in this tab are checked.

If you have Naussica's Tweaker installed, you can set the base speed from the MCM menu. If I remember correctly, it's a setting in the Actor tab.

You can use spoiler tags like this: [spoiler] ... paste text here [/spoiler]

Install and enable memory blocks log to make sure the skse memory patch is working and that you aren't hitting the DefaultHeapInitialAllocMB limit. The first line should be something like 512 256 where 512 is DefaultHeapInitialAllocMB-256 and 256 is ScrapHeapSizeMB. I don't know why the SKSE team went with DefaultHeapInitialAllocMB-256 because it's confusing as Hades. If the first number in the last line is the same as DefaultHeapInitialAllocMB-256, you hit the limit and need to increase DefaultHeapInitialAllocMB. IMPORTANT: You must play the game with Memory Blocks Log enabled until you reproduce the crash because the memory allocated to DefaultHeapInitialAllocMB jumps around significantly based on a number of factors.

Physics issues with the wagon is typically caused by not having vsync enabled so make sure you have iPresentInterval=1 in the display section in skyrim.ini, EnableVSync=true the Engine section in enblocal.ini, and Enable VSync in your video card settings set to use application settings. VSync isn't enabled if any one of these is not set correctly.

The introduction of Windows 10 and the switch in Microsoft's strategy has made Windows Update somewhat of a pain in the backside. I used to just automatically install the important updates and selectively install the optional updates. These days I spent a lot of time carefully reading the descriptions of every update Microsoft releases and I do not install any updates that seem even remotely dicey or that lack a clear description. I've been seeing a few lately that have a list of updated files but that fail to mention the purpose of the update. It's gotten to the point that I don't check Windows Update as often as I should because it's so time consuming to double check everything.

I'm with Manga on this one... you really need to try it for yourself.

Do you have Skyrim installed in a UAC protected folder (like Program Files (x86)) and have you tried disabling antivirus to see if this has any affect?

Moved to F&LNV Support. In your screenshot, you see "BMDT - Biped Data" in the first column of the first row. You don't see this text in the same column for the other three mods because it's just a label xEdit shows in the first column indicating the record type. If I'm reading this correctly, YUP is in the third column and looks like this: blank cell Head, Hair, Headband, Hat, Eye, Gl... Head Hair Headband Hat Eye Glasses Mask Power Armor Power Armor Click in the blank cell just above "Head, Hair, Headband, ..." and drag it where it needs to go. This copies the entire record and the red should turn green indicating the conflict is successfully resolved.

I usually do this in separate profiles or separate instances of Mod Organizer so I can easily rollback to a stable base when experimenting with new mods. I install STEP 2.2.9.2 Extended into a "STEP 2.2.9.2 Extended" profile. Once I've verified this is stable, I copy it into a new profile add any new mods to the new profile. Profiles are fairly cheap in that they don't take up much disk space, and it's really easy to blow away a test profile if I need to rollback the last couple mods to try again.

Edit Skyrim.ini and make sure iPresentInterval=1 in the Display section: [Display] iPresentInterval=1 Edit enblocal.ini and make sure you have EnableVSync=true in the Engine section: [ENGINE] EnableVSync=true Open your video driver settings and make sure VSync is set to use application settings. If you are using a standard display, this should enable VSync. If you are using a new-fangled display that does not use vsync you may need to enable the FPS limiter.

After you install Realistic Ragdolls and Force, move the plugin to Optional ESPs and leave it there. You don't need it when installing the STEP Compilation or when creating the bashed patch. After you install Static Mesh Improvement Mod, move the plugins to Optional ESPs and leave them there. You don't need the ESPs when installing the STEP Compilation or when creating the bashed patch. If you update the bashed patch, you don't need to reactive the mods already in the bashed patch. You must run LOOT to make sure all plugins are sorted correctly before generating the bashed patch. After you update the bashed batch, make sure WM Trap Fixes.esp is activated in the right pane.

Yup... a portable application can be unzipped and run from anywhere you want.

You have Skyrim installed in the Program Files (x86) folder so you're probably running into permission issues. Windows by default requires administrative access to access anything in Program Files or Program Files (x86). If you're running Windows Vista or later and write anything to Program Files (x86) as a standard user, Windows redirects to a virtual store in AppData instead so you might find those mysterious files in C:\Users\[username]\AppData\Local\VirtualStore\Program Files (x86)\... The disadvantage to this sneaky redirection is that the application that wrote the file that ends up being redirected can see it, but other applications may not. Assuming this is the case the easiest solution is to use Steam to move Skyrim to folder you own and that isn't protected by user access control (like C:\Games). See Why cant I edit a "Program Files" file on Windows 7?

Both logs show the SKSE memory patch is working and you are not overallocating either of the two blocks, so this isn't the problem. You can also rule out a missing master because a missing master would cause the game to crash immediately before you even have a chance to play. Unfortunately these rule out the easy to diagnose issues. Some other possibilities you might check: If you've merged any mods, verify you merged these mods properly and in the correct order.Double check the bashed patch and any other patches.Make sure you are using the latest versions of TES5Edit, WryeBash, Merge Plugins Standalone, and any other tools.As a last resort temporarily disable your antivirus software to see if it's being a bit overzealous.