Announcement: Mod Organizer 1.3b (the b is for beta) and the future of MO - UPDATED 1.3.5 is out to the public

[Tannin]

UPDATE

 

New beta version 1.3.1 available on Sourceforge.

This should fix all reported problems. The only thing I couldn't make any sense of is the report of load order being reverted, could someone please work out reliable steps to reproduce it?

 

 

I just uploaded a beta of MO Version 1.3 to sourceforge: https://sourceforge.net/projects/modorganizer/files/?

 

Before I go into the changes, let me first advice against using this version as your primary installation. While it seems to be relatively stable and I've been using it on my own system for a few weeks now I will refuse to even feel bad if this ruins your setup.

Still, I would appreciate any feedback.

 

Right, features.

• Integration of loot 0.7 beta
• the integrated loot can now be updated without a new release of MO. (1)
• the mod list now has a new column that displays icons based on the content of the mod so you can quickly see if a mod contains, say, esps or textures or skse plugins or ...
• the mod list can be filtered by their content
• When you click a mod that has conflicts, the conflicting mods now get a colored highlight in the list.

Apart from this there have been a couple of changes under the hood:

• MO is now based on the current version of Qt (5.4 instead of 4.8). Unfortunately this also leads to a 4MB bigger archive.
• Windows XP is no longer supported.
• more game-specific functionality has been factored out into plugins. While this won't suffice to support non-gamebryo games right now it may be possible for someone (not me) to write a Morrowind plugin.

 

(1) To update loot, get the "loot api" download from the loot github page at https://github.com/loot/loot/releases/ and copy the loot32.dll contained within to the loot directory of MO.

 

---

 

Since I already have your attention I'd like to also announce that this is probably going to be the last feature-release of MO, at lease for a while.

This is not saying that I'll stop working on MO but the project has become too large for a single person to work on effectively in their very limit spare time and since it doesn't look like an active development community is forming around MO I decided to focus my time on very specific topics.

This will allow me to work on those things more effectively while allowing me to keep a shred of sanity.

 

So what I'll continue to do is:

• Fix bugs in the core application
• Fix severe bugs in the virtualisation library and plugins
• Add plugin interfaces on demand
• Work on a new virtualisation library that is more flexible and supports 64 bit
• Anything that I deem enjoyable. ;)

What I will no longer do is:

• Add any features (unless I deem the implementation fun)
• Answer any requests for help (be it PM, mail or on the forums) unless it's "I want to help out with MO but I need advice" or something like that
• Do the german translation
• Fix "minor" problems or "medium" problems in the vfs system and plugins
• Maintain "lists" like the categories mappings, configurator settings file,...
• Work on the tutorials in any way

 

The reason I will only fix severe bugs in the vfs library is that this lib will hopefully be replaced anyway when the new one is working.

The reason I will only fix severe bugs in the plugins is that I believe those plugins are sufficiently simple that others could easily work on those.

 

If you don't know, the features implemented in plugins is: all the installers, the tools below the "tools" menu, the diagnostic messages (exclamation mark) and now parts of the functionality specific to gamebryo games.

 

 

Known issues with MO 1.3 beta:

• right now filtering by the mod list by "checked, unchecked, update, ..." doesn't work.

[KeltecRFB]

Do not do a manual update from 1.3.0 to 1.3.1.   Do a complete uninstall of 1.3.0 and then install 1.3.1 but you can keep the profiles and mods folder.  If you try to do a manual update like we are use to, I found out that 1.3.0 files will be left behind and give the illusion that some bugs were already addressed.

[EssArrBee]

Do not do a manual update from 1.3.0 to 1.3.1. Do a complete uninstall of 1.3.0 and then install 1.3.1 but you can keep the profiles and mods folder. If you try to do a manual update like we are use to, I found out that 1.3.0 files will be left behind and give the illusion that some bugs were already addressed.

That's just good advice for all beta software.

[GrantSP]

As far as I can see the only unique file, ie. the only file that isn't in 1.3.1 and can't be overwritten, is proxy.dll.

 

Copying over every file and then deleting that file should be exactly the same as uninstall/install.

[GrantSP]

I have to say, 1.3.2 looks very, very good so far.

[EssArrBee]

I've been playing with it all day and really like it. It did have a few minor bugs that newbies might not know how to fix, but the new features are awesome. Really happy BSAs will never be a problem with Fallout ever again.

[Artorius]

I did a clean reinstall of version 1.3.2 after backing up my profiles and downloads and most things seem to work fine but after trying to run PerkusMaximus.jar (including having the argument -Xmx1024m -jar added to the argument line) and letting it go through the entire process it crashes without building the PerkusMaximus.esp and leaves the following error:

 

DEBUG (15:21:43.0268): createfile w: ..\..\PerMa_USKP master patch.esp -> C:\Games\Steam\steamapps\common\skyrim\Mod Organizer\mods\PerMa Compatibility and PaMa Patches\PerMa_USKP master patch.esp (80000000 - 3) = 00000EE0 (0)

DEBUG (15:21:46.0904): createfile w: Files\tmp.esp -> C:\games\steam\steamapps\common\skyrim\Mod Organizer\overwrite\SkyProc Patchers\T3nd0_PatchusMaximus\Files\tmp.esp (80000000 - 3) = 00000CB8 (0)

DEBUG (15:21:48.0156): add mod file C:\games\steam\steamapps\common\skyrim\Mod Organizer\overwrite\\SkyProc Patchers\T3nd0_PatchusMaximus\SkyProcDebug\Consistency\Conflict Pruning.txt (SkyProc Patchers\T3nd0_PatchusMaximus\SkyProcDebug\Consistency\Conflict Pruning.txt)

DEBUG (15:21:50.0251): move (ex) C:\Users\Jamie Atkinson\Documents\My Games\Skyrim\SkyProc\ConsistencyV3\PatchusMaximus.esp_ConsistencyTmp to C:\Users\Jamie Atkinson\Documents\My Games\Skyrim\SkyProc\ConsistencyV3\PatchusMaximus.esp_Consistency - 1 (183)

ERROR (15:21:50.0253): failed to remove virtual file PatchusMaximus.esp

DEBUG (15:21:50.0474): remove mod file C:\Games\Steam\steamapps\common\skyrim\data\PatchusMaximus.esp

DEBUG (15:21:50.0474): using path from previous deletion: \PatchusMaximus.esp

DEBUG (15:21:50.0474): remove mod file C:\Games\Steam\steamapps\common\skyrim\data\SkyProc Patchers\T3nd0_PatchusMaximus\Files\tmp.esp

DEBUG (15:21:50.0474): handle opened with backup semantics: ..\..\Skyrim.esm

DEBUG (15:21:50.0474): handle opened with backup semantics: ..\..\Update.esm

 

This worked fine when I used it with 1.2.18 earlier today.  Note that I don't think the plugin it brings up is important, it previously gave the same error with Enhanced Lights and FX,esp at the top ,so I deactivated that and all plugins that had it as a master, and it then failed again with that above error.

 

Someone else on the Nexus has also reported this same issue and has posted this error:

 

DEBUG (23:39:54.0010): createfile w: ..\..\Apocalypse - More Apocalypse - PerMa Compatibility Patch.esp -> C:\Mod Organizer\Skyrim\Mod Organizer\mods\Apocalypse - Magic of Skyrim\Apocalypse - More Apocalypse - PerMa Compatibility Patch.esp (80000000 - 3) = 00000C78 (0)

DEBUG (23:39:58.0506): createfile w: Files\tmp.esp -> C:\Mod Organizer\Skyrim\Mod Organizer\overwrite\SkyProc Patchers\T3nd0_PatchusMaximus\Files\tmp.esp (80000000 - 3) = 00000958 (0)
DEBUG (23:39:59.0687): add mod file C:\Mod Organizer\Skyrim\Mod Organizer\overwrite\\SkyProc Patchers\T3nd0_PatchusMaximus\SkyProcDebug\Consistency\Conflict Pruning.txt (SkyProc Patchers\T3nd0_PatchusMaximus\SkyProcDebug\Consistency\Conflict Pruning.txt)
DEBUG (23:40:04.0254): move (ex) C:\Users\Sevrick\Documents\My Games\Skyrim\SkyProc\ConsistencyV3\PatchusMaximus.esp_ConsistencyTmp to C:\Users\Sevrick\Documents\My Games\Skyrim\SkyProc\ConsistencyV3\PatchusMaximus.esp_Consistency - 1 (183)
ERROR (23:40:04.0256): failed to remove virtual file PatchusMaximus.esp
DEBUG (23:40:04.0291): remove mod file C:\Program Files (x86)\Steam\steamapps\common\Skyrim\data\PatchusMaximus.esp
DEBUG (23:40:04.0291): using path from previous deletion: \PatchusMaximus.esp
DEBUG (23:40:04.0291): remove mod file C:\Program Files (x86)\Steam\steamapps\common\Skyrim\data\SkyProc Patchers\T3nd0_PatchusMaximus\Files\tmp.esp
DEBUG (23:40:04.0291): handle opened with backup semantics: ..\..\Skyrim.esm
DEBUG (23:40:04.0291): handle opened with backup semantics: ..\..\Update.esm

Edited March 19, 2015 by Artorius

[MosAnted]

Bug report: Just upgraded from 1.2.18 to 1.3.2, whenever I try to use the "search by name" function on the left pane, MO crashes.

[pStyl3]

Edit:

 

Didn't know that you can post comments on closed issues on the bug genie .. I posted a new comment here. It seems that 1.3.2 did not fix the issue with TES4Edit being unable to load .bsa files if run through Oblivion-MO.

Edited March 21, 2015 by pStyl3

[GrantSP]

Sorry, I can't replicate that error. All bsas get loaded just fine for me and no crash with either xEdit or MO.

[pStyl3]

Thank you for trying to help out. I have written another reply.

 

And I noticed .. this can probably be closed now, right?

[GrantSP]

I closed the issue about LOOT integration but I'll let Tannin decide on the status of the bsa issue.

[hellanios]

is it safe to upgrade from 1.2.18 to the new version on an existing profile?

[GSDFan]

is it safe to upgrade from 1.2.18 to the new version on an existing profile?

You should only upgrade to v1.3.x if you want to participate in bug / trouble shooting.

[EssArrBee]

Looks like 1.3.5 is a pretty substantial update.

Version 1.3.5
- If there are no Missing ESPs, say "None" rather than leaving an empty list. 
- Allow very long filenames to be used when unpacking 
- Allow drag-and-drop into the download tab (files or urls but does not support any log-in for urls) 
- backup-checkbox now remembers its state 
- esp list refresh is now delayed if the directory-structure is being updated. This may have been causing the lists to be cleared. 
- language list in settings no longer contains english twice 
- language names in settings are now in the native language 
- Added settings-tab to allow saving of steam username and password 
- warning when ambiguous files are detected in an fomod install 
- workaround to prevent repeated checking of mods with the mouse was interpreted as double click 
- extended plugin interface. Plugins can now activate/deactivate mods, install mods suggesting a name and retrieve a list of all installed mods 
- reduced number of mods for which update information is requested at once 
- added theme inspired by JetBrains Dracula (created by Kojoley on github) 
- bugfix: MO requested update information for mods without mod-id 
- bugfix: Sort equal priority mods by order in xml file 
- bugfix: detection of loot as the registry key doesn't include the executable 
- bugfix: moving a mod didn't properly update conflict highlighting 
- bugfix: upon closing the profiles dialog, the profile was changed to the top-most profile and back 
- bugfix: archive invalidation wasn't correctly enabled/disabled 
- bugfix: case conversion could produce different local-dependent results between the time the vfs lookup map is set up and later when querying it. 
- bugfix: shortcuts specifying a profile didn't work

I can't highlight the ones I like, but seems that all this stuff is quite useful and it didn't seems to mention adding some more stuff for plugin support.

[Neovalen]

Looks like 1.3.5 is a pretty substantial update.

Version 1.3.5
- If there are no Missing ESPs, say "None" rather than leaving an empty list. 
- Allow very long filenames to be used when unpacking 
- Allow drag-and-drop into the download tab (files or urls but does not support any log-in for urls) 
- backup-checkbox now remembers its state 
- esp list refresh is now delayed if the directory-structure is being updated. This may have been causing the lists to be cleared. 
- language list in settings no longer contains english twice 
- language names in settings are now in the native language 
- Added settings-tab to allow saving of steam username and password 
- warning when ambiguous files are detected in an fomod install 
- workaround to prevent repeated checking of mods with the mouse was interpreted as double click 
- extended plugin interface. Plugins can now activate/deactivate mods, install mods suggesting a name and retrieve a list of all installed mods 
- reduced number of mods for which update information is requested at once 
- added theme inspired by JetBrains Dracula (created by Kojoley on github) 
- bugfix: MO requested update information for mods without mod-id 
- bugfix: Sort equal priority mods by order in xml file 
- bugfix: detection of loot as the registry key doesn't include the executable 
- bugfix: moving a mod didn't properly update conflict highlighting 
- bugfix: upon closing the profiles dialog, the profile was changed to the top-most profile and back 
- bugfix: archive invalidation wasn't correctly enabled/disabled 
- bugfix: case conversion could produce different local-dependent results between the time the vfs lookup map is set up and later when querying it. 
- bugfix: shortcuts specifying a profile didn't work

I highlighted the ones I really liked, but seems that all this stuff is quite useful and it didn't seems to mention adding some more stuff for plugin support.

Did you miss...

 

 

 

- extended plugin interface. Plugins can now activate/deactivate mods, install mods suggesting a name and retrieve a list of all installed mods