ModOrganizer 2.0.8.1 Not Recognizing Mods on Skyrim SE Any Longer

[ma091983]

I seriously love using MO, by the way. The virtual folder idea is a genius idea, and it allows me so much freedom when it comes to trying out various mods. If the annoying black face problem reemerges, then I don't have to uninstall everything, but instead, one-at-a-time, unclick a checkbox and click back again to pinpoint which mods are conflicting with which.

The ease of installing and uninstalling mods is so awesome, that I don't want to go back to Nexus right now. HOWEVER, at some point, MO stopped recognizing my mods.

I started to notice that some mods which I was installing didn't appear to be showing up at all. And, if I uninstalled an older mod and reinstalled it, MO would not recognize it any longer. I later uninstalled and reinstalled MO to see if that would help, and it did not.

I uninstalled and reinstalled Skyrim SE and I now have a completely, pristine Data folder and I even uninstalled all of my mods in MO and reinstalled some of them.

Whenever I try to start a new game, it continues to tell me that the .esm and .esp files are missing. I check the mod folders and find that they are there.

That's when I started to backup my Data folder, I tried to make a pristine one, but it continued to make the same error. I later uninstalled and reinstalled Skyrim SE, which took HOURS, and it was the same problem. I later deleted all of my mods in the Mods folder of my MO AppData directory. And, the problem continued to persist.

One odd thing to note is that I have an alternate song, and that is still playing whenever I start the game with MO. It no longer does this with Steam Skyrim SE as I uninstalled everything and cleared it out. However, Alternate Start doesn't load, and I think that that's because it was one of the mods that I uninstalled and reinstalled to see what the effects would be.

So, my guess is that something somewhere outside of the Skyrim SE folder and the MO's AppData folder is causing this problem. Perhaps a file in the Program Files (x86) folder of MO?

I tried researching this on their wiki page, but I could not find anything like this in their troubleshooting section. This seems to be an entirely unique situation. This LOOT problem is the closest to my problem that I could find after days of researching.

Please help me.

[twiztedmongoloid]

I love mod organizer as well man. Why anyone would use NMM for classic is beyond me. MO is better in almost every way.

 

With that said it doesnt work for 64 bit skyrim without serious workarounds and then it only half works. Several functions dont work at all.

 

Because of that and many other reasons you should just stick with classic skyrim and the old MO. What is your reason for playing SE right now?

[ma091983]

I love mod organizer as well man. Why anyone would use NMM for classic is beyond me. MO is better in almost every way.

 

With that said it doesnt work for 64 bit skyrim without serious workarounds and then it only half works. Several functions dont work at all.

 

Because of that and many other reasons you should just stick with classic skyrim and the old MO. What is your reason for playing SE right now?

Because, I never played Skyrim before and this is the first experience. I don't feel like going back to an earlier Skyrim right now.

[ma091983]

I don't want to have to go back to an older Skyrim version. Is there anyone else using Skyrim SE who's also getting this problem? What about the mod makers? How can I contact them?
I'm fairly new to Skyrim and Nexus, so excuse me if I'm asking what should be an obvious question.

[twiztedmongoloid]

Like i told you Mod Organizer the 64 bit version wasnt fully finished by its devloper. So it doesnt work right. Tannin the creator of Mod organizer has been hired by nexus to rebuild their Mod Manager (formerly NMM). Dont know what the new name will be or if they will just retain the old one.

 

There are people trying to finish what Tannin started with the 64 bit MO but last i checked nobody has been able to quite figure it out.

 

With all that regarding special edition it doesnt really benefit PC players at the moment due to no SKSE or SKY UI making a LOT of mods incompatible.

 

Its really only an upgrade for console players as they get better graphics and the ability to add mods.

 

Until SKSE and SKYUI are updated as well as the new mod manager i mentioned above......as a PC player its just best to play classic. MO for classic is bug free and fully functional. Sorry if you dont like my answer.

 

If you really insist on playing special edition your best bet is to just use NMM (as much as it pains me to say that).

 

Ive always said i use the best tool for the job.

[ma091983]

64 bit is going to be better because it takes advantage of the 64 bit memory addresses. Having a 64 bit memory address means that you're operating under the assumption that there will be more than 4 GB of memory.
Plus, better graphics and it should perform better with a 64 bit OS than not.

[twiztedmongoloid]

64 bit is going to be better because it takes advantage of the 64 bit memory addresses. Having a 64 bit memory address means that you're operating under the assumption that there will be more than 4 GB of memory.

Plus, better graphics and it should perform better with a 64 bit OS than not.

 

I am well aware of the benefits of 64 bit vs 32.

 

You completely missed what i am trying to tell you. Do what you wanna do my friend.