blitzen Posted June 23, 2012 Share Posted June 23, 2012 There is a situation in which the change may cause problems, and I experienced it immediately after trying it. I was unable to load a save game after making this change. When I changed the settings to much lower values, the save would load. This was not due to any hardware limitation. With the lower settings, the game would lockup as I moved in a particular direction, but the save would load. Apparently there was some type of instability introduced by a mod or combination of mods. So my theory is that attempting to load everything up front is fine as long as everything is able to load successfully, but if there is an area with a problem, you won't be able to load the save game at all. And the problem may occur in an area that you may not even visit during that session. Something to consider. Link to comment Share on other sites More sharing options...
yafi Posted June 26, 2012 Author Share Posted June 26, 2012 Not being able to load the savegame at all isn't related to this .ini tweak, that's usually mod-related or due to overloading of scripts and savegame bloats. Link to comment Share on other sites More sharing options...
blitzen Posted June 26, 2012 Share Posted June 26, 2012 Not being able to load the savegame at all isn't related to this .ini tweak, that's usually mod-related or due to overloading of scripts and savegame bloats. The savegame file size is normal, under 10 MB. Note that the exact same savegame would load when I reduced the values back to normal. I made no other changes. If the game is in an unstable state already, the .ini tweak will potentially cause problems to occur immediately upon loading, instead of deferring them until a particular area is entered. I would say that the inability to load the savegame, in this particular case, was directly related to the .ini tweak. The .ini tweak did not CAUSE a problem, but did expose an existing one at an inconvenient time, preventing the game from completing it's initialization. Link to comment Share on other sites More sharing options...
Georgiegril Posted June 26, 2012 Share Posted June 26, 2012 @Blitzen, I agree with your assessment. Any tweak you add may or may not work in an individual case, based in part on the specific variables present in the user's situation such as previous changes made, hardware/software settings and capabilites, etc, and you provide a good example of that. That is what I was trying to point out with my previous posts...in my own case, I have made changes in other .ini settings to pretty much max out my VRAM, and because of that this would not be appropriate. However, for others it might be exactly their solution, and it is great to have this tweak on the forum for people to consider. The only way anyone can know for sure if a given tweak is useful is to test it in their (computer) environment. Link to comment Share on other sites More sharing options...
blitzen Posted June 26, 2012 Share Posted June 26, 2012 Just to be clear, my posts are not in any way intended to discourage anyone from trying these changes. I was simply reporting a single experience, with a possible explanation, as it helps us all understand this complicated game a little better. In fact, I recommend that people read all of yafi's posts/comments, and at least try out his recommendations and suggestions if applicable to one's individual situation. If others try out this particular change, let us know how it goes. A few more data points couldn't hurt. Link to comment Share on other sites More sharing options...
yafi Posted June 27, 2012 Author Share Posted June 27, 2012 Really, to me, it sounds like you're trying to shoot me down for some reason, Georgiegril. Can I perhaps have a save game of blitzen's where he applied the .ini tweak, and one where he did NOT apply the .ini tweak? I am 99.99% confident this .ini tweak does not lock save games, it's impossible for it too as this effect only changes how much resources your computer uses (what little it does anyway). Save lockups are due to mod changing and removing. Link to comment Share on other sites More sharing options...
Georgiegril Posted June 27, 2012 Share Posted June 27, 2012 Not at all, Yafi. I 100% agree with Blitzen--- your solution could be the perfect one for some, and are absolutely worth consideration by anyone who is experiencing issues that you address. Beyond that, I believe that your contributions (not just this one) on the forum have provided creative, thoughtful and useful strategies that increase the happiness (at least gaming-wise) of many. Link to comment Share on other sites More sharing options...
Badmagic Posted July 6, 2012 Share Posted July 6, 2012 Since 1.6 the games been a mess for me, trying various things sceptically I gave this a go combined with disabling iPresentInterval and forcing v-sync through CCC, worked perfectly, all stutters removed, in fact it worked so well I was able to increase uGridsToLoad back to 7, install HD textures and whack AA back to 8, a combination of feats that's simply not been possible since the official LAA anti-patch on my ageing hardware so... It may not work for some, it works for me. Link to comment Share on other sites More sharing options...
bben46 Posted July 6, 2012 Share Posted July 6, 2012 My recommendation: Try it. It doesn't cost anything and it may work. :thumbsup:If not, just remove it and you haven't lost anything. Worst case, you have to remove it - and Nothing is changed.Best case no more stuttering and Yafi deserves a kudo. http://www.freesmileys.org/smileys/smiley-dance014.gif Link to comment Share on other sites More sharing options...
MadWizard25 Posted July 6, 2012 Share Posted July 6, 2012 Yafi is a fix pro, the least you should do is give his advice a try, rather than argue about it. Fixes for TES games are hardly ever universal. The only thing to do is try it. Link to comment Share on other sites More sharing options...
Recommended Posts