

Half of this is then allocated to scrap and half for the game to store whatever resources it needs while running. The next problem is that when the game is started it allocates a memory block that is 512MB in size. And there is nothing you can do tweaking the game itself or it’s configuration files to stop this behaviour – it’s a coding limitation.

It does however not stop the application from trying to access more but if it does then it will instantly crash to desktop. That means a lot of things but what is most important is that it means that the amount of memory the process can allocate is limited to ~3.1GB. So, lets get into it – and if you don’t care at all for the technicalities of this then at least read the Papyrus section and then jump on to the SKSE and ENBoost guide at the bottom. If you have a very stable game now with lots of scripted heavy mods then chances are you already have done most of the tweaks, or know of them, and might not have much need for this. I know, I know there are thousands of these guides out there but I will mainly focus on memory, CTD (Crash to Desktop) and ILS (Infinite Loading Screen) in a simplistic way and not delve into all the other tweaks one can do to the game (for good and for bad). I figured that in order to give everyone the best possible experience with SRM once it’s launched I will write a small tweak guide and explain a few caveats that might be good to know.
