Jump to content
  • 0
Sign in to follow this  
primem0ver

MO installed mods not being found

Question

This is my first time using MO and utilities are not recognizing anything but what is installed in the vanilla directory. I cannot get LOOT or TesVEdit to recognize any mods installed through MO. I have ONLY tried running them through MO. I cannot play skyrim until I get my mods working because this is a reinstall after an OS fail and my savegames use the mods I have installed with MO (which means I need to get TesVEdit working in order to combine a few like I had them before).

Share this post


Link to post
Share on other sites

11 answers to this question

Recommended Posts

  • 0

Ugh.  It didn't make a difference.  AHA!!  Yes it did.  I modified my original zip uninstall the first time accidentally.  So even if the folders are the same, it must use the original install path in order to work.

 

To make this more clear...

If you use ridirects, junctions, mapped drive folders etc... in your path you MUST use the exact same path it was originally installed too.  Even though c:\Program Files (x86)\Games\Steam\SteamApps\common\Skyrim and d:\Games\Steam\SteamApps\common\Skyrim are actually the same folder (on my computer), the path used in the ModOrganizer.ini file must be the same as the original install path.

Edited by primem0ver

Share this post


Link to post
Share on other sites
  • 0

In addition to my answer to your question in the Nexus forum, you must recognise that ANY tool that you want to use on your MO installed mods MUST ALSO be installed as an executable via MO.

 

MO uses a virtual file system and therefore the mods installed need to 'worked on' by tools that are aware of that VFS.

LOOT, Wrye Bash, TES5Edit or any other tool you want to use will only 'see' mods if they are run via the MO ui.

Share this post


Link to post
Share on other sites
  • 0

I said the following in the Nexus forum:

 

I am certain I did it right.  I clicked the Green Blue Gear button at the top (towards the left) and added it through the dialog you spoke of.  I followed the MO instructions on the LOOT video (https://www.youtube.com/watch?v=mzsb3hvbbr4) and the merge script video (

 

 

The only thing that isn't as you say is that the executables are NOT in my Skyrim Data folder.  But honestly, those tools have always run fine from the folders I installed them in.

 

 

 

In addition to my answer to your question in the Nexus forum, you must recognise that ANY tool that you want to use on your MO installed mods MUST ALSO be installed as an executable via MO.

So then from what I understand, I must install LOOT and TesVEdit from within MO BEFORE adding them to the list using the Modify Executables dialog?

Edited by primem0ver

Share this post


Link to post
Share on other sites
  • 0

 

 

So then from what I understand, I must install LOOT and TesVEdit from within MO BEFORE adding them to the list?

No. By "install via MO" I mean you need to have them added as executables in the MO program and run them from there. You can install them by any method you like but for them to "see" those MO installed mods they need to be RUN from MO.

 

If you have done as the instructions on the description page and the variuous YouTube videos describe, and I am assuming you have, the only other thing I can think of at the moment is Windows UAC is interfering in some manner.

 

If you have installed MO into the Program Files directory I would suggest you uninstall it and place it elsewhere.

Share this post


Link to post
Share on other sites
  • 0

UAC?

 

Perhaps then I should explain more about my setup in case it matters.  I do not follow traditional windows conventions for several things.  Skyrim is installed through a junction "Games" in my Program Files (x86) folder.  MO isn't installed in the Program Files folder at all.  Here is the way it was done:

 

D: is a drive with empty folders that map to different partitions.  D:\Games is mapped to my games partition.

In my Program Files (x86) folder is a folder junction (made using mklink /j) that points to the above folder.

 

I installed skyrim in c:\Program Files (x86)\Games\Steam\SteamApps\common\Skyrim

I copied MO (from the zip file it came in) directly to d:\Games\Steam\SteamApps\common\Mod Organizer and start it using a shortcut on my desktop.

I then linked to the Skyrim folder using the d:\Games\Steam\SteamApps\common\Skyrim path (same actual folder but different "path") when starting the first time.  [EDIT: this was my mistake...see solution]

 

Should I have linked through the original install path?

Edited by primem0ver

Share this post


Link to post
Share on other sites
  • 0

hmm... interesting.

 

So does the game run when run from MO? Also do your MO installed mods load IF the game does run from MO?

Share this post


Link to post
Share on other sites
  • 0

Honestly, I don't know.  I haven't played yet.  I have more mods than allowed which is why I need to combine some of them.  But I suppose I could find out by starting a new game with some MO installed mods running to see if they load.  Question is... what is a good mod to use so that I can tell right away?  If you could let me know I can test it tomorrow and post the results.  Need to get to bed lol.

Share this post


Link to post
Share on other sites
  • 0

I have one other quick idea.  I know that if I search for files in my users folder using D:\Users, that the crappy Windows "quickfind" features do not respond (which is a good thing because the windows indexing feature SUCKS).  So perhaps if MO maps to the folder in the ini file it uses and the other utilities use the registry to find the actual install path, then using the the d:\ path was a mistake because my experience with windows indexing suggests that the virtual path does matter.  So I am going to try changing the path in the MO ini file to the original install path and see if that works.

Share this post


Link to post
Share on other sites
  • 0

Ahh, okay. Well you need to see straight away, that is in game time, not right away as in tonight that is. If you have Alternate Start that will quickly tell you if MO is working. Or something like SkyUI then when the carriage ride ends you can fairly soon see if it is active.


If you have installed Skyrim and then later moved it or in some way changed the location, then yes there will probably be some orphaned references in the registry.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By Aiden5576
      I love the guide (been using it for years and love the efforts you guys have put into enhancing the vanilla game), but I have an issue/question about Alternate Start being a requirement for the patch.  Why?  Don't get me wrong it's a fantastic mod with all the options available, but, not everyone wants to use that.  I for one prefer Skyrim Unbound as I feel I have much more control over how I start the game than just picking a location to spawn in.  I would love to remove it as a master, but, I don't even know how to do that anyway.
       
      I guess i'm basically asking why it's been made a requirement  to use the patch?  I apologize if this has been asked before already.
    • By Hydonix
      I'm trying to change the master's of two plugins I have from Blues Skyrim.esp to Dawn of Skyrim.esp. I can't even get the plugin I'm trying to edit to load within xEdit because it is greyed out because the master is missing so I don't even have a chance to edit the master. Would really appreciate any and all help on this matter!

    • By DogWada
      I'm using MO2 for Skyrim LE. When i first installed MO2 i selected "Create a portable instance" when i was prompted, so i don't have a global instance, i'm not sure if that's ok? I used Vortex before this and had no issues with FNIS so i do know how to use it.

      At this point i've watched multiple MO setup and installation guides and read a bunch of forum posts but i can't get GenerateFNISforUsers.exe to work when it's run through MO Executables. When i run it, it says:
      Generator: C:\Games\MO2\mods\2 FNIS Behavior 7_6\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe
      ">>Warning: Bad installation. Generator not run from <Skyrim_Data>\Tools\GenerateFNIS_for_Users. If you use a mod manager, run FNIS from its list of supported tools.<<
      Skyrim 32bit: ??.??.?? - C:\Games\Steam\steamapps\common\Skyrim\ (Steam)
      >>Warning: Expected generator path: C:\Games\Steam\steamapps\common\Skyrim\data\tools\GenerateFNIS_for_Users not found<<"
      But when i run "Explore Virtual Folder" and open GenerateFNISforUsers.exe there it loads all my mods fine. I could just activate it this way or go to the data tab in the right MO pane and right-click GenerateFNISforUsers.exe and select "Execute with VFS" each time but i'm concerned something won't work if im doing it this way, and it's less convenient to activate it like this every time.
      I did what this guide said: https://youtu.be/53472H4lAuA?t=597(timestamped) but this didn't work for me either. For him when he runs the GenerateFNISforUsers.exe through MO tools it says "MO is locked while the executionable is running", for me i get this message: and FNIS doesn't show on my screen so i can't see if it's loading my mods correctly or anything. If i click "Unlock" it says: and i think crashes FNIS. If i don't press unlock and just wait a few seconds the message will go away and my overwrite folder will have contents.
      After all of that if i set the Executables to the same directory i used for this process it still just gives me the same 2 warnings like i said at the start of the post.
      So what am i doing wrong here? What should i do?
       
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.