cmaesing

Just an idea: Assuming you’re launching from within MO2. Are you launching SKSE? I had it once in the past that I launched the standard Skyrim via MO2, and then was wondering why nothing worked. Just throwing in a quick thought. Good luck!

Thanks yet again @Hannibal139. I really appreciate you taking the time on this one little issue of mine. Will give that definitely a try today! I did actually have a look at all my butterfly mod pages before starting this thread. But all of them didn't show any bugs listed (or only unrelated ones, if I remember). I'll pm the mod author of THAT texture dds file which my new butterfly friend always uses (it comes from https://www.nexusmods.com/skyrimspecialedition/mods/37302). Of course I could delete that dds file - in which case a standard texture is being used. With that, however, buried somewhere in one of the default Skyrim files, I find it easier to work on the file that this mod provides. Shall revert here when I know more.

@Hannibal139 Wow, thanks for finding that out! Let me check and see if it works / resolves itself by disabling those two mods. UPDATE: Playing around with my 4 butterfly mods (disabling this or that one) didn't do the trick, unfortunately. I have identified the type of butterfly that always appears, though. So my hope is that I will now create a blank / transparent dds file, rename it so it matches the critter's name - and then technically be there, but that I simply won't see it anymore. Will keep you posted.

Thanks @Hannibal139 for your input. Had a brief look, but nothing came up. Will take some more time later today, and revert here if I manage to fix it for good.

I would guess this could have to do with Skyrim Better Roads @ https://www.nexusmods.com/skyrimspecialedition/mods/2640 (maybe unlucky install, maybe a load order issue). That mod adds improved mountain paths similar to the geometry you're looking at here. Not sure if this IS it, but worth a shot. Good luck!

I came the other day out of the cave after the Clavicus quest - and at that moment had a butterfly stuck on me. And the damn thing just wouldn't go away! https://i.imgur.com/CyPbHIi.jpg Here is what I have tried so far: Fast travel, wait, sleep, swim through river. The butterfly remains. Leave SSE completely, restart and reload the savegame. The butterfly remains. Console command player.dispelallspells. No effect though, the butterfly remains. Console command to disable the butterfly. But when I click on it, my character's name and details appear. So am not able to disable the butterfly itself. Via console command change into vampire and back into normal form. While that DOES get rid of the butterfly once I am in vampire form (and remains gone once I change back), after some time the butterfly reappears. And I haven't been able to identify any action or script that would trigger this. My butterfly mods are (in this load order; don't have any other insect mods): 1. Butterflies Land True (has esp) 2. Rally's Butterflies Moths and Torchbugs (no esp) 3. Butterfly Improved (no esp) 4. Butterflies Unchained (has esp) So I unchecked the esp from #4 - no change, the savegame loads, and the butterfly is still there. When I uncheck the esp from #1, the game ctds as it is about to finish loading. So my guess is that has something to do with how the 1st interacts with SOME mod in my load order. That said, my setup is highly modded, based on the Northern Experience guide, but with lots of personal addons (MO2 managed, 250 ESMs and ESPs, 420 ESLs or ESL flagged ESPs). Luckily, the game is wonderfully stable so far - except for this one issue that came up now. Since the butterfly always looks the same (seems to be a Luna moth), and since it always appears on the same position in relation to my body (mid height, forward right-ish ... that's where it then flies around), I would guess (but am not sure) it's a script issue from another mod. Maybe Quick Light, maybe Bandoliers. Will check those out a bit more in detail. I should mention that I did ask about this on the Steam SSE forum yesterday @ https://steamcommunity.com/app/489830/discussions/0/3196989419235765412 ... And while folks were able to kindly direct me towards the player.setrace command, I thought I'd ask in a different forum to see if anyone has any other idea. Thanks!

Apologies for necroing an old post - but I prefer having solutions in the same place vs others having to criss cross over several related forum entries. That said, I today came across the same issue (albeit in a different location). And after searching the net for an hour or so came across the solution that did it for me: As rickerhk has pointed out above, under the game's display settings, I accidentally had switched from "large" to "small" textures. Going back to "large" textures resolved this immediately. Hope this helps anyone else who might encounter the same problem.

@avariel002 Please read my post on the top. That explains step by step. Good luck!

Seems like dwelling on semantics to me. But if it makes folks happier: I am 99.9% positive the *workaround* presented here is the only viable one. Cheers.

I am 99.9% positive the solution presented here is the only viable one.

Thanks for your reply, BlueGunk. I did give it a try, but to no avail. Free space also isn't an issue - have a couple of 100 GBs left on my hd. I have left it for now out of frustration - and might return in a few days. My guess is I have to go back to whichever save is not corrupt. Praying it's not too many hours back into gameplay. Will revert here if I ever get it resolved.

Awrite, gents. After playing Skyrim (later Legendary, now SE) for some years, I recently thought I'd go for a final playthrough before allowing it to retire for good. While I would not call myself an IT or technology expert, I have been modding the heck out of the different Skyrim versions for some time - and of course also this time. Used the Nordic Guide as "guidance" for an install. And even with a heavy mod list of 250 esps and 200 esls/eslified esps, the game is stable (an un-reproducable ctd every few hours ... a blackface that can be fixed via CK, but that is pretty much it). Installation time of about two weeks paid off here. That said, I started encountering the absolutely frustrating "ctd on save" bug. Having spent hours of searching and reading the past two days, I think I have tried pretty much all fixes which are being discussed or recommended as viable: Fix savegame with ReSaver. This actually helped me earlier in my playthrough with the same issue - but interestingly enough, all my current savegames do NOT show any issues here - so nothing to fix for ReSaver.The player.kill solution.The coc qasmoke/pcb solution.Disabling and unchecking (from plugin list) iNeed.Adjusting the Papyrus section in skyrim.ini to iMinMemoryPageSize=1024 and iMaxMemoryPageSize=3072. This actually helped earlier in my playthrough with the same issue - but the issue keeps coming back (values are still set as stated here).Moved most except for a handful of savegames into a separate folder, to have a short list of savegames.My current playthrough is about 50h into the game, the latest savegame (ess-file) size is at 17 mb. I can successfully save an older savegame (went back to a very early one, say 5h of gameplay). But I haven't tried to find where the cutoff is. The latest one I tried is 15h of playthrough back - and still results in the ctd. A final word on the save behaviour: When I load my latest savegame and try to (hard or quick) save, the game starts the actual save process. It does not immediately ctd. The ctd happens about 10-15 seconds into the save procedure. After the ctd, I will then find the skse-file properly created. It seems the issue is with creation of the ess-file: Here I only see an ess.tmp file with 0 mb file size. Am on 1.5.62 with SKSE64 2.0.12. Deliberately haven't updated yet, as I have too many mods relying on these versions (and I am afraid to break something unnecessarily). Thanks for any insight!

I know this is the Skyrim (not Skyrim SE) forum. Still hoping that someone here might know a solution, hence replying to this thread. Cheers! ===== Awrite, gents. After playing Skyrim (later Legendary, now SE) for some years, I recently thought I'd go for a final playthrough before allowing it to retire for good. While I would not call myself an IT or technology expert, I have been modding the heck out of the different Skyrim versions for some time - and of course also this time. Used the Nordic Guide as "guidance" for an install. And even with a heavy mod list of 250 esps and 200 esls, the game is stable (an un-reproducable ctd every few hours ... a blackface that can be fixed via CK, but that is pretty much it). Installation time of about two weeks paid off here. That said, I started encountering the absolutely frustrating "ctd on save" bug. Having spent hours of searching and reading the past two days, I think I have tried pretty much all fixes which are being discussed or recommended as viable: Fix savegame with ReSaver. This actually helped me earlier in my playthrough with the same issue - but interestingly enough, all my current savegames do NOT show any issues here - so nothing to fix for ReSaver.The player.kill solution.The coc qasmoke/pcb solution.Disabling and unchecking (from plugin list) iNeed.Adjusting the Papyrus section in skyrim.ini to iMinMemoryPageSize=1024 and iMaxMemoryPageSize=3072. This actually helped earlier in my playthrough with the same issue - but the issue keeps coming back (values are still set as stated here).Moved most except for a handful of savegames into a separate folder, to have a short list of savegames.My current playthrough is about 50h into the game, the latest savegame (ess-file) size is at 17 mb. A final word on the save behaviour: When I load my latest savegame and try to (hard or quick) save, the game starts the save procedure. It does not immediately ctd. The ctd happens about 10-15 seconds into the save procedure. After the ctd, I will then find the skse-file properly created. It seems the issue is with creation of the ess-file: Here I only see an ess.tmp file with 0 mb file size. Am on 1.5.62 with SKSE64 2.0.12. Thanks for any insight!

If not already done, you might want to lock your FPS to 60. Afaik, going beyond triggers the behaviour you are describing.

Probably some cloud save functionality turned on in Steam.

RESOLVED: Found the culprit: It was the Unofficial Material Fix - Embers HD compatibility patch @ https://www.nexusmods.com/skyrimspecialedition/mods/21027?tab=files It was overwriting - amongst other campfire nifs - the aforementioned one. Have reverted it back, and now looks normal again.

Ok, I have nailed this down to the default fire as e.g. used for the cooking stations in any camp (be that Imperial or Stormcloak). Campfire01LandBurning [MSTT:00035F47] in skyrim.esm, per SEEdit its model is "Clutter/WoodFires/Campfire01LandBurning.nif" Here is a picture of another cooking station that was added through a mod, and does not have the issue. But then again, the fire is a slightly different one, as not surrounded by stones. https://i.imgur.com/kUCvGfQ.jpg No solution yet, though.

Crash on start often means that a file in the load order isn’t active (or not even present) that is required by another one. Have a look if anything is missing on that front.

https://i.imgur.com/rRLQ5Tk.jpg I have no idea where these are coming from. Am at the end of the Nordic Skyrim guide @ https://www.nexusmods.com/skyrimspecialedition/mods/12562, am following their esp order (i.e. nothing rearranged by LOOT or so), but have no idea how to get rid of this. Reinstalled ELFX, also Cinematic Fire Effects, to no avail. I do have Campfire and related mods installed for some time already - they all worked fine. So guess the culprit is some other mod. This does not happen with other light / fire sources (e.g. giant fires). Thanks for any insight!

Glad you sorted it out. Thanks for coming back - might help someone else in the future!

My guess: You have to go back to your pre merge (and before those new mods) state and load an earlier save. As a quick input, what I always do before any major mod changes (that includes merges, or bigger new mods to be included) I make a copy of my entire Skyrim folder, plus extract my load order. That way I can always go back easily in case something gets messed up. I normally keep up to three such copies, and then delete the oldest folder as a new one comes in. Sorry, but given your rather extensive load order this is all I have. Someone else might know more.

RESOLVED: Copy pasting here a reply from this issue’s initiator ThelebKarnaa, by which he commented on the same post in the mod ‚No Snow Under the Roof‘: „Seems the issue (Blue farmhouse, Mine Entrance, some rocks, etc in snowy landscapes) is caused by mod(s) disabling snow masking. Over on Majestic Mountains I learned to set in SkyrimPrefs.ini: "bEnableImprovedSnow=1" to "bEnableImprovedSnow=0. Seems this setting isn't really important if you're running snow/landscape mesh/texture replacers anyways. Also to note you want to be sure benableProjecteUVDiffuseNormals is set to "=1" and not "0" (important).“ In my case, both bEnableImprovedSnow and benableProjecteUVDiffuseNormals were set to "=1". I switched bEnableImprovedSnow to 0, et voilá! All good again.

For me, the issue comes down to some shadow setting, and not a missing texture. That is what it looks kime at least - just not able to nail it down (yet). Here are three examples in Dawnstar (with and without direct sun, so the difference is visible): https://i.imgur.com/6iwNksK.jpg https://i.imgur.com/M4ZUTtm.jpg https://i.imgur.com/j9SgNj1.jpg Addendum: After deleting https://www.nexusmods.com/skyrimspecialedition/mods/20102 and re-creating my smashed patch (via MatorSmash), the stone issue seems to have receded to a certain degree, but remains. I think top textures of stones no longer are bugged, but side textures still are. The wooden mine entrance remains bugged as well for now.

I am having the same with the mine entrance and some rocks. Supposedly (the rocks) from Majestic Mountains. But also not been able to rectify. Did you have any luck?

Thanks for chipping in, gents! (Yet another) lesson learnt.