

I've stumbled upon a weird issue that I haven't encountered or read about before. I think the verification through steam itself may have been enough as it now launches correctly, I'm going to give it a while before I mark this as solved though just in case. The AI BSA should be listed first in the list. Actually on BSAs, check in the 'Archives' tab that each of them is actually checked and that you have MO managing them, and Archive Invalidation is working properly.

With the later versions of MO there isn't as great a need to extract the BSAs, though you can if you wish. With this clean slate of a profile add in each section of the guide and double check the settings as you go. All new profiles MO creates will be based on these newly generated INIs. If there are no active mods in the profile and the problem still exists logically the fault is in those INIs.Ĭlear out any trash that may be left over from your ENB and get Steam to verify your files and then run the game from the launcher to set the new default INIs and work from there. Well if that is the case, the new profile would have pulled the INIs from the games defaults in your 'My Documents' folder and used those as a base.
