Still no fix for MCM not showing mods?

[tarzanofmars]

I did a brand new install for my new build (i7,GTX780,SSD etc) and followed the latest STEP instructions. Spent about 12 hours doing it.

 

No CTDs, everything looks great (except some trees in the far distance look blocky, I'll work on that next), I also changed the load time for the papyrus as suggested to give it more time to load complex scripts as suggested.

 

I have Realistic Needs and Diseases, Frostfall, Wet and Cold, Hunterborn and several other mods (that worked fine in my old build with MCM/SkyUI) but now the only mods showing in MCM are Lanterns, Complete Crafting and SkyUI.

 

I have spent a few hours googling solutions and most of the threads on this subject just end with no real solution.

 

I did the console reload command, nothing. I am currently trying to uninstall every mod that uses MCM, as I read that some have had success doing that, then adding them back one at a time, but I have no real easy way to find which mods use it as some of these are new to me.

 

I am using ModManager (per STEP) and there is no listing in mods or plugins for Lanterns of Skyrim and thus I cannot uninstall it. I have a plugin for Complete Crafting Overhaul and I unchecked it, reloaded game, brand new, not a save and both Lanterns and CCO are still showing in MCM.

This whole process is convoluted and way too complex for a game.

 

If I ever get this game running perfectly I will upload my entire Skyrim folder to Dropbox so other people will not have to go through this mind numbing process. There is NO FILE SIZE LIMIT on Dropbox when using the desktop application.

 

Why has someone not done this before? Just take a fully working 200 mod Skyrim folder and share it with people directly??

 

 

[bojanni]

Because that would be illegal because you would be sharing copyrighted software and a lot of modders would not agree with sharing their mods that way.

 

Something is obviously wrong when you don't have a Laterns of Skyrim plugin in the left and/or right pane of Mod organizer. I would start there.

[tarzanofmars]

Even if someone owns the game? The folder would do no good unless you owned the game right? I have the steam version.

 

Hmm I installed Lanterns normally, I don't what to do then. I'll take a look at your load order, do you use similar mods?

[bojanni]

Yes, it's the same as when you own a movie on dvd or blu ray. You are not allowed to share the contents, even parts of it. You own the medium, not what's on it.

 

I use Lanterns of Skyrim for instance and all my other mods that have a MCM menu show up perfectly in MCM.

[tarzanofmars]

I don't think Lanterns is the problem, but it is weird it is not visible in MM.

 

There are about a dozen threads on this issue of MCM showing some mods and not others, I was hoping someone who had the problem and then corrected it would see this thread and share the fix.

 

The only fix I can't try is removing all mods that use MCM because I can't remove 2 that do or find out which others use it.

[bojanni]

Yeah I know about the issue and encountered it once or twice. Usually the console command worked just fine or I just started playing and the menu would be registered after a few minutes.

 

I suggested you would start with Lanterns because it is obvious something went wrong there. My thought was, if you start solving that, the chance is you encounter other issues which maybe the cause of your MCM menu problem.

[tarzanofmars]

Thanks. Do you use ModManager or NMM? I never had an issue using NMM before and now I'm using MM...

 

The lanterns esm and bsa are in my data folder, just reinstall? And as far as the crafting, I unticked the plugin and that's all I know to do? It still shows on a new game.

 

I suppose I'll go through my data and physically remove any file I think uses MCM. That just sounds like a disaster though.

 

The frustrating thing is that I had a really good setup going and a nice save game, I had nearly all the mods I do now (except I'm running all the HD textures on highest available) and MCM worked just fine everytime and you know how I had that working? In the most random/haphazard/whatever-suited-my-fancy way, added mods via steam and then just ran boss and played, never a problem.

 

This time I painstakingly followed STEP and I'm having all these issues.

 

#DontDoWhatIDid

[bojanni]

I never followed STEP, just started , crashed, started over , crashed, followed youtube tutorials etc. I switched to Mod Organizer, because I like the idea of a clean data folder .it took some getting used to but it suits me more than NMM. You are talking about MM. Do you mean Mod Organizer or do you use something else ?

[tarzanofmars]

Sorry, I meant Mod Organizer. I never had issues with subscribing mods on steam (believe it or not) and then just running boss, along with SKSE.

I just tried these 'fixes' below and now I'm CTD at load screen, something that's never happened to me. Even have tried reversing it, still CTD. Don't know how to find out what's causing it.

I think I'm just going to start over and use steam mods, NMM and boss, I know lots of people have issues with that but I never did.

In response to post #14491968. #14492598, #14493923 are all replies on the same post.

It sounds like people are getting caught by Mod Organizer's "BSA Priority" feature again. It was discovered over a year ago that the way MO tries to dynamically manage BSAs for it's "BSA Priority" feature causes problems for some mods.

My understanding of the issue is that when the core SkyUI scripts have to interact with scripts from other mods the MO's Priority management trick doesn't always get all of the scripts unpacked fast enough for them to interact successfully.

The reason unpacking the BSA helps is that it keeps MO from playing it's little games with the SkyUI BSA file and so the SkyUI scripts are always available.

The easier, but less obvious, solution to the problem is to just uncheck the BSA file so that MO won't try to "manage" it. That way you get the performance benefits of a packed BSA file.

 

SKYUI + Mod Organizer Users with missing MCM Menus - FIX!

I spent days trying to figure out this problem looking everywhere on the Internet. I tried every suggested fix, nothing worked. Less hair...

Mod Organizer (MO) (version 1.2) does not install SkyUI properly. You will see the SkyUI Interface, but the MCM (Mod Configuration Menu) will only show the MCM 3.0 logo but no Mod Config Options.

So here is what I did to fix the issue:

REMOVE FOMOD FROM SKYUI ARCHIVE

1. Remove SKYUI from MO.
2. Download the SkyUI 4.1 archive (7z file) manually to your downloads folder.
3. Using 7z, unarchive the mod to a new directory.
4. Delete the original archive.
5. Delete the FOMOD folder from the new directory.
6. Re-archive the folder.

UPDATE MO SETTINGS

7. Open MO
8. Open up the Settings dialog (the Wrench and Screwdriver icon on the top of the interface).
9. Click the Reset Dialogs button.
10. Close the Settings dialog.

INSTALLING SKYUI AND UNPACKING BSA FILE

11. Click the Install Mod Archive icon (top left of MO interface)
12. Select your saved SkyUI modified archive.
13. During the installation of the mod, you will be asked if you want to unpack the BSA file.
14. Select YES!
15. Re-enable SkyUI MOD in MO.
16. Re-enable SkyUI Plugin in MO (might be done automatically in step 15.
17. Run a BOSS Sort.

Start Skyrim and cross fingers that you have MCM Config Menus!

Optional - If you see mods in your MCM menu, but there are some missing, then you can run the following command from the console:

setStage SKI_ConfigManagerInstance 1

This would not of worked before as the Scripts were not available to the console until you installed SkyUI using the above method.

I hope this helps out all those frustrated MO SkyUI users.

Cheers,

Rick

[tarzanofmars]

I have no idea how I did this but after trying the above I just reloaded an old save, one I had written off as lost forever, one that I'd used before I completely reinstalled thew game and started from scratch. It works (so far) and the MCM shows all the mods.

 

Crazy, as it still won't work with a brand new game.