koounekosan

Okay, I have been looking for a solution for weeks now, having taken a break from FO4 for a bit to revisit Skyrim. Changing my character's height was one of the best parts. It really made it feel like I was looking through someone else's eyes. Naturally, with setscale, you can achieve the same result in fallout, but it makes some things downright goofy. I don't care so much about the terminals being a little high or low. That's immersive, looked at the right way. But when I point my gun at something I want dead, and the point of aim is no longer associated with the sights of the weapon? It loses my interest instantly, and I can't seem to find a mod or setting to tweak that will reposition the scope/iron sights to take the change in height into account. Hip-shooting works fine, and I have to assume everything in 3rd person works, but I would prefer to remove 3rd entirely. Please tell me there is a simple aim-down-sights solution I just managed not to find by not using exactly the right searches.

Heuugh! Finally found the problem. Wasn't MO or Skyrim, or even drivers! It was a stupid Win10 'feature'. Found the solution at: https://steamcommunity.com/app/215530/discussions/1/523897277921744787/ If anybody else has a similar problem running Skyrim through Mod Organizer, and you're lucky enough to find this before you spend a whole week trying to get things working, open Task Manager and disable TabletInputService I guess I need a Solved stamp now?

Okay, so nope. Still crashing when I try to run through MO.

Well, it seems the driver update fixed at least Vanilla. Ran for 45 minutes without a crash or stutter (and holy crap! I almost couldn't tell I wasn't using Noble Skyrim with my settings optimized... at least, not until characters got involved... so edgy)

Ohh...kay... May have found a potential cause for problems. GeForce Experience seems to have uninstalled itself, secretly, silently, and thereby implanting a faulty nvd3dum.dll in place of what I assume was a working one.

Aaand no change. Total, absolutely clean reinstall, managed to play for ten minutes, and I was back to desktop. No crashdump, no papyrus (because I forgot to enable in MO skyrim.ini). No SENSE! Except now skyrim crashes on its own, without the help of MO.

alright, everything uninstalled, backups restored/steam-verified. The testing recommences.

Got, and did, all that. Even watched the video. May not have done in the right order, however. Re-attempting now. And I intentionally left out USLEEP, since it wasn't part of the vanilla test-mule that was working. It isn't Skyrim that is crashing it's Skyrim (SKSE) when run through MO. Only when run through MO. I've seen other folks that have had this problem, all of them over a year ago, but no mention is ever made as to what they did to fix their problems.

Aaand it looks like I ran out of space before the end. Too tired to figure out what's missing. Hopefully by the time I get back from work this afternoon, you wonderful nerdy folk will have magicked up me a solution that's easy, and also fed my cat. Good night, Internetizens.

Since this is a common issue, I figured I would see if there were any helpful helps out here on the 'ol interweb afore I went 'n bugged folk about my bugged setup. So, I only recently got back into playing Skyrim, having lived in a truck since before the first DLC was released (although I think SKSE was already out?) which naturally means I've only just-as-recently started trying to mod Skyrim. Followed the organic approach: 1. Figure out where to get and how to install mods; bork Skyrim 2. Learn about NMM, un-bork Skyrim after reading helpful helps from other folks. 3. Re-un-re-un-re-bork, total-reset, run stable for a few weeks. 4. Finally decide to make the switch to the big-boy Mod Tool. Wipe everything off, and reload with MO. So now, I've been trying to get skyrim to run with Mod Organizer. It will! For almost exactly ten minutes. As an experiment, I loaded up my backed-up just-out-of-helgen never-modded, pre-any-DLC generic troubleshooting save from the desktop-launched vanilla skyrim button. Ran perfectly for over an hour? I didn't time it, but I know it was a good long time. So I figured I'd try loading up in MO and continuing from that point. Ten minutes: Desktop. My ENTIRE Load Order(no spoiler block because I'm a sadist :wink: ): Skyrim.esm Update.esm Dawnguard.esm HearthFires.esm Dragonborn.esm HRTPs1,2,3.esp I even turned off MO's BSA management, since it was injecting stuff like partial SkyUI fragments, and I figured that might be a bad thing. Everything I have installed/active, but not loaded (Hope I remember the instructions for spoiler blocks for this one... Nope, had to look it up.) That entire list, and more (I didn't think to take a before/after list-shot for comparison, but I know I had over 200 files in my load order at one time) were working as flawlessly as a community project can... when nobody is talking to anybody else in the neighborhood. I had over 200 hours of stable laytime in over the last month (as long as you don't count having to re-start my PC to re-load the game as un-stable). I'd like to be able to provide SKSE's most recent crashdump, but MO is somehow preventing WriteMiniDumps=1 from functioning, CrashFixPlugin did output a log file, but it's one line and says "This is useless", and though I'm going to include it, I doubt my last Papyrus log will be useful.