RomanFox

Discussion topic: Better Grabbing by SkyrimThiago Wiki Link I've been using this in my own build. Vastly reduces frustration with grabbing and moving things around, and I haven't seen any weird compatibility issues with anything in the STEP v2.3 list.

I'm intrigued by the potential of using Light Limit Fix along with CS if implemented in the future.

Really appreciate you checking that out! Looks great now! R

Here's a video. I tested at the nodes near Lakeview Manor and Embershard Mine. Please let me know if there's anything else that might help.

Hello, all! This has mildly annoyed me for a while now, but I'm still getting what appears to be z-fighting on stone quarry nodes even though the latest version of HD Stone Quarry and Clay Deposit claims to have fixed it (way back in July 2023). It looks fine when that mod is disabled, but then those quarry nodes are super easy to miss. I'm asking here because I don't know whether it's something to do with another mod, and I'm also wondering if others following this guide are having the same issue. I noticed the same issue in the 2.2 STEP version, so this isn't a recent thing. If it helps, I'm using the Lightside version of Majestic Mountains. I redownloaded both the core mod and the MM update, and was sure to pick the appropriate version when I installed it. If necessary, I can try to record video.

Verified working, didn't even have to regenerate LOD. I always appreciate your assistance!

Thanks so much for the help! R

I've seen this mildly annoying issue brought up before, but it was a while back now. I'm running STEP v2.3 and following all instructions in the guide with respect to grass cache and LOD. Wherever this one clover-like leaf thing shows up in the grass, one point of the model is stretched weirdly until I get close to it [See Imgur album--screenshots were taken just outside Bthardamz, but it happens everywhere I see that grass object]. This may be something to do with the Cathedral Landscapes mod, but that mod's page has had comments disabled. Wondering if anyone else is seeing this same thing or has any new advice on tweaking it. Edit: I'm using an RTX 3070 with updated drivers. This has happened whether I'm just using the grass cache with no grass LOD generated, or using both cached and LOD HD grass. Might I need to regenerate grass cache?

Hello, everyone! I hope I'm in the right place for this. I just installed this mod with the recommended selections from the 2.2 guide version (notice the Stealth Skills Rebalanced boxes are ticked), and LOOT threw the following error in aMidianBornContentAddon_SSR_Patch.esp: So I installed the Basic version of Stealth Skills Rebalanced (which isn't listed in the guide), and found that its main ESP is named Stealth Skills Rebalanced_COMPLETE.esp. Am I missing a patch somewhere? I didn't see one for aMidianBorn and SSR on kryptopyr's patch hub page. Is there something additional I should be doing to get this mod to work with STEP v2.2, or should I not be ticking the SSR boxes?

I sent you a DM regarding unavailable older mods.

I was able to start a new game and play around in the Ratway for half an hour or so. No crashes so far -- keeping my fingers crossed. Thanks again to both of you for helping me to get everything up and running again! And I am most definitely looking forward to a new guide version. For now, though... I'm not touching anything else or taking any more Bethesda updates.

@Mousetick Holy cow, what a find! I can at least get to the main menu now. I'll try and play some later on today and see what happens. Thank you both for all your help! R

@ButchDiavolo Great thought! But I had already deleted _ResourcePack.bsa and _ResourcePack.esl based on other posts I saw about these. I hadn't seen anything about MarketplaceTextures.bsa, but I deleted this as well per your suggestion and that hasn't fixed the problem. I assume the Papyrus logs would show up in \Documents\My Games\Skyrim Special Edition\Logs\Script. I do see a couple of these from yesterday when I was disabling/enabling mods for testing (there are a lot of "missing file?" and "cannot be initialized because the script no longer contains that property"), but even though I've enabled the logging flags again in Skyrim.ini, I haven't been able to get it to generate any new logs today after something like 9-10 launch attempts. There are logs showing in the SKSE folder under the My Documents path for SSE, but of the two that mention Papyrus in the filename, neither is reporting any obvious failures. I don't see any .manifest files in my current Creations folder, but in the old version of my game folder that I was able to pull from my hard drive backup, there are 74 files that are dated 10/28. Not really sure what to do with these. I'm kind of at a loss here. Might be better for my sanity just to put Skyrim on the shelf for a while until the team comes up with a new guide that supports the current version.

So, I've been playing with this some more throughout the day today. I wanted to rule out any possible registry shenanigans, so I completely uninstalled the game and reinstalled it through Steam. Let 1.6.1130 download all AE CC mods. Applied all files from the 3 documented download_depot commands for 1.6.640. Cleaned vanilla masters. Reinstalled freshly downloaded SKSE, ENB, and all STEP patches (being sure not to download any of these mods from Nexus dated after the 1.6.1130 update. Still the exact same treatment as before: Launch skse64_loader > black screen > intro music plays for about half a second > no Bethesda logo > CTD. Looking through logs, I've seen a bunch of "Found unhandled type: (PlayerCharacter*)" in CrashLogger.log. Actual crash logs look pretty much exactly like the one I posted previously. I did try to enable Papyrus logging as you suggested, but I'm not sure what file I should be looking for after enabling it. Currently, I have the entire STEP 2.2.0 guide installed in MO2. Entire groups 6 and 20 are disabled. I tried enabling group 6 mods in groups of 10, and I could at least get to the main menu with any group of 10 except for Realistic Water Two and Security Overhaul SKSE - Gems Patch - The Cause Chests Secured (I did merge the Ayleid lock model file as instructed). If I enabled either of those mods by themselves or larger groups of mods, it's back to CTD before the Bethesda logo. What a mess. Wish I'd never taken this update.

Hello, everyone! I hope I'm in the right place here. The STEP guide has spoiled me. I can't play Skyrim without it. I'm sure this is a familiar story, but my game updated to 1.6.1130 and of course broke many of the STEP mods. I followed several guides on downgrading back to 1.6.640, but I still can't get the game to load to the main menu. I launch from MO2, the screen goes black. After a bit of loading, the menu music plays for about half a second and then... CTD. First line of crash log shows: When I first installed v2.2.0 of the guide (this past August), I kept all the archives I downloaded and have not updated any since before the update. So as far as I'm aware, I shouldn't have any mods that were updated after December 5 or so. What I've tried: Updated GPU drivers Ensured Windows is up to date Deleted all files from the game folder and let Steam reinstall 1.6.1130 as well as all (official) creations in my library Overwrote game folder using files obtained from download_depot commands Also tried overwriting files from the Skyrim root folder in a hard drive backup that was made prior to the update Completely wiped my MO2 profile and followed the guide again from scratch, including re-running BethINI What I'm running: Skyrim v1.6.640 SKSE v2.2.3 ENBSeries v0.484 (have also tried 0.499, both versions worked pre-update) I am able to successfully load to the main menu if I disable all mods from the 06-Models and Textures and 20-Patches groups. It's been difficult testing this by disabling one mod at a time because of the number of mods in 06, and also because 06 and 20 are so interdependent on each other (LOOT screams at me a lot when I start disabling things). I'm willing to accept that I could be missing something incredibly basic and stupid. However, one thing I'm not good at is deciphering crash logs. Would anyone be so kind as to take a look and try to help me zero in on this issue? Pastebin Regards, R