Issues with New USSEP?

[Fear2288]

Anyone having crashes or other issues with the recently updated USSEP?

I’ve come back to the game after a few months and updated my mods and was surprised to see a USSEP update.

I added a few new ones that came out in the meantime as well - mostly armor sets, retextures, and model replacers.

But while the game starts and I can get to the main menu, it crashes after pressing New Game.

My crash logs aren’t being very helpful, naming a range of mods from a few Lux patches to an NPC replacer or two to quest mods like Innocence Lost Expansion and the Destroy the Dark Brotherhood Enhanced mod.

I know that I have quite a few mods that needed USSEP patches or required USSEP but I can’t say if all of them have been updated since USSEP’s update (or even if they need to be).

Has anyone else had issues since the new update?

[UsernameTaken666]

No issues here.

[Nabinkemper]

I recently updated to current from 640. Rather than update mods individually, I went with a clean reinstall. Everything is working great at the moment. Sometimes it's better to start with a good foundation than to update mods on the fly.

[Fear2288]

Originally posted by Nabinkemper:

I recently updated to current from 640. Rather than update mods individually, I went with a clean reinstall. Everything is working great at the moment. Sometimes it's better to start with a good foundation than to update mods on the fly.

When you use 2800 total ESMs, ESPs, and ESLs you don’t really do that - you’ll be putting that together for a good two weeks before you even play the game (and it’ll likely still have some issue on first attempt).

I’ll try reinstalling the new USSEP, if that doesn’t work I’ll try disabling some of the mods my crash logs are specifically naming one-by-one. If that doesn’t work I’ll try lowering that 2800 to something smaller.

I have 20+ GB of RAM still available for Skyrim to use, but there always seems to be this “hidden limit” that fluctuates a little where if I go over it it just doesn’t work. It happens more with FO4 than Skyrim for me but every now and then it pops up here.

[ryo_oki]

No problems so far, sounds like a mod or 2 might not have gotten updated. I'm starting a complete new mod list and reinstall...again...... :> I swear I spend more time playing with mods than I do the game itself.

[Nabinkemper]

Originally posted by Fear2288:

When you use 2800 total ESMs, ESPs, and ESLs you don’t really do that - you’ll be putting that together for a good two weeks before you even play the game (and it’ll likely still have some issue on first attempt).

I’ll try reinstalling the new USSEP, if that doesn’t work I’ll try disabling some of the mods my crash logs are specifically naming one-by-one. If that doesn’t work I’ll try lowering that 2800 to something smaller.

I have 20+ GB of RAM still available for Skyrim to use, but there always seems to be this “hidden limit” that fluctuates a little where if I go over it it just doesn’t work. It happens more with FO4 than Skyrim for me but every now and then it pops up here.

Completely understandable, Fear. My list sits at about 450-460 at the moment. Good luck to you!

[Fear2288]

Originally posted by Nabinkemper:

Originally posted by Fear2288:

When you use 2800 total ESMs, ESPs, and ESLs you don’t really do that - you’ll be putting that together for a good two weeks before you even play the game (and it’ll likely still have some issue on first attempt).

I’ll try reinstalling the new USSEP, if that doesn’t work I’ll try disabling some of the mods my crash logs are specifically naming one-by-one. If that doesn’t work I’ll try lowering that 2800 to something smaller.

I have 20+ GB of RAM still available for Skyrim to use, but there always seems to be this “hidden limit” that fluctuates a little where if I go over it it just doesn’t work. It happens more with FO4 than Skyrim for me but every now and then it pops up here.

Completely understandable, Fear. My list sits at about 450-460 at the moment. Good luck to you!

And trust me, I’m not exaggerating either.

I once did the “Nuke it all, and start from scratch” thing a year or two ago…with about 1500 then I spent something like 4 - 6 hours a day for over two weeks just reinstalling mods, sorting conflicts, messing with LO, and troubleshooting issues like the one I’m having now.

I REALLY don’t want to ever do that again lol

[Fear2288]

Reinstalling USSEP didn’t do anything, neither did disabling some of those mods mentioned in the crash logs and some of the new ones I installed.

Verified game cache - nada.

I may have a lead on an LO issue in regards to a Lux patch or two, I’ll have to see if the order is correct for them.

If it is, I’m sorta stumped.

I’ll have to resort to just cutting mods and getting that total number down to see if it’s the elusive “hidden limit” I mentioned…

The kick in the nuts though is that back when I last played in October - I had one of my most stable mod lists of this size ever. In a 300+ hour playthrough I think I CTD’d maybe 4 times…which is sorta unusual when you’re running 2000+ mods and you’re not the type that meticulously uses SSEEdit to manually create custom patches and resolve conflicts.

[Mugiwara]

Not sure whether you have one or not. But I will ask the question: Do you have a bashed patch? If so you may well need to run Wrye Bash again. One of the downsides of such large load orders is it could be anything.

[Fear2288]

Oddly enough, disabling the Innocence Lost Quest Expansion seemed to be the solution.

After disabling that, I was able to press New Game and create a character as normal.

Unfortunately it crashed shortly afterwards with the logs pointing to a NiNode issue, but I’ll try again later to see if it’s repeatable or just typical NiNode nonsense (random).

Weird that ILQE was the culprit. It does have a patch in its FOMOD for USSEP and the mod hasn’t been updated since the USSEP update, but ILQE is a jayserpa mod and he’s usually good about keeping his stuff updated/working…also no one on the mod page has mentioned this issue.

[xybolt]

Originally posted by Fear2288:

I REALLY don’t want to ever do that again lol

well, if you have a exceptional large mod list (there are not many that has a mod list with more than 1000 plugins), you should not have updated the mod. Many mods depends on USSEP and it happens that a "forwarded change" got reverted or moved because Bethesda made a change. I hope you're learning from this next time. What I do is to create another entry in MO2, put the update there and try this one.

Do know that USSEP has also some modifications in script files. It is possible that a mod is not interacting with these functions correctly.

Apparently you might have found a solution;

Originally posted by Fear2288:

Oddly enough, disabling the Innocence Lost Quest Expansion seemed to be the solution.

IIRC the mod comes with an USSEP patch. Perhaps it is worth to reinstall that mod?

Seems something is iffy with it as someone has left this comment in the above mod

I have been having problems with CTDs at start, the faulty file seemed to be the USSEP patch so after updating the USSEP mod it fixed. Hope it helps anyone having the same problems.

It is best to install crash logger and use their channel to narrow down the culprit if you are not able to read it or find the actual culprit.

[Fear2288]

Update:

It appears I finally found the solution.

Turns out, the problem was Lux.

In the Lux main mod FOMOD install you’re given an option to install a USSEP patch for the “previous” or “latest” version.

Then over on the Lux Patch Hub, there’s a USSEP patch as well for the most recent USSEP update (4.3.3 I believe).

I had selected the “latest” version in the Lux main install AND installed the USSEP patch from the Lux Patch Hub.

I assumed this wouldn’t be an issue because the Lux main mod had been updated recently and I figured the “latest” option was the same as the patch on the Patch Hub - so having both wouldn’t be an issue.

I guess this was incorrect, and despite having updated Lux recently, GGUnit hasn’t integrated the USSEP patch found on the Patch Hub into the main FOMOD installer.

Thus, running the installer again and selecting “none” for a USSEP patch and just using the one found on the Patch Hub seems to have resolved the issue with CTDs.

TLDR; don’t use the USSEP patch found within the Lux main installer, select “none” and then only use the USSEP patch found on the Lux Patch Hub.

[Ilja]

Originally posted by Fear2288:

TLDR; don’t use the USSEP patch found within the Lux main installer, select “none” and then only use the USSEP patch found on the Lux Patch Hub.

If files have same name, then one loaded last should overwrite the other.
If someone is worried about that and has installed patch with LUX main, in MO2:
- Open the mod folder in left panel.
- Optional ESPs.
- Move files from right hand side (Available ESPs) to left hand side (Optional ESPs.) File is no longer installed to your load order.

[mcbarker69]

Which version of Skyrim are you using? If you're using v1.6.640 (SE), the updated USSEP won't work. I believe it requires v1.6.1130 (AE) or later.

[Hypertext Eye]

Originally posted by Fear2288:

When you use 2800 total ESMs, ESPs, and ESLs you don’t really do that - you’ll be putting that together for a good two weeks before you even play the game (and it’ll likely still have some issue on first attempt).

When you have 2800 mods and everything is working, you never update anything ever again.

[Fear2288]

@Ilja

The problem must be that the Lux Main “latest” USSEP patch and the one provided on the Lux Patch Hub are not the same.

Despite Lux being updated somewhat recently, GGUnit must not have integrated the newest patch for USSEP into the FOMOD install.

They must have different names or something.

But what I can tell you is that by NOT installing the USSEP patch during the Lux Main FOMOD and just using the Patch Hub version fixed the issue and I went from crashing mere moments after creating a character to being able to put 10+ hours into a new game.


@mcbarker69

Not using any older versions. I’m using the latest version of the game.


@Hypertext Eye

Sure, you don’t touch it while you’re actively playing, but when I come back after a break I’m going to update existing mods, install new ones, and remove ones that didn’t live up to expectations.

Does it cause troubleshooting headaches like this?

Sure does, but I’m not going to deny myself whatever new fixes and content mod updates provide and keep playing a mod list that’s X months or years old.