Jump to content


Photo

Mods will not show up in LOOT or SSEEdit. (Run through MO2)


Best Answer GrantSP , 06 January 2018 - 02:04 AM

You're using MO 2.0.7. Update to the latest 2.1.1 release and see if the issue persists.

Go to the full post


  • Please log in to reply
7 replies to this topic

#1 ryanak

ryanak

    Prisoner

  • Members
  • 3 posts

Posted 05 January 2018 - 09:04 PM

My mods are working in game when I run it through MO2, however, they do not appear in LOOT or SSEEdit, only the Skyrim.esm, Update.esm, Dawnguard.esm, HearthFires.esm, and Dragonborn.esm appear in each. I have set up the executables for both LOOT and SSEEdit in MO2. I have tried adding arguments in the ModOrganizer.ini file, but they just disappear when I run LOOT through MO2. I saw somewhere that Windows GameBar may be the problem, but disabling that did not help either. Any ideas about what my issue may be?


  • 0

#2 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 05 January 2018 - 09:17 PM

Post your INI and the logs from the last time you ran those tools.

 

Be sure to use spoiler tags for long posts or use a service like PasteBin.



#3 ryanak

ryanak

    Prisoner

  • Members
  • 3 posts

Posted 06 January 2018 - 01:15 AM

ModOrganizer.ini
 
 
I tried a fresh install of Skyrim SE, MO2, LOOT, and SSEEdit. Still having the same problems.

Attached Files


  • 0

#4 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 06 January 2018 - 02:04 AM   Best Answer

You're using MO 2.0.7. Update to the latest 2.1.1 release and see if the issue persists.



#5 ryanak

ryanak

    Prisoner

  • Members
  • 3 posts

Posted 06 January 2018 - 04:39 AM

That worked, thank you. I was using a tutorial from somewhere and was linked to an older version I guess. I'm dumb.


  • 0

#6 Kelryth

Kelryth

    Prisoner

  • Members
  • 5 posts

Posted 02 June 2018 - 01:55 AM

I have this same issue playing Fallout 4:

 

Log: usvfs-2018-06-02_06-45-11.log

 

ModOrganizer.ini


  • 0

#7 Greg

Greg

    Dragonborn

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1,777 posts

Posted 02 June 2018 - 08:26 AM

This isn't a debug log so it doesn't really provide any information to go on. You'll need to open the Settings dialog (the screwdriver and wrench icon at the top), click the Diagnostics tab, and change Log level to Debug. You should delete all the log files first before running Mod Organizer to keep the uvfs log as small as possible. When you finish capturing a good debug log after reproducing the issue, change the log level back to info. The debug log captures a lot of useful information but it really slows the game. A few thoughts in the interim...

 

Add an exclusion or temporarily disable your antivirus to ensure it is not interfering with the hooking process.

 

Run Explorer, right click on ModOrganizer.exe, click Properties. If you see an Unblock button, you'll need to click Unblock and click OK. Rinse and repeat for all *.exe and *.dll files in the Mod Organizer folder and subfolders. This is mostly an issue with Windows 10 and I think I've reached my Windows 10 rant limit for the week so I'll be quiet.

 

Do not install Mod Organizer in the Steam or Fallout 4 folder because this is known to cause issues with the virtual file system.

 

Do not install Fallout 4 (or any other game you run from Mod Organizer) in Program Files, Program Files (x86), or any other folder controlled by UAC because this will cause permission issues that prevent the hooking processor or the virtual file system from working correctly. Always install Mod Organizer and the tools you use (like LOOT, Wrye Bash/Flash, etc.) in a folder you create as a user.

 

If you are running Fallout 4 (or any game or tool) as an administrator and you are not running Mod Organizer as an administrator, the hooking process will not work because Windows prohibits a user process from hooking an admin process. If you must run the game as admin to get it to work, you have permission issues somewhere so see the previous point. Also keep in mind that any files (like your saves and the INI files) created by a process running by an admin may be created with admin as the owner and you as a user may not have access rights to these files.

 

EDIT: I forgot to mention, you might also try the latest 2.1.4 dev build in #builds on the Mod Organizer discord. If you do this, be sure you unblock the zip file before you extract the files (right click the zip from Explorer, Properties, Unblock, OK). If you skip this step, every file extracted from this archive may be blocked and Windows 10 may have a hissy fit).



#8 Kelryth

Kelryth

    Prisoner

  • Members
  • 5 posts

Posted 02 June 2018 - 01:25 PM

If your discord is from this post: then your Discord link has expired. You have to use the Permanent option instead of the temp link.

 

I set mo to debug but it looks the same to me. Im on windows 8.1

log USVFS

 

Edit I think I figured it out, My antiviruses auto-protect seems to be interfering with something as loot works if I disable auto-protect. I added my mod folder where I have MO and loot and stuff installed to the auto-protect, sonar and download intelligence tools exclusion list of my AV and it looks like its working again


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users