MOD ORGANIZER went totally malfunctioning! HELP

[PINGERton Agent]

Bought SSE, installed Sexlab for 4 hours, malfunctioned, installed everything all over again, and now Mod Organizer is rerouted the game folder location into god knows where.

 

I tried everything. I checked out settings, deleted my local cookie, reinstalled entire MO, and it malfunctions and my entire load order was fake and never actually install anything to my Game root folder.

 

So, if i cant find the answer, since i have no idea how to use Wrye, i doubt i can even manually install my mod list in desire cuz i tried and didnt work.

 

Turns out Sexlab Arousal Redux for SE and NiOverride is totally not working with my manually jury rigged game folder. i had to delete all efforts and grab my backup folder.

 

The point is, whatever i do, MO states that my desired mod was installed, but when checking other Mod managers or directly into root folder, none of the functions actually installed.

So i really need to have some input about redirecting MO download location into actual game folder.

 

All the best.

[Dorabella]

My first suggestion is to install MO in the Skyrim directory.
The second is to remove the various mods, uninstall MO, and always in the directory of the game install NexusMM

[ButchDiavolo]

The first question would be: which MO do you use? MO1 or MO2. MO1 doesn't work with SE.

 

Secondly, assuming you installed MO2, which option did you select when asked. Most modders say you should install it as "portable", because that apparently gives you more freedom to customize your MO folders (where to download to, where to install etc)

If you selected the other option during install, MO2 will be installed in to your C:\Users\[yourname]\AppData-folder.

 

I haven't had any problems using MO2 (version 2.1.3 on nexus) installed as portable. After customizing the folders, everything ends up where it should. So check your C:\Users\[yourname]\AppData folders to see if MO2 is placing the files there.

[PINGERton Agent]

 

4 minutes ago, Vachnic said:

The first question would be: which MO do you use? MO1 or MO2. MO1 doesn't work with SE.

 

i use 2.

 

well, guess i should try portable, but it didnt work when i tried, guess this time it can be different.

[PINGERton Agent]

23 minutes ago, Vachnic said:

Secondly, assuming you installed MO2, which option did you select when asked. Most modders say you should install it as "portable", because that apparently gives you more freedom to customize your MO folders (where to download to, where to install etc)

1

Sorry, didnt work. guess i should import entire load of mods into Vortex. Nowhere to run elsewhere cuz MO2 obviously is compromised and doomed beyond reproach.

Also i changed my download locations into D drive cuz i use SSD and im already out of space to store. Should i endure the storage occupation?

[ButchDiavolo]

Well, I am sorry that MO2 isn't working for you somehow. I am not sure what else I can tell you to try. But if Vortex works for you, then just stick with that as a mod manager. Or if all else fails, use NexusMM.

[PINGERton Agent]

roger that, thanks btw.

[khumak]

Keep in mind that MO does not ever install anything in your actual game folder in case that's what you were looking for.  It uses a virtual file system so you have to run all tools as well as the game itself from within MO or they won't see any of your mods.  This can be confusing at first but once you get used to it, it's much easier to manage your mods that way.  NMM and Vortex both install mods into your real data directory.

[Uncle64]

4 hours ago, Lestat1627 said:

My first suggestion is to install MO in the Skyrim directory.
The second is to remove the various mods, uninstall MO, and always in the directory of the game install NexusMM

Why should he ever do that?

[Nazzzgul666]

6 hours ago, 4nchorage Pingas said:

The point is, whatever i do, MO states that my desired mod was installed, but when checking other Mod managers or directly into root folder, none of the functions actually installed.

 

The entire point of using MO is that it doesn't put anything in your data folder ever. And not using other mod managers that do so. If you're unhappy with that, don't use it, that's not a bug but a feature.

[Dorabella]

2 hours ago, Uncle64 said:

Why should he ever do that?

I have no idea. Initially, I used MO, but having discovered that it did not install the mods, I removed it and replaced it with NMM . Using NMM, installed in the game directory, I solved all the problems of the installed mods.
I do not know what has to do with your problem, but I had found a discussion in which they said NOT to install Skyrim in C / Programs / Programs (x86) directories as I was going to create various problems. Following that suggestion, I installed my Skyrim in C / Games, NMM in the Skyrim directory (C / Games / Skyrim)

[Uncle64]

Oki. If that works for you.

MO1-2/NMM can whith easy be installed in any disk or folder. Best thing always to do is NOT to use Steam default folders for installing games.

 

Not sure if it have been said, but MO dont install any file in Skyrim\data folder. It uses its own viritual file system.

 

OP in what setting did you install your MO2? Portable or Standalone?

 

[PINGERton Agent]

4 hours ago, Uncle64 said:

OP in what setting did you install your MO2? Portable or Standalone?

 

 

Just made New file and install entire stuff into it. maybe it was the problem after all...

thankfully i just used NMM to install vital parts and it worked fine except Dripping when Aroused keep spewing error message despite plugin checkup said otherwise.

 

Maybe i really should reconsider my approach method toward MO and give it a try with a totally different way. I will check my local wiki for this one.

 

Wish me luck

[ButchDiavolo]

From experience I can tell you that using more than one mod organizers (i.e. MO and NMM/Vortex) will greatly increase the likelyhood of problems. MO works completely different (and "cleaner") than NMM/Vortex, as others have said before. NMM/Vortex install mod into the Steam-game directory, whereas MO does not. MO uses a virtual file system, which keeps your game directory clean. The only things you have to install in the game directory with MO are SKSE and your ENB files (and dlls for SSE fixes etc.)

 

In short, combining the two different kinds of mod organizers will not work, because i.e. MO won't find the mods you have installed with NMM and vice versa. So pick one option and not both.

 

If you decide to go the MO2 route, do not install MO in "Programs" or "programs x86 folder"! I personally always install MO as close to a root directory (i.e. D:/MO2) as possible. Also, don't install Steam in the programs or programs x86 folders. Personally I use D:\steam. But that is up to you where you install it.

[khumak]

On 7/30/2018 at 6:52 AM, Vachnic said:

From experience I can tell you that using more than one mod organizers (i.e. MO and NMM/Vortex) will greatly increase the likelyhood of problems. MO works completely different (and "cleaner") than NMM/Vortex, as others have said before. NMM/Vortex install mod into the Steam-game directory, whereas MO does not. MO uses a virtual file system, which keeps your game directory clean. The only things you have to install in the game directory with MO are SKSE and your ENB files (and dlls for SSE fixes etc.)

 

In short, combining the two different kinds of mod organizers will not work, because i.e. MO won't find the mods you have installed with NMM and vice versa. So pick one option and not both.

 

If you decide to go the MO2 route, do not install MO in "Programs" or "programs x86 folder"! I personally always install MO as close to a root directory (i.e. D:/MO2) as possible. Also, don't install Steam in the programs or programs x86 folders. Personally I use D:\steam. But that is up to you where you install it.

Vortex is actually fairly compatible with MO.  Both of them install mods the same way and just do the actual deployment differently.  In both cases it's not possible for you to have a conflict during the installation phase because nothing is deployed yet.  The deployment is when the conflict resolution happens.  Vortex does it as a separate step before you run the game.  MO does it when you actually run the game.  So you can actually set them both to use the same mod directory and only install your mods once and then have access to both mod managers for the same game.  There's not much reason to do that though. 

 

The only reason I can think of would be a situation like the one I ran into where I installed all of my mods through Vortex and ran into a problem I couldn't figure out so I just set my mod directory in MO to be my Vortex install directory, purged my data folder in Vortex, and then switched to using MO (didn't have to reinstall anything, just run the game and I'm done).  I could see someone doing the opposite if for example they just couldn't get one of the 3rd party tools to work through MO or something.  You could deploy your mods in Vortex, run that tool, save the output to a mod, then go back to using MO again.

[PINGERton Agent]

welp, turns out it was my load order and installation scramble mess. And i cant figure out what went wrong from the beginning.

I learned Racemenu is the only way and ECE does not support XPMSE, but how the hell should i install Boob physics without problems? I think major problem is mostly comes from female framework issues.

 

HDT SMT looks promising... but since there is a voice that says HDT is unstable and obsolete and i cant figure out whether is true or not, i could not rush my decisions.

 

so i must ask, how to install HDT and XPMSE properly and not gonna destroy my local folder into pulp?

[PINGERton Agent]

error: Native function GetEquippedArmorInSlot in empty state could find no matching function on linked type Actor. Function will not be bound.
The problem here. I cant interpret this stuff. I dont know where everything went wrong and scrambling load process. I'm confident its skeleton and bodyslide, HDT related armour issues. but heck, this is more improved situation than before. Beforehand i couldnt even notice client popping up.