As soon as changing cell : CTD.Īgree =\ I'm using 7 and sometimes 9, and it's unfortunately not so stable like in older patches. 7 works if loaded in a closed cell (in Whiterun I.E.), not in an exterior one (in tundra). I really thought when doing this memory would explode but nada Though i didn't get yet with Ugrids 7 to the magical 3 GB limit running around a marathon in the World i reached 2.3 GB as the highest peak *grml* even tfcing and flying around i never gone above capturing all the space and even lots of trees. My current experience is different with 1.8 i can use up to 7 and it runs very nice but if i try ugrids above 7 savegames wont load and the Game is stucking in the loading screen (Windows no response message, infinite loop). Tested on 3 GB cards, 4 GB cards, Win 7 64. I didn't have any infinite load screen, not even one. crap in my inis, none of the recent tests has been successfull about this. Unfortunately, even with removing all the iMaxAllocated etc. Higher uGrids means not only better distance details, but also smoother gameplay.
If Boris finds the way to unlock what it needs for us to set uGrids to 7 again with no CTDs, I'd be an happy man. One Bugthesda introduced their first "memory optimizations", then it became unstable. I could also set it to 9 with not SO many CTDs.
Charlievoviii wrote:I'm LMAO watching noobs still using Ugrids over 5 and crying about CTD.īefore TESV 1.6.09xxx patches, uGrids to 7 was totally stable to me, even with HQ textures everywhere.
0 kommentar(er)
