GrantSP

Move your mouse to the far right and press the mouse left button, the cursor should change to the "moving UI element" style and when you move the mouse to the left, the right-hand pane should snap into view.

There are two distinct outcomes for those that use MO to manage an Oblivion game. If you have the Steam version then you will/might experience difficulties with some modsIf you have the retail disc version you will see no problems and can safely manage your game with minimal problemsI have the retail version and have successfully modded my game and have seen no issues. However @Hishutup, who is the maintainer of the Mythic Dawn guide has the Steam version and always sees problems. So the choice is yours. There are many threads already started about specific mods and their installation so check those before you embark, but these two points are the primary consideration.

Nice additions guys. We might collectively get this beast tamed.

You probably already know of a a very annoying bug that renders the Bear Gear quest line broken, if not it's todo with the Clan Tuirsearch's Castle and a non-working switch to open the grill after you grab the diagrams from the chest. CDPR are apparently aware of it and looking at a fix, seriously how difficult can one switch be? Anyway, there is another bug that can be exploited to get out and I'll place the link here as I want to keep all my good gaming fixes in the same forum.

Today Microsoft installed a rather large update to my system and reinstalled all these apps back again. I simply redid all the steps again, some I had to do several times as the apps kept re-appearing in the Start Menu. Additionally some new apps can also be removed via the Control Panel, so you may also want to check what can be "fixed" there.

I may have confused you a little, sorry for that. I read your post and had in mind you're enquiring about the "Overwrite" folder, which is basically MO's temp folder. Where in fact you are enquiring about "overwriting" files in general, as you would see using any other mod manager. Hopefully @Greg's answer has steered you right. Perhaps watching some of the video tutorials will explain further about how MO does what it does.

That about sums it up.

MO guide chapter on "Overwrite".

Windows updating in the background most likely. Win10 is very heavy-handed with keeping everything the "Microsoft" way.

I always use "Custom" when it comes to installing software and the first thing I did was NOT install Gaming Evolved! I see no use for it with my system. The game specific settings as far as I can tell are just pre-made settings for the game that do exactly what we are already doing in the profiles, I could be wrong, but I doubt it.

Looks like AMD is ditching the AMD Catalyst Control Center in favour of its new app: Radeon Settings I'll look at how the settings differ compared to the two, but I'd say it's no more than a long overdue UI revamp. EDIT: Yep, just a radical UI update, no changes to settings as far as I can see.

The installation of the mods isn't as important as the order in the left-hand pane of MO, as any mod with the same filenames can be installed and placed accordingly to provide the game with the correct files. e.g. this mod provides the following files from the initial install of the "Texture 2" option: Warburg's 3D Paper World Map - Texture 2.ini (0 kb)Warburg's 3D Paper World Map - Texture 2.bsa (67016 kb)Warburg's 3D Paper World Map - Texture 2.esp (37 kb)Then the "beta Dragonborn - Addon" provides these files: Warburg's 3D Paper World Map - Dragonborn.bsa (12853 kb)Warburg's 3D Paper World Map - Dragonborn.esp (8 kb)Completely separate files so it will make no difference if these are merged into the first or not, for convenience sake they should be. The "Dawnguard - Addon" adds this file: warburg's 3d paper world map - dawnguard.esp (12 kb)Again, no conflict here, but easier to merge it into the first install. The "No Player Marked for Texture 2 - Addon" is a different matter as it has this file: Warburg's 3D Paper World Map - Texture 2.bsa (67016 kb)Clearly a different version of the original texture BSA and MUST be merged into the first install or, if you want to keep them separate, active in the left-hand pane with a higher priority, ie. lower in the window,, than the initial install. Assuming MO is handling your archives AND all of them are active (check the "Archives" tab) AND all the plugins are loaded there should be no issue. Extracting the BSAs will only be obscuring any LO issues that you might be having. Of course there might also be other issues at play here such as graphics drivers or ENB settings or such like, for the sake of this discussion I'm addressing only the mod in question.

There are two separate issues at play here: Where xEdit/MO place the edited ESM What does LOOT seeYou can if you wish clean your ESMs with xEdit from outide of MO so long as you end up with cleaned versions in a mod that can be enabled in MO and the original in Data so Steam doesn't complain. Either/or, your choice. The behaviour of xEdit/MO is somewhat flaky for different users hence the differing outcomes. As for LOOT not seeing them as cleaned. This indicates either an incorrect LOOT installation or the cleaned ESMs not being active in the VFS. LOOT should see exactly the same order of files as the game engine does when it is installed and run from MO.

No offence taken on my part, I simply mentioned it as a precautionary reminder. I got it very clear from posts that you own your copy, but Nexus have a "shoot first ask questions later" policy. I'm still a little uneasy about crackz, copying your game discs is a different matter entirely. When it comes to trouble-shooting game tools it is just another layer of pain to get through if the user is using a cracked copy of the game executable. It's hard enough getting three or four tools to play nice with one another without introducing a rogue element.

Either another process has one of the files open or a system thread is still running. Either reboot or grab a copy of Unlocker and kill it.

Wouldn't want to mention something like that on the Nexus, might get you an instant ban. "I used a fix so I wouldn't have to start steam" is another way of saying "crack", ie. a common way pirates supply games. Even if you own the game they are very touchy about such things. We're a little less trigger happy, but still frown on "crackz".

I'm not seeing any issues with the last version being run via MO.

ahh... that would also do the job. Why did I doubt you?

Welcome to STEP @Deadmano

Yeah, this is a good example of why conflict resolution isn't always straight forward. To answer your queries as best I can, this is what will happen in game. With your "bashed patch" loaded, #7, the records will match the vanilla game as shown in #1 and also #2. Removing your "bashed patch" will mean FWE and the WMK patch for FWE will be used and the RH Ironsights stuff will cause issues with some weapons. There is some further discussion around here about the Blackhawk and how to get "ironsights" for this weapon and it will show you that it is far from an easy task. As for the "Bash Tagger" script, the author had a run in with some people on Reddit and in a fit of frustration has removed all his code from the various places he had it hosted. Although while looking through the Bethesda forum today I did see him posting recently so maybe he will release it again, I wouldn't count on it though.

You might want to add a function that checks if spINI already has backed up copies of the INIs and if so it either asks to backup those or leave them alone. As a test I has my default INIs restored then ran spINI and "spINIified" them. Later I tried again and the backed up versions are now of the first run, meaning the default value INIs are lost. Not really an issue if you know that's what happens, as I did, I just made copies before I ran it a second time. Users that aren't as careful might find it odd though.

You probably have the "Hide no conflict rows" setting enabled. Invoke the context menu in the right-hand pane with a right-click and disable it.

The discussion is very clear in stating ALL the xEdit versions are fine to use, with the proviso that there are a lot of new records in the FO4 plugin structure that are uknown at this point and caution should be used. However ALL *snip versions suffer from an error in the way they save the data structure and are therefore always going to cause savegame corruption.

There are a couple of steps described in the wiki that need to be completed. You need to download not only the original file but also the FOMOD file and temporarily extract BOTH of them. Then move or copy the FOMOD folder into the folder structure of the Skyrim Redesigned mod. This the part where it mentions 34 individual folders instead of the original 33 from Skyrim Redesigned. What you should have now is a folder structure with Skyrim Redesigned as the top level and 34 folders underneath it including the fomod folder. Using whichever archiving tool you have, 7zip is a very good one to have, compress this folder structure and name accordingly. The wiki says to name that way because that naming convention allows MO to see the Nexus ID: Skyrim Redesigned-8954-1-0 and the version number: Skyrim Redesigned-8954-1-0 The actual process of naming the archive is handled by you using whichever tool you have.

There's a lively discussion over on the Bethesda forum about the use of the *Snip tool used by some authors to make their plugins. Basically a re-occurrence of the whole debacle with Skyrim mods early on before the Creation Kit and/or xEdit became available. Already a number of mods are being cited as causing savegame corruption and the authors are either washng their hands of the matter or saying they will redo it when the correct tools are available. So, basically anyone that installs a mod with a plugin should weigh up if they want to risk the dangers over the alleged benefits.