Bleak Falls Barrow glitches

[Ugh]

Still trying to sort out problems for my potential LotD set, and the latest glitches to stump me both occur in Bleak Falls Barrow, hence its mention in the title.  Ignore the FPS counter in the corner; I didn't have my frame limiter set on when I took these pictures, and the glitches are there regardless of the FPS limit.

 

The problems (in picture form): http://imgur.com/a/jXGPP

 

My load order: https://modwat.ch/u/Ugh

 

Main texture packs I used during this test were Noble Skyrim and Optimized Vanilla Textures.

[allsunday]

If turning on ENB is negatively effecting both character and object behaviors... the only solution I can come up with is to replace your enblocal.ini file with... I dunno, try the enboost version from Skyrim Nexus or just use the original one from the ENB you downloaded.  Heck, just download a new ENB that you like and replace all the files and see what happens.  Normally before doing any of this, I'd backup my Skyrim folder though... all of the files and folders besides the Data Folder should be fine.  The Data folder is only where your mods go and there are only a very small handful of ENBs that actually put files into the data folder -- but you would know if the ENB you're using did or not, wouldn't you?

If one solution does not work, place the original files you backed up back where they belong and try, try again.

 

This is just a guess because only the settings on the enblocal.ini file can drastically have this much of an effect on the game's behavior.

 

I'd also recommend running FNIS again.

[Ugh]

No luck.  I noticed the problems cropping up on another profile as well, so I tried a re-install, but the problems remain, having been joined by some objects floating around in the air (skeleton bits, mostly, during the part where you fight the giant spider), and enemies being a bit more immobile than usual.  Not that the enemies can't move, mind you, but that they're moving at a reduced speed, and trying to throw their attacks out earlier, as if they occasionally think my character is further forward than he actually is. This is just getting really weird now.

[Ugh]

So it's been like a week since I posted in this topic, and I ended up nuking my Skyrim install and starting again.  I'm just posting in here to say that I did find the cause for the buggy Dessicated Corpse mesh; turns out USLEEP accidentally sent out a corrupted version of the mesh with their last update, which was fixed quickly in the SE version, but went unnoticed on vanilla because, surprise surprise, everyone who noticed it was using an ENB like I was, which made the problem more blatant.  Just spreading the message for anyone else who noticed the bug in their game.

[Ugh]

Ok, forget I said anything, because I've narrowed down the culprit considerably while reinstalling and testing everything.  Turns out my draugrs going completely screwy has something to do with either Legacy of the Dragonborn itself, or one of the compatibility patches.  As soon as I activated those, the screwy physics glitches return once I kill a draugr with a power attack (it occasionally took a couple kills for the bodies to start glitching out, but it was repeatable).  This also affects skeletons, including one in particular placed down by Morrowloot near the exit that bugged out much wilder than the skeletons or other dragur, bouncing around the room wildly and nearly un-selectable before glitching out of bounds entirely.  Not only did re-running FNIS not work (though it did take a few more dragur deaths for the glitching to kick in), but this seems to have corrupted my Skyrim install itself, as a different MO profile with only USLEEP, SkyUI, MFG Console, and Crash/Bug Fixes exhibited the same behavior, even without anything FNIS or LotD related.

 

Load order, as usual is here: https://modwat.ch/u/Ugh  (Everything, I should note again, was pretty much in working order before I activated LotD and it's patches; I actually had them downloaded and ready to go a good day or two before I got around to activating them).

 

So, short of nuking my install AGAIN, how would you guys go about troubleshooting this particular issue?