Jump to content


Photo

No mods showing in Loot

mo2 loot mods

  • Please log in to reply
36 replies to this topic

#16 cptmcsplody

cptmcsplody

    Prisoner

  • Members
  • 25 posts

Posted 14 April 2017 - 01:51 PM

can you check if copying your plugin list from your mod organizer profile to the SSE app data plugin file without the dlc fixes the issue.

 

This mod explains it better http://www.nexusmods...ion/mods/2827/?


Edited by cptmcsplody, 14 April 2017 - 02:02 PM.

  • 0

#17 TorNyan

TorNyan

    Citizen

  • Members
  • Pip
  • 74 posts

Posted 14 April 2017 - 03:28 PM


That plugin is not necessary if you use @LePresidente's fork of MO2. My advice is to remove your current install and use just that fork.

Come to think of it... I am not actually using that plugin anymore. I did not realize LePresidente's upload was a fork, but I am using that fork. I previously used the Tannin's beta 3 v2.0.7 along with the SkyrimSE plugin that I linked before, but uninstalled it since I had problems (the same problem as now + nxm links not working with Special Edition). Sorry for the confusion.

I use LOOT (current version) v0.10.3 and the xEdits are v3.2 (current version). I have tried LOOT v0.10.2, v0.10.1, v0.10.0, v0.9.2.0, v0.8.1, v0.7.1, v0.6.1. I have tried installing LOOT and Mod Organizer to the default folders, and also to (subfolders in) the Skyrim folder.

I now tried using v1.3.11 (latest Tannin version) to manage original Skyrim, which posed the same issue (I only tried LOOT though, not TES5Edit). The same issue is prevalent with v2.0.7 (current LePresidente version) with original Skyrim too (not just Special Edition). For each install I deleted the ModOrganizer main directory and ModOrganizer local appdata directory, and I added the command line argument in MO for LOOT that you suggested.

The combination of Mod Organizer v1.2.14 (older version) and LOOT v0.6.1 (latest version before the material design) does work! However nxm links does not work (though not the same issue as with Tannin's MO beta 3 + TESVSE plugin). And of course, this is not a solution for Special Edition.
The combination Mod Organizer v1.2.14 and LOOT (current version) v0.10.3 does not work.

I have launched both Skyrim and Skyrim Special Edition from Steam, opened the options in the launcher, loading the game up and loading a save file. I also ran LOOT and xEdit outside Mod Organizer. Installing a plugin manually into the data folder and running LOOT and TES5Edit without Mod Organizer does work. I have also tried re-installing LOOT and the xEdits. I have tried restarting the computer.

Steam is running when Mod Organizer is started.

I have tried closing all background applications etc.

This is a fairly fresh Windows installation.


  • 0

#18 TorNyan

TorNyan

    Citizen

  • Members
  • Pip
  • 74 posts

Posted 14 April 2017 - 04:00 PM

I now tried uninstalling original Skyrim ("Oldrim") to see if the problem was related to having both original and Special Edition installed. It did not help.

 

can you check if copying your plugin list from your mod organizer profile to the SSE app data plugin file without the dlc fixes the issue.

 

This mod explains it better http://www.nexusmods...ion/mods/2827/?

For me, since the issue is not specific to Special Edition, I do not think this is related. The batch file you linked deletes and creates a new plugin.txt file in %localappdata%\Skyrim Special Edition. But I do not have a plugin.txt file there (though the batch creates one). I think maybe that is only if you use Steam Workshop mods? Either way, it did not solve my problem. But thank you.


Edited by TorNyan, 14 April 2017 - 04:14 PM.

  • 0

#19 TorNyan

TorNyan

    Citizen

  • Members
  • Pip
  • 74 posts

Posted 14 April 2017 - 04:36 PM

Oh, and I have tried enabling windows 8 compatibility mode and to run as administrator for ModOrganizer.exe and LOOT.exe (reverting it afterwards).


  • 0

#20 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,833 posts

Posted 14 April 2017 - 06:09 PM

Just to get things clear, MO/MO2 is handling your installed mods properly, you're just not seeing LOOT function correctly?

 

Could you post your modlist and also a screenshot of LOOT please?



#21 TorNyan

TorNyan

    Citizen

  • Members
  • Pip
  • 74 posts

Posted 15 April 2017 - 10:21 AM

Yes. The ESP plugins that are activated in Mod Organizer does not show up in LOOT nor xEdit, but they work in-game. But it is not simply a LOOT problem, because when I tried installing a plugin manually by extracting it to the data folder and running LOOT outside Mod Organizer, that worked. The mods from Mod Organizer does not get loaded into LOOT, it seems. Like maybe it is a bug with the virtual folder system? But then again, it works with SSE and the Creation Kit but not with LOOT and xEdit. When launching Skyrim Special Edition from Mod Organizer and clicking Mods and then Load Order from the title screen menu, my mods are all there.

 

When launching LOOT from Mod Organizer, the text "MO is locked while executable is running." appears briefly and disappears as soon as LOOT is started.

The sort function in Mod Organizer does work.

Other things that I have tried:
I have tried deleting the LOOT and xEdit executables from Mod Organizer and adding it again.

I have tried using the "--single-process" argument for LOOT in Mod Organizer.

I have tried setting full control permissions to users and authenticated users for ModOrganizer and LOOT folders including their local appdata folders.

 

Screenshot of Mod Organizer, and LOOT run through Mod Organizer

 

Screenshot of Mod Organizer, and SSEEdit run through Mod Organizer

%localappdata%\LOOT\CEFDebugLog.txt



%localappdata%\LOOT\LOOTDebugLog.txt


%localappdata%\LOOT\settings.yaml


SSEEdit_log.txt


Edited by TorNyan, 15 April 2017 - 10:36 AM.

  • 0

#22 cptmcsplody

cptmcsplody

    Prisoner

  • Members
  • 25 posts

Posted 15 April 2017 - 10:45 AM

see this https://github.com/l...loot/issues/567


  • 0

#23 TorNyan

TorNyan

    Citizen

  • Members
  • Pip
  • 74 posts

Posted 15 April 2017 - 03:41 PM

 

Thanks. Deleting the LOOT local appdata folder did not solve my problem. If i delete settings.yaml, it is re-created when I run LOOT.


Edited by TorNyan, 15 April 2017 - 03:42 PM.

  • 0

#24 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,833 posts

Posted 15 April 2017 - 06:53 PM

I'm not sure what is going wrong with your install, try using these settings for LOOT and xEdit.

 

I've created a separate folder away from Steam and my games where I place all my tools: D:\Games\Utils\ Under which I install LOOT, in a folder called LOOT and one copy of xEdit in a folder called xEdit.

 

In my Skyrim Special Edition instance of MO2 I have those tools with the following arguments for LOOT and xEdit:

"--game=Skyrim Special Edition"

-sse

 

In my Skyrim instance they are:

--game=Skyrim

-tes5

 

After changing your settings to these, please run MO2 for Skyrim and start both LOOT and xEdit and then paste the contents of the "logs" folder here. Change to Skyrim Special Edition and paste those logs also.

nb. The logs folders are under your main MO2 folder in %appdata% and there should be separate folders for each game. Each folder should have at least 2 logs.



#25 LePresidente

LePresidente

    Prisoner

  • Mod Authors
  • 33 posts

Posted 16 April 2017 - 01:37 AM

Make sure both the following files are in the MO2 install folder. 

 

  1. usvfs_proxy.exe
  2. usvfs_x86.dll

Those two are what handles loot and any x86 application to see the virtual filesystem, I have been seeing a few reports of AV's killing it


  • 0

#26 MaximilianPs

MaximilianPs

    Prisoner

  • Members
  • 34 posts

Posted 08 August 2017 - 06:07 PM

I've the same problem, and the same is for Wrye Bash and SSEEdit, none of that can see any .esp but Skyrim, Update, Dawnguard, Heartfire and Dragonborn.

What I notice is that MO (2.0.8.3) won't keep his application locked as usual, just after a second the "Mo is locked while the executable is running." small window dissapear!

I guess the issue is linked to this behaviour in some ways.


Edited by MaximilianPs, 08 August 2017 - 06:08 PM.

  • 0

#27 MaximilianPs

MaximilianPs

    Prisoner

  • Members
  • 34 posts

Posted 09 August 2017 - 03:39 PM

Ok I've installed MO 2.0.8.3B but the problem still present !  :crying:


  • 0

#28 Greg

Greg

    High King

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,437 posts

Posted 09 August 2017 - 06:36 PM

If you are on Windows 10 and have installed the 4GB VRAM patch from the Insider Updates, this apparently bundles some other patches that breaks Mod Organizer's virtual file system.



#29 MaximilianPs

MaximilianPs

    Prisoner

  • Members
  • 34 posts

Posted 10 August 2017 - 09:01 AM

I've Windows 10 x64 with a 16GB DDR3 and a 1080 with 16GB VRAM, but I'm not an insider so maybe it didn't install the patch?...

Any workaround to fix it BTW?


Edited by MaximilianPs, 10 August 2017 - 09:04 AM.

  • 0

#30 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 3,833 posts

Posted 10 August 2017 - 04:39 PM

Regarding the Creator update that breaks things (thanks Microsoft ;{), please follow the link in my signature about tricky software and follow the steps to disable the Game Bar and let us know if that was/is the culprit.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users