GrantSP

See this thread.

The basic rule of load order is: if you don't trust what LOOT gives you, check it in xEdit and see if there are conflicts. There are simply too many variables to be able to provide a definitive list of what should be before what else, that's why even with all the reports to LOOT and the constantly updated 'masterlist.yaml', there is still a need to make your edits which end up in your own 'userlist.yaml'.

The issue isn't so much a MO one as a Nexus server one. As noted in the MO forum, here and in Nexus, the files in the FULL install have been updated to include the correct 'hook.dll' but, and this is the important part, the server that is assigned to you for that download may not yet have that file updated. The quick fix is to grab the 1.3.5 to 1.3.6 UPDATE file and install that. It is because @Tannin chose to not update the version number for the minor file update (hook.dll went from 2.7.4 to 2.7.5) so as far as the servers are concerned there is no rush in propagating the same versioned file around the internet.

According to that screengrab, you only have the original vanilla plugins loaded! What are you expecting to see in LOOT? LOOT will only sort the list of plugins you provide it with, in your case, nothing is added. Unrelated, but you don't need the HiRes plugins to load, disable them and have MO manage the BSAs by itself, and then sort the left hand pane to have them load after the other unmanaged data.

I think I will upgrade when possible, the next big decision then will be whether to ditch Chrome and go with their fancy new 'Spartan' or 'Edge' or whatever it is they will call it. Just from a few preview videos and reading the blurb it looks a good option.

Ok, so in what way is the 'Sort' not working? There should a series of log files generated in the 'logs' folder, could you either post them here in spoiler tags or provide a link to an online hosting service like PasteBin?

Just to clarify when you say "LOOT", you do mean the standalone tool run from inside MO, not the 'Sort' button in MO's UI? If that is the case then I would say you have a broken LOOT install. Additionally if you are getting messages about missing Qt files then I think you may have also broken your MO install. Best thing to do is open explorer to your MO folder and delete everything except the folders: profiles, mods & downloads and the modorganizer.ini and categories.dat (if you have one) and with a brand new FULL MO install archive copy the contents from that archive back into the now-cleaned MO folder. Sometimes files from previous versions get orphaned and make calls that aren't needed. It may also be the case that you have some other software on your system that is interfering with the Qt files, but let's tackle that only if the fresh installs don't work.

Very interesting, and alarming. Thank you for the links.

What about 7zip doesn't work? That's a fairly important tool in anyone's system. Is it just the UI part because if it is the actual archive code that would impact on other tools like MO which use their library? Visual Studio issues may be a pain. I've only now just got my coding tools re-installed and have been messing around with some projects, god I hate coding, I now remember why I keep quitting! Still, I want to try and get some of the code in the MO project compiling on my system to see what, if anything, I can do.

As of today I now have a small notification in my taskbar from Microsoft advising me of their next OS and offering it to me for free. Going by past records this OS is most likely to fall into Microsoft's 'good' releases, historically they tended to go in a regular: good -- bad -- good -- bad -- good, with Win7, which I currently have, being 'good' and Win8/Win8.1 being 'bad'. Is that how you users have seen it? Those with Win8/8.1 and perhaps those with pre-release versions of Win10. My laptop is more than capable of using it apparently so I am considering it, but since I use it primarily for gaming, or gaming related activities, I'd like to know of any pitfalls or oddities that may arise. Any ideas as to the pros/cons of this OS upgrade?

I just meant that the 'Start In' field actually had something in it. Not that it should make a difference, but it can't hurt to try things, we've lucked out on just about every other method! :confused: Sorry to say it, but I'm out of ideas.

The first listed file under the "UPDATES" heading. The one marked: "Mod Organizer v1_3_6 update -- updates version 1.3.5 to 1.3.6" However, you and I are probably both non-Premium members, and the servers assigned to us are not updated as quickly as those with Premium accounts. @Tannin has stated that the updated files ARE in the FULL install files, they just haven't been propagated to all the servers yet, so you may find that the correct files are actually in those downloads if you grab them at a later date. This appears to be one of those Nexus oddities and not an issue with @Tannin's updating methods.

Well if that is the case (I have no reason to doubt you) then there is a horrendous delay in Nexus' updating of ALL their CDN servers. As mentioned elsewhere, I downloaded the 1.3.6 version a good 6-8 hours after the first posting in Nexus of that issue. I tried again earlier today and the same files are being offered as the 1.3.6 version. That 'hook.dll' version 2.7.4 was still in the archive as of just a few hours ago. I understand your reasoning on version numbers, I just don't think it is a helpful stance. However it's not a position I want to take a stand on, I'm not providing any code fixes so my stance is not worth anything!

There is still a need to grab the UPDATE file from Nexus. Even though you have 1.3.6 installed there are 'updated' files in the 1.3.5 -- 1.3.6 Update file that will solve this Java issue. The specific file that is needed is the 'hook.dll'. The version of this file in the FULL 1.3.6 files is 2.7.4. The version in the UPDATE file is 2.7.5 and this is needed. Better version numbering would aleviate this situation and I have left a comment in the Bug Genie stating as much. Version numbers don't cost anything so there is no need to avoid using 1.3.6.1 if this a minor incremental update.

Backup 'mods','downloads' & 'profiles' folders as well as the modorganizer.ini and delete everything else. Install the FULL 1.3.6 archive version by opening it and copy everyting in that archive into the now clean MO folder. The 'hook.dll' file inside this archive (2.7.4) is not the latest version (2.7.5), so grab the UPDATE file and install it's contents over the files in the MO installation. You should now have a perfectly working MO install.

These tools, and the Skyrim equivalent, can be run through MO, however it involves changing the tool's settings for every profile you have. As they only look to one location for the INI files, you can change it to see your current profile's INIs but as soon as you change profiles, you will need to change the setting again, and again, and again. Very tiresome.

The latest LOOT from GitHub is fine. @WrinklyNinja spent a great deal of time with 0.7 in beta before releasing it as a final version.

Then the issue isn't with MO not supplying LOOT with the correct details, it is a case of a broken LOOT install. Running LOOT by itself will show the 'vanilla' plugins regardless of which manager you use to manage mods. Since this isn't happening we must conclude LOOT isn't set up correctly. Remove the LOOT folder from it's installation folder, or if you used the installer version, run the Uninstall routine. Ensure the settings in you 'Local user AppData' folder is cleared. C:\Users\<UserName>\AppData\Local\LOOT\Skyrim This shouldn't strictly be necessary but just in case there are leftovers from previous installs that might be messing with LOOT.

'Vanilla'. As in the plugins that are supplied with the game. No other plugins installed in the Data folder.

Yeah, it is very confusing. "Which version or MO are you using? Oh... well it will look like this. If another version then it will look like that."

When you run LOOT by itself, ie. not from MO, does it start with a blank screen or does it show only the vanilla plugins?

I usually set this in the 'Arguments' field so that regardless of which game LOOT may have previously worked on, assuming you use it for more than just Skyrim, it always opens in MO set to work on the correct game. --game=SkyrimBut, regardless of that setting, do you see that issue only after MO was started from initiating a download from Nexus with the 'Download with Manager' button? Starting MO from the desktop usually avoids that problem.

A mystery indeed! What happens when you assign a working directory to the FOSE settings in MO and also set it to close on launch?

When you open the 'Profile Manager' and select any of the profiles you have made, the option at the bottom of that window about "Archive Invalidation" applies to that profile. Checking the box applies these changes: bInvalidateOlderFiles is changed from 0 to 1 SInvalidationFile changed from ArchiveInvalidation.txt to nothingand unchecking it reverts them.

There appears to be a slight change to way MO handles the 'vanilla' plugins in the later versions. In previous versions, those used when the wiki was prepared, the ESMs 'were' in fact updated into the 'Data' folder AND backups were placed into the 'Overwrite' folder. Now it appears the ESMs are edited and MOVED into the 'Overwrite' folder along with their backups. This means you will need to either move them back into the 'Data' folder or create new mods using the method described above. Personally I see no problem with moving them back into the 'Data' folder. Additionally, I believe with later versions of xEdit (TES5Edit), the need to perform the 2nd clean on Dawnguard is not needed anymore.