Greg

I never really understood why some mod authors created the C# style installers. It seems to me the XML style FODMOD does the job fairly nicely and the XML schema isn't all that difficult to understand.

In that case, run the .NET Framework Setup Verification Tool and follow the links near the top of the page to the .NET Framework Repair Tool if necessary.

You should have both machine.config and web.config in %windir%\Microsoft.NET\Framework\v2.0.50727\CONFIG. If this is the folder you took the screenshot from, you might try running a repair of the Microsoft .NET Framework 2.0 and 3.5 to see if this fixes the issue.

I think it's best to leave this in place because it may help someone that runs into the same issue in the future.

Topic moved to Mod Organizer 2 support.

It seems some process on your system is locking files in the mods folder for some reason. The easiest way to find out what's locking the mods is to download and run Process Explorer from the SysInternals suite. When Process Explorer comes up, click Find | File Handle or DLL, enter the name of one of the locked files (e.g. somerandometexture.dds or somerandommod.esp), and it'll tell you which processes have an open handle to that file.

It's most like something has one or more files in that folder locked when you attempted to delete the mod. When this happens, Windows deletes all the unlocked files and adds the locked files to a "pending delete" queue. Unfortunately, Windows Explorer is dumbed down and doesn't have a clue how to handle this scenario so it reports an "access denied" error that often leads people down the wrong path instead of the correct error reported by Windows. The folder will most likely vanish if you log out or reboot to force whatever to release to lock.

A memory leak basically means the game needs to allocate a block of memory for something but forgets to free this memory when it's no longer used so this block of memory can never be used by anything else. If this is a one-time leak in the application for a small block of memory, it's probably not a big deal. Where it gets to be a big deal is when the application needs to allocate memory for the same thing over and over and over again but never frees that memory so it can't be used by anything else. A real world analogy might be you buy a box of cereal every time you go to the grocery store but you never throw throw out the old boxes. Over time your pantry is full of unopened, half-eaten, or empty cereal boxes so you no longer have room to store new groceries. I can't really think of a good non-morbid real-world analogy for this, but the operating system reclaims all memory used by the game after the game exits or crashes.

In fact, I'll go one step further by stating that you should really be testing the game after installing each section to verify stability. This way you have a very narrow list of candidates that might be causing issues so troubleshooting is significantly easier.

Ah... so this option is available only when using an HDMI cable. This may explain the apparent discrepancy and all the bickering on the AMD forums about missing settings.

Going with your logic, room rental in Riften should be 250 because I'm sure Maven is getting a cut.

A possible option is to uninstall the game bar or the XBox stuff. I remember seeing instructions for doing this somewhere, although this goes with the usual disclaimers and Microsoft may reinstall it when you least expect it.

You should use Mod Organizer 1.3.11 for Skyrim Legendary Edition. Mod Organizer 2 is for Skyrim Special Edition and Fallout 4.

Yeah, the Color settings have been moved although I find this less than useful because all this is supported directly by my flat panels. The one setting that no longer exists (at least I haven't been able to find it) is the Pixel Format setting. If you want to include pictures or screenshots, you'll need to post them on an image hosting site and include a link to them in your message.

I don't recommend this because you may run into conflicts with different versions of the same mod or duplicate mods with slightly different names that can be a pickle to troubleshoot. This will also take the modlist and load order from one instance of Mod Organizer and blow away the other so in the end you still have only one active profile instead of a "merged" set. Of course, you can note what's different in the download folders between the two instances, copy the files from download folder to another, and install them as if they are freshly downloaded from Nexus.

The information provided in that link is a viable option with AMD GPUs with drivers up through 16.5 or thereabouts. Unfortunately, AMD removed "My Flat Panels" in a version shortly after 16.5 and the current version doesn't even have "Radeon Additional Settings" in Preferences. The executable is still on disk if you know where to look, but the only options are Preferences and Eyefinity.

I hope this does not mean Steam is sneaking this into the game when we least expect it.

If you click the Configure Profiles icon at the top, click the profile you want to copy and then click the Copy button. This copies the selected profile to a new profile with the name of your choice. EDIT: This works with Mod Organizer 1.3.11 but I don't know about Mod Organizer 2.

The Papyrus log is not a crash log. You should keep the Papyrus log disabled because the Papyrus log can overload the scripting engine. Unfortunately, I'm not familiar with the majority of the mods you have installed so I can't help much. I see you have a lot of follower mods and I can say from experience that having a lot of NPCs can cause issues. Have you gone through all your mods in TESVEdit to resolve all conflicts?

System Specs will definitely be useful here. The only other thing I can think of is to use BethINI to ensure your Skyrim.ini and SkyrimPrefs.ini files are in good working order. I also have these differences in enblocal.ini, although I doubt these changes will cause the behavior you are seeing. I'd definitely use BethINI first since some of the settings in Skyrim.ini and SkyrimPrefs.ini can do some really odd things. [GLOBAL] UseDeferredRendering=true [PERFORMANCE] EnableOcclusionCulling=true [ENGINE] LodBias=-0.33

You should sort your mods into an appropriate load order using LOOT. This note states that users should not sort the masters in hearthfireextended.esp by loading the mod into TESVEdit, right clicking, and selecting Sort Masters because doing so will break the mod. It has nothing to do with sorting the load order using LOOT, although I understand why it might be confusing.

Are you perhaps pressing B at some point when the FPS drops to the bottom of the ocean? If so, this is the ENBoost brute force kicking in for screen archers. It basically forces the game to render maximum quality graphics for screenshots at the expense of very poor FPS. A number of users were caught off-guard when this was first introduced just by entering a character name during the intro that contains a B. I always set KeyBruteForce=0 to disable the shortcut key for this feature.

If I'm not mistaken, you need to create the bashed patch first then any ASIS/SUM/SkyProc patches after the bashed patch. If you need to rebuild the bashed patch, deactivate any ASIS/SUM/SkyProc patches, rebuild the bashed patch, and then activate any ASIS/SUM/SkyProc patches. If you don't do this, you'll end up with a Sheogorath patch from the Daedric realm that won't work.

I think what you are describing might be a known issue with Mod Organizer 2. It seems Mod Organizer 2 is in a bad state after exiting the game so the workaround is to restart Mod Organizer 2 after exiting the game. I seem to remember LePresidente posted some information about this and asked if any C++ developers could help fix this issue. Mod Organizer 2 crash due to running out of Memory after closing Fallout 4 0x800705aa exceptions 0xC0000005 exception after writing to file via usvfs_x64 with xEdit

This is pretty awesome and my hat's off to the Microsoft developers that walked this up the chain to get it fixed so quickly. What I find really annoying though is that the original 4GB issue sat in Microsoft Connect since 2015 and is still active. I think Microsoft Connect was a good idea when it was created, but it's become a dumping ground for issues and is no longer useful. https://connect.microsoft.com/VisualStudio/feedback/details/1263324/gpu-memory-allocation-limit-on-directx9-windows-8