MO 1.2.x beta testing

[Tannin]

I just uploaded MO 1.2.2 which supports the feature TheBloke proposed. Right now it's only on sourceforge because I'd like to hear your opinions first:Installer: https://sourceforge.net/projects/modorganizer/files/ModOrganizer-1.2.2.exe/downloadArchive: https://sourceforge.net/projects/modorganizer/files/ModOrganizer_v1.2.2.7z/downloadPlease note that the tutorial is a bit broken currently, but you don't need that, right? ;)

[z929669]

Awesome. I will try it out when I can ... in the process of selling/buying homes, so I am not spending much time at the keyboard anywhere but at work ...

 

I am anxious to hear input from TheBloke, Keith, Neo and the STEP team though.

[Neovalen]

Will check it out sometime soon. Out on the town ATM :)

[keithinhanoi]

I'll check tomorrow, as it's way too late here already!

[EssArrBee]

I'll cehck it out right now. Is it only an update to the BSA handling or is there anything else we should look at?

[Neovalen]

Does this look like what we'd expect to load? Keep in mind all my files are loose, no BSAs besides the vanilla ones and I dont use the HRDLC esps. Archives tab has all BSAs checked and managed by MO.

 

[EssArrBee]

Okay, so a few things before I get to BSAs.

• The little drop down on next to profiles bar is cool.
• The fix mod order function is nice, but didn't work 100%. Still had to move a couple things manually.
• All my mods were reset and unchecked after install.
• MO starts up faster and Skyrim loads up faster than 1.2.0 or 1.2.1.
• The lightbulb Flag is much easier to read than before.

So the BSA handling:

• When I started MO Hearthfire was detected and put at priority 0, but Dragonborn and Dawnguard were at the bottom of my install list.
• When I moved Dawnguard to the top, I couldn't put USKP or my Optimized textures before Dawnguard using drag and drop. All three files just had priority 0, so I had to manually type in the priority, but after that everything was fine.
• I guess if we have the check box on the archive tab ticked that all BSAs are greyed out unless they are loaded with a dummy plugin. That seems like a good idea to me, tie loading to install order not plugin order.
• The bug where BSAs would retick themselves after swithcing tabs is gone.

[Neovalen]

Since ESS has left some feedback here is my experience:

 

Installed MO 1.2.2 using the installer on top of 1.2.1, my load order / activation states remained intact. New mods for the DLCs were added at the top of the load order. without issue and I had no issues dragging and dropping anything.

I do have a light bulbs for "Potential Mod Order Problem" and "You have files in your overwrite" but I know all the conflicts in my setup and know there is nothing wrong. These were unchanged from last version but figured I'd mention it anyways.

 

I could not open the conflicts tab for the "fake" mods but I did see them listed in the other mods conflict tab and all appears properly as I would expect. Starting time and Loading times appeared reduced but could be "placebo effect".

 

Reference: Windows 8.1 with default theme and using Dark.qss for MO.

[DoubleYou]

One bug I'm finding: If the first mod in priority 0 is contains only a BSA and no corresponding plugin, that BSA is being loaded first and overwritten by everything. For instance, I have my Skyrim optimized textures in a BSA mod without a plugin at priority 0. Beginning of Archives.txt looks like this:

 

STD.bsa

Skyrim - Animations.bsa

Skyrim - Interface.bsa

Skyrim - Meshes.bsa

Skyrim - Misc.bsa

Skyrim - Shaders.bsa

Skyrim - Sounds.bsa

Skyrim - Textures.bsa

Skyrim - Voices.bsa

Skyrim - VoicesExtra.bsa

STD.bsa is my optimized textures. Of course, with this order, they will be completely overridden. If I move it to priority 1, it is fine. If I move Unofficial Skyrim Patch to priority 0, it is fine.

[DocClox]

I still can't run Bodyslide. It warns me about process elevation, starts a new MO instance, shows me the logo and then ... nothing. There's a MO process in the background doing something, but I never get the bodyslide app launched.

 

It's not just bodyslide either, (assuming it follows 1.2.1) but that's the case that stops me migrating from the last stable.

 

[edit]

 

I should add: apart from that, it looks fantastic.

Edited June 6, 2014 by DocClox

[EssArrBee]

I'm not having DY's problem, but I did load up Fallout New Vegas and it seemed to work well for that game too. I have a bunch of mods that I have to install right to the DATA folder because I couldn't get the GECK to launch with MO and it detected all those mods and put them into folders at the top of mod list.

 

The one weird thing was that there was also a folder called FalloutNV, so it may be detecting some of the game files as DLC or something.

[DoubleYou]

@DocClox

Bodyslide loads up fine for me. Try running Mod Organizer as administrator and then running Bodyslide. Also ensure that Bodyslide is checked in the Left Pane.

[DocClox]

Hmm... I haven't tried running MO as admin; I thought one of the basic principles of MO as that you shouldn't need to run it with admin rights. I'm sure I saw Tannin say as much on this forum.

That said, I'll take any workaround. Especially if it works with FNIS as well (which has just failed to start from MO for me with 1.2.2)

[edit]

I can confirm, bodyslide does work if you run MO as admin. Still think it's a bug though,

[edit]

FNIS however won't start at all, even with admin rights.

[edit]
 

NVM - Old profile, new version of FNIS - no exe found. Old news.

 

Point stands about not needing to run MO as admin, however.

Edited June 6, 2014 by DocClox

[Neovalen]

Normally you don't to run MO but if client program needs it then you need to.

[keithinhanoi]

I decided to try installing 1.2.2 as a "new" user.
 
TEST RUN #1
 
I moved my MO 1.1.2 install directory out of /Skyrim, and dropped the MO 1.2.2 folder from the .7z install archive right inside my /Skyrim install directory.
 
It recognized the 3 DLCs, added them to the mod priority list in the correct order (DG, HF, then DB -- I don't have the HR-DLC installed).
 
However, the plugins were not enabled - and they were listed in the wrong order (DG, DB, then HF). Nevertheless, I enabled the plugins in the Plugin tab. Also, in the Archives tab, Dawnguard.bsa was listed under data, while the HearthFires and Dragonborn BSAs were listed under their own separate headings. 
 
I thought this might be happening because this new version of MO adds the DG pseudo-mod with priority 0, and to check on this theory, I tried moving HF up above DG in the left-hand mod priority pane, but this only resulted in HF being assigned priority 0 as well as DG. 
 
After this happened, I clicked Refresh in the Data tab of the right-hand pane, and immediately the warning icon lit up. The warning listed was PMOP with a recommendation to "Move HearthFires after Dragonborn". I did not try using the beta "Fix" feature.
 
Checking back in the Archives tab, I found that now it did not match the mod priority of 0 assigned to both DG & HF. So my theory might be wrong, but it seems that since MO associates priority 0 with /data in the Archives tab, perhaps the new DLC pseudo-mod feature should assign them starting with a Priority value of 1 for DG?
 
Just to see what would happen, I manually moved HF below DB in the left-hand mod priority pane, and clicked Refresh in the Data tab. HF remained in place with priority 0, still above DB, but DB now had a priority value of 2! Even stranger, in the Archives tab, only DG was still listed under data, while then HF and DB were under separate headings (in that order.) So it appears the priority value assignment and ordering isn't working quite right yet.
 
Then I deleted the MO 1.2.2 folder entirely, and started over again to test plugin sorting (since as mentioned above, they started off in the incorrect order).
 
TEST RUN #2
 
Again the DLCs were recognized, added as priority 0, 1, 2 for DG, HF, DB but with the plugin load order as DG, DB, HF (all 3 disabled). So I enabled them as in test #1.
 
When I clicked Sort under the Plugins tab, MO downloaded the LOOT masterlist, etc., fine, and the built-in browser window popped up with the LOOT Report. Checking in the Details tab of the report, it listed the DLC plugins in the expected correct load order of Skyrim.esm, Update.esm,  DG, HF, and then DB.
 
But then when I closed the LOOT report window, the load order in the Plugins tab remained unchanged (Skyrim, Update, DG, DB and then HF). I'm afraid that since I haven't used either of the MO 1.2.x betas before this 1.2.2 test, I'm not sure if I've missed a step to get LOOT to order things correctly - but nonetheless, in the "new" user context, this is what I'm seeing, and it would be unexpected behavior.
 
I also noted that after using the built-in LOOT Sort feature, the warning icon lit up, this time with a log-based error, as follows:
 

INFO (11:16:15.0540): no ini tweaks file
INFO (11:16:15.0540): data path is D:SteamLibrarySteamAppscommonskyrimdata
DEBUG (11:16:15.0540): mods are in "D:SteamLibrarySteamAppscommonskyrimModOrganizermods"
DEBUG (11:16:15.0589): data path: D:SteamLibrarySteamAppscommonskyrimdata
ERROR (11:16:15.0589): archive "D:SteamLibrarySteamAppscommonskyrimModOrganizerprofilesDefaultarchives.txt" not found!
ERROR (11:16:15.0597): failed to set up list of bsas
----------- LOG END -----------

 
Looking through the Settings menu, I noticed that a "Display mods installed outside MO" option has been added, but when I disabled this option, all the DLCS remained listed in the mod priority pane, and with no changes in the Archives tab. So, it seems that option hasn't been implemented yet.
 
At this point I'm stopping, because with the idiosyncrasies with the Priority value assignment to just the 3 DLCs, it doesn't make any sense to see what happens if I install the Unofficial Patch mods and try to order them between the DLCs.
 
I've posted up the two MO debug level log files for my two test runs on pastebin.com here (#1) and here (#2).
 
Please let me know if you want me to try any further tests.

 
PS., Shouldn't we start a new thread for test reporting on this MO 1.2.2 beta????

[DoubleYou]

@Keith

Priority number 0 is bugged atm. Place Distant Decal Fix there, as it needs to be before USKP anyway.

 

Split topic to new thread.

 

@EssArrBee

It doesn't show up in the gui.

 

@Neovalen and everyone

 

Order for High Res DLC  and optimized versions in left pane should be:

 

HighResTexturePack01

HighResTexturePack02

HighResTexturePack03

HRDLC1 Optimized

HRDLC2 Optimized

HRDLC3 Optimized

 

NOT:

 

HighResTexturePack01

HRDLC1 Optimized

HighResTexturePack02

HRDLC2 Optimized

HighResTexturePack03

HRDLC3 Optimized

 

This is due to the fact that Bethesda accidentally duplicated two files (textures/effects/gradients/gradsprigganvariant.dds and textures/effects/fxglowspotlinearalpha.dds) from HighResTexturePack01 into HighResTexturePack02.