PLEASE READ! I'm at my wit's end... magical -forcesteamloader bug...

[Krit-hit]

Full Load Order: https://pastebin.com/W7D9Dw1x

 

Ever since I made my mod list, my Skyrim has had a bizarre bug where it launches windowed and works as long as it is minimised on the taskbar (music works, game loads up to main menu etc.) but as soon as I tab into the game, it completely freezes up. Now there is (or rather was) one way to fix this bug : by typing "-forcesteamloader" in the SKSE arguments section. 

 

It worked normally then, but with some caveats - every time I start the game, the first time it will encounter the freeze bug even if -forcesteamloader is applied in arguments, and then it must be closed with task manager (Alt+F4 doesn't work against the freeze bug), and then -forcesteamloader must be removed from SKSE arguments and reapplied. Only then it will work again. You can't preemptively remove and add -forcesteamloader to skip the freeze one time, it must be triggered once between each play session before the "magic spell" can work.

 

It was annoying, but ultimately playable, so I kept playing like this for well over a month. Over the course of this time, I did try some things to find what causes this, and hopefully find a fix. I was only semi-successful, I'll share what all I tried in a bit. But why I'm here now is because yesterday, what I always feared at the back of my mind, came to pass. After its long month of service, even -forcesteamloader finally lost its magical properties. No matter how many times I reapply it now, I still get the freeze bug, rendering my Skyrim unlaunchable. With my last shred of hope, I now share all that I have learned of this otherworldly phenomenon, just in case anyone here knows of a possible solution.

 

1. The game stays frozen when it happens, it does not crash even if I leave it on for a long time. Thus, no crash log exists.

 

2. I have attempted to use ProcMon tool to see if it can figure anything out. But if I stay tabbed out, it just lists off a bunch of different mod esps, a list that lengthens and shortens at its own whims with every second. And if I tab in, the game freezes and ProcMon simply states "No Activity".

 

3. I have attempted to disable all my mods and then try launching the game with only a few mods at a time, to see if I can locate the culprit. Now this is where it gets truly bizarre, but I'll try to explain as best as I can. I kept enabling mods a few at a time, until I found one that triggered the freeze, so I disabled it and went to the one after it. It was still working, so I went to the one after it and so on. But then I found another mod that triggered the freeze. No problem, I disabled it and kept going, until I found another one. Now here I wanted to test something, so I instead tried keeping the "guilty" mod enabled but disabled another of the "not guilty" mods, just as a test. And sure enough, the game launched even with the previous "culprit" enabled. There were no problems with any of these "guilty mods" in gameplay either, nothing crashed or bugged out.

 

It's like, after a few mods, Skyrim simply begins to demand a "blood sacrifice". This sacrifice can either be the last mod you enabled, or one of the previously enabled mods, but not just anyone. You need to try disabling one, then checking if the sacrifice is accepted. If not, the freeze bug happens again. In that case, you need to re-enable that sacrifice and try sacrificing something else instead, until you find one that Skyrim deems worthy. Then you can keep playing, and even add on more mods on top of that if you want, so it's not like it's hitting a hard limit. It's simply that after a few, it stops you and asks for an offering.

 

4. These sacrifices can be any kind of mod, there is seemingly no connection between them. The very first of these that I discovered was Sentinel (Armor Mod). Another was JK's Fort Dawnguard (Location overhaul), and another was Embers XD (Fire vfx redone), and another was Katana (follower mod). But they staved off the freeze bug nonetheless, and at no fault of their own. I can still run the game with all of these active and working perfectly, it's just that some other equally randomly-chosen mod must pay the price in their stead. Hell, sometimes, even the opposite was true - ADDING an extra mod would somehow tip the scales back into that "golden zone" that launched the game.

 

Finding this golden zone was always a painful game, but I didn't always have to play it. For such was the power of -forcesteamloader, may it rest in peace.

 

5. It just kind of happened one day, with no hints of preambles. -FSL just... stopped working. So I tried doing it the old-fashioned way again, uninstalling a bunch of mods trying to locate the "sacrifice", and I found one. Game technically launches with it, but only once. The next time I try to launch it, the freeze bug rears its frightening head again. And now a new sacrifice must be found.

 

Of course, like all things in this arcane web of code, it too has its own cryptic laws and exceptions.

 

6. I have discovered and saved at least 2 load orders that ALWAYS result in the game launching. Don't even need to reapply -FSL. Here they are -

 

Magic Load Order 1: https://pastebin.com/C7wQCK11

Magic Load Order 2: https://pastebin.com/TtRdfBMQ

 

Unfortunately, there are two issues with this. For one, these load orders may get me to the main menu, but they still crash the game when I try to load up my save file. Too many important mods missing, perhaps? And secondly, they only work once. If I close MO2, and then open it again to relaunch Skyrim, these magic load orders yield to the freeze bug too. I can still get them working again by reapplying the exact same load orders through the "Restore backup" feature of MO2 though. I suspect something happens between closing and reopening MO2 that reorganises something in these load orders, causing them to lose that special sequence of files that can defeat the freeze bug. But that's just my speculation, I'm just as blind to the inner workings of MO2 as I am to Skyrim's.

 

So this is all I've got, I think. I'll add more details if anyone has questions. And I'd love to hear ANYTHING you may know about this, however tangential. All knowledge can potentially be useful. I'd also like to thank you from the bottom of my heart even if all you did was read these lunatic ramblings to the end. 

 

Just remember, my friend - magic is real. And it's not locked between the pages of some flesh-bound tome, or sizzling from the tip of a wand hewn from the earliest trees. No, magic resides solely within the code of The Elder Scrolls V: Skyrim, and it is as raw and untameable as it used to be during the dawn of time.

[traison]

22 minutes ago, Krit-hit said:

Ever since I made my mod list, my Skyrim has had a bizarre bug where it launches windowed and works as long as it is minimised on the taskbar (music works, game loads up to main menu etc.) but as soon as I tab into the game, it completely freezes up. Now there is (or rather was) one way to fix this bug : by typing "-forcesteamloader" in the SKSE arguments section.

 

This is placebo. All that argument does is force SKSE to assume you're running the Steam version of the game. This option is only used once, and that is when determining whether to inject the SKSE dll, or to terminate SKSE.

 

Launching windowed could be caused by several things:

1. Something goes wrong in window creation.
2. Something goes wrong in DX device creation.
3. Something else steals window focus.
4. The Skyrim ini files are read-only or otherwise inaccessible, like for instance in a OneDrive folder.

28 minutes ago, Krit-hit said:

It worked normally then, but with some caveats - every time I start the game, the first time it will encounter the freeze bug even if -forcesteamloader is applied in arguments, and then it must be closed with task manager (Alt+F4 doesn't work against the freeze bug)...

 

Alt+F4 only sends a message to the WndProc. If the message pump is frozen, or otherwise busy, it can be delayed. Its technically also voluntary for an application to do anything with this message, and its functionality can be changed.

 

31 minutes ago, Krit-hit said:

...and then -forcesteamloader must be removed from SKSE arguments and reapplied. Only then it will work again. You can't preemptively remove and add -forcesteamloader to skip the freeze one time, it must be triggered once between each play session before the "magic spell" can work.

 

Placebo.

 

31 minutes ago, Krit-hit said:

I have attempted to disable all my mods and then try launching the game with only a few mods at a time, to see if I can locate the culprit. Now this is where it gets truly bizarre, but I'll try to explain as best as I can. I kept enabling mods a few at a time, until I found one that triggered the freeze, so I disabled it and went to the one after it. It was still working, so I went to the one after it and so on. But then I found another mod that triggered the freeze. No problem, I disabled it and kept going, until I found another one. Now here I wanted to test something, so I instead tried keeping the "guilty" mod enabled but disabled another of the "not guilty" mods, just as a test. And sure enough, the game launched even with the previous "culprit" enabled. There were no problems with any of these "guilty mods" in gameplay either, nothing crashed or bugged out.

 

Reasons for this:

1. Plugin limit.
2. stdio limit.

33 minutes ago, Krit-hit said:

It's like, after a few mods, Skyrim simply begins to demand a "blood sacrifice". This sacrifice can either be the last mod you enabled, or one of the previously enabled mods, but not just anyone. You need to try disabling one, then checking if the sacrifice is accepted. If not, the freeze bug happens again. In that case, you need to re-enable that sacrifice and try sacrificing something else instead, until you find one that Skyrim deems worthy. Then you can keep playing, and even add on more mods on top of that if you want, so it's not like it's hitting a hard limit. It's simply that after a few, it stops you and asks for an offering.

 

You're chasing ghosts. You have bigger issues than mods loading or not loading. Keep the load order at whatever works for now, and focus on finding the real problem.

 

34 minutes ago, Krit-hit said:

It just kind of happened one day, with no hints of preambles. -FSL just... stopped working.

 

Despite what you may want to think, it never worked.

 

35 minutes ago, Krit-hit said:

I have attempted to use ProcMon tool to see if it can figure anything out. But if I stay tabbed out, it just lists off a bunch of different mod esps, a list that lengthens and shortens at its own whims with every second. And if I tab in, the game freezes and ProcMon simply states "No Activity".

 

The procmon event list can not get shorter randomly and on its own - if an event has occured, it can not "un-occur". As far as I know procmon has no "no activity" printout either.

 

37 minutes ago, Krit-hit said:

And I'd love to hear ANYTHING you may know about this, however tangential.

 

Alright, here goes:

1. You've downloaded something other than ProcMon from Sysinternals (Microsoft). That's probably an issue, and is most likely hostile.
2. You have a cracked version of Skyrim.
3. You have OneDrive enabled, and its messing with Skyrim's access to its ini files.
4. You're hitting some limit when loading plugins, be it the plugin limit or the stdio limit.
5. You have some malfunctioning or overly excited anti-virus solution that's messing with file access.

[Demonwise]

Jeezes, man. That... is... weird. It almost sounds like there is an issue between your gpu and your OS. Like the act of changing focus to and off the window of the game causes a hiccup in the system that causes the game to hang. 

 

I think I have encountered this before with other games before. I think the real issue is why can't your game just start on its own in fullscreen or borderless? 

 

So, before I go any further, I just want to say that I don't even have a clue how to fix this so I'm sorry. That said, perhaps if you're willing to bear with my ramblings as well perhaps I might stumble upon somthing that could help you.

 

Some thoughts. Are you using ENB? If not then just skip this. Otherwise, I might suggest removing that entirely just for debugging purposes. I bring this up because ENB has its own display settings and other stuff that overwrites the game's settings. Removing ENB might shed light on whether or not some of it's settings were borking things up.

 

Next thing I would ask is, have you tried deleting your ini files from your My Documents folder? Before you do, back them up. Sometimes for whatever reason this 'settings' can get borked. The game will auto-generate them if they aren't there so it should be safe to delete them and then try to load Skyrim again. Doing so will make the game run and default/stock settings. That said, if you have custom arguments in any of these files required for mods then you will need to re-add those to the files eventually to make sure the mods work. 

 

Generally, my understanding is that when the game crashes trying load a save then there is likely some soft-dependency for a mod that is missing or in the wrong order. If the game crashes before getting to the main menu then, as I recall, that is more of a missing hard-dependency requirement for one or more mods. In either case, some classic hardcore debugging will be necessary to make sure that every mod has every dependency and that they have the right versions. Some of the dependencies may have updated past the mod requiring it or vice versa making them incompatible and also making both a liability for your modlist and load order.  

 

I hope some of this experience/advice proves helpful. I really do. Frick, man, this is kind of why I haven't seriously tried to get back into Skryim. I spent so, so many dozens if not hundreds of hours getting a 90% functioning modlist back in the day and loathed to touch it thereafter for years. Now that so much has changed, I just can't bring myself to put that level of effort into what will likely just amount to a jerk-off sex simulator. 

[Krit-hit]

Hi, so first of all, thank you both for replying with legit advice. I really wasn't expecting anything at all!

 

@traison I originally arrived at the "-forcesteamloader" argument when I found it on the Skyrim Mods Troubleshooting Guide. The very first bit in the guide describes what seems like my problem, and back then, adding "-forcesteamloader" made my game launch when nothing else did. I am using a legitimate Steam version, and it's on version 1.6.1170. I also have SSE Engine Tweaks and the Modified toml for it.

 

I do have OneDrive on my PC but it's not enabled, I never even made an account on it. I can't even fiddle with its settings to "turn it off and on and off again" or anything of the sort without making an account first. Could it still be interfering? I can make an account and mess with the settings if so.

 

I have 24 active ESMs, 126 active ESPs, and 373 active ESLs. All of these should be below the limit, I think. 

 

I have not checked if Antivirus might be interfering, that is true. I do have my Skyrim on Program Files since that's where Steam puts it by default. Can I just cut and paste it out to someplace else, or would that break more things than it fixes?

 

Also, I tried to take a recording of my ProcMon's weird behaviour. I know it's not the best quality video but I hope it helps in some way. Here: https://streamable.com/a90t13

 

@Demonwise I am not using ENB but I do have Community Shaders, which I heard is a similar thing. Should I try uninstalling it? 

 

I also tried deleting the ini files but unfortunately it didn't work out. 

Edited May 15, 2025 by Krit-hit

[traison]

13 minutes ago, Krit-hit said:

I do have OneDrive on my PC but it's not enabled

 

If you have Windows 10 or 11 and didn't specifically break/disable OneDrive, it will be active, regardless of what the settings may tell you.

 

14 minutes ago, Krit-hit said:

Could it still be interfering?

 

If you created a Microsoft account when installing Windows 10/11, OneDrive will be actively copying your files to the cloud.

 

15 minutes ago, Krit-hit said:

I have 24 active ESMs, 126 active ESPs, and 373 active ESLs. All of these should be below the limit, I think.

 

stdio limit is by default 512 and includes BSA archives and potentially other stuff. Your plugin count is already at 523. SSE Engine Fixes has an option to increase this to 2048. I'd say you need this at this point.

 

16 minutes ago, Krit-hit said:

I do have my Skyrim on Program Files since that's where Steam puts it by default.

 

That's an issue. You're not supposed to write to anything in the Program Files directories. They're protected for a reason. It's unfortunate (for us modders and tinkerers) that Steam defaults to this, but Steam is technically just following and complying with Microsoft's models.

 

18 minutes ago, Krit-hit said:

Can I just cut and paste it out to someplace else

 

Technically yes, but that's going to be far more work and trouble than doing it properly. Move your Steam library using the utilities in Steam itself. It takes care of all the work for you and you don't have to worry about issues like updates and what not in the future.

 

19 minutes ago, Krit-hit said:

Also, I tried to take a recording of my ProcMon's weird behaviour. I know it's not the best quality video but I hope it helps in some way.

 

That is not procmon; there is no CLI version of it that I know of. ProcMon is a GUI application.

[Krit-hit]

Moving my game out of Program Files turned out to be quite a bit longer and more complicated than I thought but I finally managed to get it done. Unfortunately I'm all out of time for the day though, so I'll try finalising the process and giving it a go tomorrow. 

 

I do have Engine Fixes and the modified toml for it, which I thought sets the plugin limit higher by default. I'll give it a manual check too tomorrow. And I'll see how I can get OneDrive's talons off of my laptop if all else fails.

 

BTW Turns out I was using this Procmon. Perhaps not as useful as the other one you linked, but thankfully it isn't a virus or anything.

[MadMansGun]

1 hour ago, traison said:

limit is by default 512 and includes BSA archives and potentially other stuff. Your plugin count is already at 523. SSE Engine Fixes has an option to increase this to 2048. I'd say you need this at this point.

esl do not count, the limit is only for esp & esm files.

 

4 hours ago, Krit-hit said:

Ever since I made my mod list, my Skyrim has had a bizarre bug where it launches windowed and works as long as it is minimised on the taskbar (music works, game loads up to main menu etc.) but as soon as I tab into the game, it completely freezes up. Now there is (or rather was) one way to fix this bug : by typing "-forcesteamloader" in the SKSE arguments section. 

-forcesteamloader should not be needed, your enb & game settings may be messed up.

 

go into enblocal.ini and make sure it's set to this

Quote

[WINDOW]
ForceBorderless=true
ForceBorderlessFullscreen=true

at the least it will help you tab out when things go wrong.

[traison]

2 hours ago, MadMansGun said:

esl do not count, the limit is only for esp & esm files.

 

I assume by ESL you mean plugins loading into the FE address space. In that case I will unfortunately have to disagree with you. I dumped all open file handles while the game was running, and I see plenty of FE plugins being kept open.

 

Sysinternals handle.exe:

$ handle -p SkyrimSE.exe

 

My current install has 493 file handles open:

$ handle -p SkyrimSE.exe -s

 

My plugin count as reported by Mod Organizer 2 is 20 esm, 114 esp and 104 esl totalling 238.

 

Edit: I think you may have misunderstood my previous post. I was talking about stdio limit, not the plugin limit imposed by the game's plugin loading system.

Edited May 15, 2025 by traison

[Krit-hit]

Okay, so since last night I have -

 

1. Moved the game out of Program Files.

 

2. Uninstalled OneDrive.

 

3. Confirmed that Engine Fixes has set the stdio limit above 512 (it's at 2048), as has the Modified toml (it actually has it set up in the 8000s!).

 

But I'm STILL stuck with that damn freeze bug T_T

 

Any chance you know of anything else that might be causing it, @traison?

 

@MadMansGun I don't use ENB so I don't think I have any ENB configuration files. (Unless they come with base Skyrim?) Anyway, I can tab out. It actually makes the game unfreeze and start working again. Like if I tabbed in at Bethesda logo and it froze there, I can then tab out, wait a while and tab back in to see it has loaded up to main menu now (but it freezes again as soon as I've tabbed in). I can also see it loading and progressing if I just hover the mouse over the window on the taskbar, it only freezes when I'm tabbed into the game itself. 

 

Sorry if I didn't clarify that in the main post. I just need to use Task Manager to end it because if I just press X on the floating window in the taskbar to end it, then it doesn't actually close the game. MO2 remains unusable and Skyrim can be seen lingering in the processes list, so I have to click End Task to actually end it.

[traison]

58 minutes ago, Krit-hit said:

Any chance you know of anything else that might be causing it

 

I would have to see this problem for myself. RustDesk or TeamViewer. Make sure you understand what it is and what the risks are before you agree to anything. PM me if this sounds reasonable to you.

 

59 minutes ago, Krit-hit said:

if I just press X on the floating window in the taskbar to end it, then it doesn't actually close the game.

 

This works in the same way as Alt+F4. It sends a message to the message pump. If the pump is not working, nothing happens. When you get the "Not responding" window title, it's because Windows has detected that a message pump has stopped processing messages.

 

Another way to put that is that hitting the "X" on a window is more of a wish than a command.

[Krit-hit]

Thanks a lot, I'll consider your suggestion. I'm doing a bit more fiddling to see if I can figure it out myself first.

 

I tried disabling all mods and enabling them back up from the last to the first this time, instead of last month when I first encountered this problem and did it from first to last.

 

Back then I was seeing the freeze bug happening around 100 mods in, then from then on randomly enabling or disabling something would make it run again until eventually adding some more mods triggered the bug again.

 

Today I managed to get all the way to 683 mods and 470 plugins before I actually encountered the bug. Maybe there's some mod that causes the freeze bug but only after some other mod is introduced to the same list as it, so it passes the check at first and only shows problems later, I'll experiment more when I have the time but the freeze first occurred today when I enabled Skyrim Immersive Creatures and FileAccess Interface for Skyrim SE Scripts - FISSES. Both of these trigger the freeze, whether I only select any one of the two or both.

[Krit-hit]

Okay it's still more complicated than I thought. From what I can tell at least, it's seemingly one of these, perhaps when mixed with something else. I could still be way off though.

 

 

At least somewhere around these is where the freeze bug starts popping up. I've seen it happen when I enable FISSES, Immersive Creatures, Enhanced Blood Textures, Improved Alternate Conversation Camera or Base Object Swapper. But I've also managed to make the game run with one or more of these enabled as well, just by disabling one or more of the other culprits instead. Truly random bunch of mods, from what I can tell at least.

 

I also went through the mod pages to ensure I have all requirements, and I do. I just cannot figure out what is happening here! It's like every step towards understanding just makes the whole thing bigger somehow.

[Krit-hit]

I also noticed that this particular bunch of mods lines up kind of nicely with the first time I encountered the freeze bug while testing from top to bottom a month ago. 

 

I wrote "(FREEZE)" next to the Sentinel mod because it was the first one that caused the freeze back then. I wonder now if it was because of one or the other of the mods that preceded it, because this time the bug is happening around the same group of mods on the list. Maybe the problem lies somewhere between Sentinel and Base Object Swapper, I don't know. It's too late at night now and I have a busy couple days ahead so I might not be able to get on it right away, but I'll still take any advice if anyone reading this has encountered issues with any of these mods.

[Krit-hit]

MY FRIENDS

 

I think I may have located the true culprit! The comments section of Community Shaders on Nexus has quite a few people from the past couple weeks describing the EXACT SAME freeze bug I'm having, right down to the weird behaviour with the game running when it's alt-tabbed but freezing when you tab in. I'm still going through the responses to figure out which solution might work for me, but at least the villain has been unmasked!

 

Well... at least I hope so. I'll return with the solution if I find one that works. 

[traison]

The new version is broken yes, but I haven't heard it freezing the game where you describe it freezing. Version 1.1.15 works, use that for the time being.

 

Edit: and since it's not documented anywhere, here's the plugin versions for 1.1.15:

Spoiler

Cloud Shadows-139185-1-1-1-1737068749.7z
CS Light-138443-1-2-1-1738021578.zip
Dynamic Cubemaps-112763-1-0-4-1710625858.zip
Grass Collision-87816-2-0-0-1733538004.7z
Grass Lighting-86502-2-0-0-1733537978.7z
Light Limit Fix-99548-2-0-1-1733596917.7z
Screen Space GI-130375-3-0-3-1734449232.7z
Screen Space Shadows-93209-1-2-1-1737068709.7z
Skylighting-139352-1-0-1-1737227592.7z
Subsurface Scattering-114114-2-0-0-1733538036.7z
Terrain Shadows - Heightmaps-135817-1-0-0-1733598206.7z
Terrain Shadows-135817-1-0-0-1733602194.7z
Vanilla HDR-76521-1-1-1-1665265181.zip
Water Blending-95145-1-1-0-1699907425.7z
Water Effects-112762-1-0-0-1733538121.7z
Water Parallax-112761-1-0-0-1710523592.7z
Wetness Effects-112739-2-0-0-1733538076.7z

 

Edited May 17, 2025 by traison

[Krit-hit]

It is over... the Great Freeze has been thawed. 

 

The issue, as it was explained to me, was that the latest Community Shaders comes with some setting called Frame Generation (in the Display tab of the in-game CS menu) enabled by default, but apparently this setting only works while the game is in borderless windowed mode. The suggested solution was to just change the game to run on borderless windowed too.

 

So I tried that... and it worked! I've tested it multiple times now and can confidently say that it just works! Game still launches on a side tab but switching to it now doesn't freeze the game anymore! 

 

If anyone else is having this issue, make sure to set it to borderless windowed in both ini and official game launcher, as well as SSE Display Tweaks if you're using that! Some people said they were also able to return to playing on full screen after disabling the Frame Generation setting, saving it, and then restarting the game, but in my experience that did not work. The Great Freeze just returns if I launch it on full screen, even though Frame Generation remains disabled. But I'm fine playing on borderless windowed, and there's plenty of tweaks to make it run just as well as true full screen. 

 

So yeah, took quite a bit of time but problem solved! Modded Skyrim may be a font of unruly magic, but there's an entire community of sorcerers ever on the pursuit of mapping out the wild runes of its foundation, the methods to its madness. Sometimes a single spell holds the power of creation and destruction within the confines of its syllables. 

 

Maybe someday when I feel braver about plunging those depths, I'll make a custom shout that immediately shatters frozen enemies. (Force! Steam! Loader!)

 

Jokes aside, thanks a lot for your consistent suggestions, @traison! I actually asked about this issue on several websites and forums but this was the only one where someone replied. 

 

[traison]

6 minutes ago, Krit-hit said:

I've tested it multiple times now and can confidently say that it just works!

 

Teleport to Shor's Stone and walk South to Riften. Near the watchtowers and the altar ruins with the Amuet of Zenithar the game will start stuttering, and if you walk too fast it will freeze. This was the first issue that popped up with 1.2.0 (and it's still in 1.2.1). Second issue was freezing on load screens, this hasn't been fixed either but it *might* be the framegen thing as that in general is linked to freezing with CS.

[Krit-hit]

 

5 minutes ago, traison said:

 

Teleport to Shor's Stone and walk South to Riften. Near the watchtowers and the altar ruins with the Amuet of Zenithar the game will start stuttering, and if you walk too fast it will freeze. This was the first issue that popped up with 1.2.0 (and it's still in 1.2.1). Second issue was freezing on load screens, this hasn't been fixed either but it *might* be the framegen thing as that in general is linked to freezing with CS.

 

Got work now but I'll test it after I get home. I never encountered loading screen freezes even with Community Shaders but I'll keep it in mind if it happens in the future. At least I know what mod to fiddle with now!

[Krit-hit]

Hey @traison, I took the route between Shor's Stone and Riften that you mentioned yesterday and I'm happy to report that there wasn't any freeze. I'm not certain if it's related to the Frame Generation setting though, because I had these locations already discovered (the watch tower and the Shrine of Zenithar as well) from earlier in my playthrough when Frame Generation was still enabled. 

 

I haven't encountered any loading screen issues either. I will say that in some parts my FPS has worsened, but I think it might be because Community Shaders or some other graphical mod wasn't totally working until now? I'm noticing a change in the game's lighting and such too, I definitely do not remember the sun rays being so realistic before. And I've also noticed my FPS getting a significant increase in interior cells, dungeons and towns. 

 

Anyway, all in all everything is okay right now. Let me know if you think I should test some other locations or situations. 

Edited May 18, 2025 by Krit-hit