Skyrim Memory Patch - fixing ILS, uGrids CTD, freezes - Final ?!

Requirements

64bit OS - 32bit may work but untested, probably should use /userva switch, but if you are that desperate good luck
a decent amount of RAM - more than 4GB
a suitable graphics card with decent amount of VRAM - depending on texture sizes
ENBoost - need to free up main memory
Stable uGridsToLoad - if you want to test with higher uGrids. You may not really need it, but it fixes a recursion bug that could potentially cause CTD with default uGrids as well.

Zum Vergrößern anklicken....

Brucie schrieb:

Verstehe ich das richtig das man nur den ENBBOOST, Stable uGridsToLoad, skse, skse steam loader.dll online und den skse.ini Eintrag braucht damit das läuft?

Zum Vergrößern anklicken....

mditsch schrieb:

aber das ist doch der Sinn der Sache, mit mehr als den scheusslichen ugrids 5 zu zocken

Zum Vergrößern anklicken....

mditsch schrieb:

könntest du hier bitte Quellen benennen? Ich habe mal versucht was zu ergooglen, aber fand nix. Danke dir..
..Nicht dass du es mit der timescale verwechselst?

Zum Vergrößern anklicken....

For those who are asking "What is uGridsToLoad?", here is a quick overview. This is pretty basic, and I am by no means an expert. I still encourage you to research the subject thourougly before diving in and messing with these settings. There is a lot more knowledge these days about the consequences of tweaking uGrids, and while it can potentially be done safely, it is far easier to tweak it and permanently corrupt your save games. Hopefully this mod will solve the standing issues, allowing us more freedom to tweak uGrids safely.


Games like Skyrim are epicly immense. They contain vast worlds populated with incalculable volumes of static and complex behavioral content. As such, it is generally impossible to load all of that information into the systems memory at once. To combat this problem, Skyrim divides the game world into "cells", organized into a grid. By default, the game loads the fivexfive (5x5) area cells around the player, including the player's current cell, at "full level of detail". In these 25 cells, the game executes world content at its maximum capacity...high res textures, moderate to high object LOD, etc. The game "runs" in these five cells...all scripted content, game events, etc.


Since Skyrim offers the ability to see far off into the distance, it also loads additional cells beyond these core five, albeit at a lower level of detail. These are "Exterior Cell Buffers"...partially loaded, ready to be transitioned into a fully loaded cell. Exterior cell buffers do not execute scripted content, usually have lower resolution textures, and use low object LOD, etc. Exterior cells complete the world, but the game doesn't really "run" in these cells...they are just there to provide continuity and totality to the world.


Before tweaking uGrids, it is best to understand the consequences. As most players who mod their game probably know, Skyrim is not a particularly stable game. Even a vanilla install often has problems. Original game and DLC data files often contain "dirty" edits, and a host of other issues related to the scripting system in Skyrim make "tweaking" pretty much anything a risky endeavor. Save game corruption, CTDs, ILSs, and lockups are a common occurrence in modded games. In the case of scripted content, the game will execute scripts in all fully loaded cells. That means that in the current user cell, as well as the surrounding cells, the game will run things...wildlife, bandits, war factions, and anything else your mods may add to the game. Increasing uGrids from the default of 5 has explicit consequences. Not only will it load more active, "living" content into your computers memory, and execute it on your CPU & GPUs, it will also load more textures to render those cells at higher detail. The world can look, and behave, amazingly realistically at a higher uGrids setting...but all of that beauty and realism can **potentially** come at the cost of a less stable game.


The "uGridsToLoad" setting is a Skyrim.ini configuration setting that allows you to change how many cells around you in the world grid into which content is loaded. It's companion setting, "uExterior Cell Buffer", is directly related, and should always be set according to a simple mathematical rule. The default settings are uGridsToLoad=5 and uExterior Cell Buffer=36. This follows a simple mathematical rule: uExterior Cell Buffers=(uGridsToLoad+1)^2. This rule means that uGrids must always be an odd number (and should really never be set lower than 5), thus making the valid options 5, 7, 9, 11, 13. (Note: It is believed that 13 is the highest valid setting, however on the ENB forums, there have been a few comments of people using 15, albeit with sketchy stability...and seemingly on devilishly beasty computers at that!! Given the mathematical rule, this means that, accordingly, uExterior must be 36, 64, 100, 144, 196.


You can see the exponential relationship here, and maybe understand why many who followed early Skryim tweaking guides (such as the famous one from nVidia: http://www.geforce.com/whats-new/gu...aranteed-to-make-your-game-look-even-better#1) and jacked up their uGrids/uExterior settings ended up crashing with OOM errors and the like. Loading hundreds of cells into the world, 49, 81, 121, or 169 of them fully running game content, on a system that may not have been up to the task could definitely cause problems. Infinite loading screens often occur when you push uGrids too far, as loading content into a fully loaded world cell takes a LOT longer than loading it into an exterior cell buffer. Especially with modded games, particularly those that include lots of heavily scripted mods and extensive high res texture packs.


There were also deeper, less obvious, and more insidious problems with changing uGrids. With Skyrim, all of your save games embed scripted content. Since scripted content runs in the fully loaded cells, increasing uGrids and saving, then decreasing it would usually break your save games unless you increased uGrids again. When loading a save game, it will try to load any embedded scripted content into all the fully loaded cells that existed at the time of the save...many of which may simply not exist if you later reduce uGrids. Additionally, the author of this mod, AltimorFP, identified MORE coding bugs in Skrim's original content, which handled things either incorrectly, or perhaps less than efficiently and in an unstable manner. This mod aims to correct the instability issues that revolve around uGrids, and how it affects scripted content in the world. Before you dive in and try it, I strongly encourage you to research uGrids more, determine how much active content your system can handle, and experiment properly (i.e. make SURE you run "save BeforeUgrids" in the console before you do anything, so you have a known "original uGrids" save point to fall back on WHEN things go wrong.) Once you have an idea of how uGrids works, and are ready to give it a try...I would install this mod first (as it should at the very least be no worse than tweaking uGrids without it, and potentially MUCH better! )

Quelle: Thread Stable uGridToLoad

Zum Vergrößern anklicken....

mditsch schrieb:

Hi Nylin,

Quellen und wodurch?

Zum Vergrößern anklicken....

Donni632001 schrieb:

Markas hat das ja schon gut erklärt.

Zum Vergrößern anklicken....