Jump to content

[solved] Skyrim not recognizing LAL (using MO)

Recommended Posts

Okay, so last night I got a lot of help uninstalling all my mods and reinstalling some of them so I can start using Mod Organizer instead of NMM. Everything was working fine until I installed Live Another Life. I started up a new game to test it out, but strangely enough I was greeted with the opening vanilla carriage ride. I quit the game, checked everything to make sure it was installed correctly (it was) and tried moving LAL further down on the load order. But no matter how far down on the load order I put it, every new game started out in the carriage.


Here's my load order from MO:




Unofficial Skyrim Patch.esp
Unofficial Dawnguard Patch.esp
Unofficial Dragonborn Patch.esp
Unofficial Hearthfire Patch.esp
Lanterns Of Skyrim - All In One - Main.esm
Unofficial High Resolution Patch.esp
dD - Realistic Ragdoll Force - Realistic.esp
AOS2_EBT Patch.esp
AOS2_GDO Patch.esp
AOS2_WAF Patch.esp
AOS2_WetandCold Patch.esp
AOS_TAD Patch.esp
Skyrim Immersive Creatures - DLC2.esp
Skyrim Immersive Creatures.esp
dD - Enhanced Blood Main.esp
dD-DG-DB-Immersive Creatures EBT Patch.esp
Guard Dialogue Overhaul.esp
WetandCold - Ashes.esp
Traps Make Noise.esp
Weapons & Armor Fixes_Remade.esp
Immersive Battles.esp
Immersive Brigands.esp
Immersive Dawnguard.esp
Immersive Dragonborn.esp
Immersive Factions.esp
Immersive Mercenaries.esp
Immersive Patrols.esp
Immersive Travelers.esp
Immersive Werewolves.esp
Unique Uniques.esp
Alternate Start - Live Another Life.esp
nem-e5i5's RaceMenuPlugin.esp



A couple extra things. MO is giving me two warnings.


Warning #1




INFO (16:04:59.0518): no ini tweaks file
INFO (16:04:59.0518): data path is C:\Program Files (x86)\Steam\steamapps\common\Skyrim\data
DEBUG (16:04:59.0519): mods are in "C:\Program Files (x86)\Mod Organizer\mods"
DEBUG (16:04:59.0519): data path: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\data

ERROR (16:04:59.0519): archive "C:\Program Files (x86)\Mod Organizer\profiles\Default\archives.txt" not found!
ERROR (16:04:59.0553): failed to set up list of bsas

----------- LOG END -----------


This one just means I'm not getting a complete list of bsas for use with programs like LOOT or BOSS, right? I used BOSS, and sure enough, it's not recognizing my entire load order. I installed LOOT to see if that would work, and again, I'm only getting a partial list of my load order from LOOT. Not sure how to fix this, would appreciate help on it as well.


Warning #2




Files in the Overwrite mod are are usually files created by an external tool (i.e. Wrye Bash, Automatic Variants, ...).
It is advisable you empty Overwrite directory by moving those files to an existing mod. You can do this by double-clicking the Overwrite mod and use drag&drop to move the files to a mod.
Alternatively, right-click on Overwrite and create a new regular mod from the files there.

Why is this necessary? Generated files may depend on the other mods active in a profile and may thus be incompatible with a different profile (i.e. bashed patches from Wrye Bash). On the other hand the file may be necessary in all profiles (i.e. dlc esms after cleaning with TESVEdit)
This can NOT be automated you HAVE to read up on the tools you use and make an educated decision.




I checked the Overwrite section, but the only thing in there is a file marked hdtPhysicsExtension.log for SKSE (It looks like this: (folder) SKSE > (folder) plugins > hdtPhysicsExtension.log). I'm not sure how to turn this into a mod, or if I even should. I'm also not sure if either of these errors are related to my inability to use LAL.


Any help would be greatly appreciated.

Link to comment

For starters, go to the icon at the top in MO that looks like a driver's license or something. In there be sure that "local savegame" is checked for each profile you create. This leads to the next issue....


Go to /document/my games/Skyrim/ and copy/move the two .ini files there to somewhere safe then nuke that entire Skyrim folder. This is where vanilla/NMM saves end up and bad stuff can reside in there. Then each profile has it's own .ini tweaks and it's accessed with the jigsaw puzzle looking icon at the top of the MO window. You can copy your old .ini files and paste them into there for each profile, and yes it means each profile can have a different setup if you need it. Awesome, huh? You could just run the vanilla launcher and let Skyrim automatically generate .ini files as well, but since they'd be in /documents/my games/Skyrim/ you need to do this before nuking that folder obviously. :D


If you still have any manually or NMM installed mods and LOOT is running inside of MO it may not see your mods. Or if LOOT is being run outside of MO it will only detect the stuff manually or NMM installed into the Skryim game folder. You really need to have a brand new, sparkly clean Skyrim install for MO to do it's real magic and then you need to only add mods with MO. So put LOOT anywhere you want on your computer then add it to MO as an executable binary with it directed towards the MO mod folder.


And speaking of manual installs, you will need to add a couple things manually. These are things that go in the Skyrim root folder and not in the /data/ folder. MO is a virtual /data/ folder itself. So anything that goes in /data/ gets installed with MO and anything that goes in the root folder above /data/ still gets manually placed there, like SKSE and ENB files.

Link to comment

Okay, it was a combination of things:


1. I was not starting Skyrim via SKSE through MO. My fault, I didn't think that was required.


2. There were some missing masters, I took care of that


3. I did as gvman3670 suggested


And now things work fine!


Thanks for the help guys, I really appreciate it.

Link to comment


This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. For more information, see our Privacy Policy & Terms of Use