Using Aging Off/Story Mode Off - game takes 18 minutes to save
JBoat:
Quote from: clemeaux on 2009 July 10, 14:03:15
Sorry - I didn't verify that yet. Maybe it was only my imagination but I really had the impression that the game didn't (save-) crash as much as before. Anyway it does make sense to increase that 2Gb to 4Gb if you have enough memory on your system (like in my case 8Gbs) since even Win 32 is capable to address 3.4 Gb of memory.
Apart from that I wonder whether you are right.
While XP itself can address up to 3gb with the proper configuration, 32-bit applications cannot without being edited first, and/or recompiled. Even after being enabled for it, they have to physically *want* to address larger space (like with the ini setting). So unless all three are happening, it's just a placebo / voodoo effect. :) I have had it make a difference in other games in the past on XP, but have moved past that to the wonderful world which is 64-bit now.
Perhaps after SLAM is complete, I'll visit it and see if it makes any performance difference on Vista 64, since applications here have a native shell within which to acquire more memory after being edited. I don't personally have any performance issues though - even my saves only take 10 seconds or so. RAID too is a wonderful thing.
Keep toying with the idea however - there is a slim chance it could pay off and work.
Anach:
Ive been doing some testing this past couple days, and this is what i've found so far.
1. If I save twice per sim day, I can usually only make 2 saves before it fails with either error or CTD at the end of saving (bad save.)
2. If I wait longer before saving (2 days) I have higher chance of getting error code 12 the first time I try to save.
3. After the second successful save, I often end up with graphical glitches, such as missing textures (black bodies, or black UI objects.)
4. If I reload a game after getting the missing textures from saving, I still have black objects. I need to clear the cache files to fix the missing texture issues.
5. Error code 12 can usually be bypassed by removing all saves from my save directory and attempting to save again.
It seems to me that the saving issues arent a game problem, but more of the save manager itself. It does seem that saving the game somehow causes cache corruption and often has an issue with the overwriting of existing saves. It is also possible that saving expedites the issue of the memory leak. So most likely there is nothing we can do to fix it and have to wait for another patch.
moondance:
Strangely, my Indie Mod neighborhood still saves quickly. Maybe when they killed EA's version of story progression they also inadvertently killed whatever caused saves to take forever on older neighborhoods.
JBoat:
Quote from: JBoat on 2009 July 10, 16:53:31
Quote from: clemeaux on 2009 July 10, 14:03:15
Sorry - I didn't verify that yet. Maybe it was only my imagination but I really had the impression that the game didn't (save-) crash as much as before. Anyway it does make sense to increase that 2Gb to 4Gb if you have enough memory on your system (like in my case 8Gbs) since even Win 32 is capable to address 3.4 Gb of memory.
Apart from that I wonder whether you are right.
While XP itself can address up to 3gb with the proper configuration, 32-bit applications cannot without being edited first, and/or recompiled. Even after being enabled for it, they have to physically *want* to address larger space (like with the ini setting). So unless all three are happening, it's just a placebo / voodoo effect. :) I have had it make a difference in other games in the past on XP, but have moved past that to the wonderful world which is 64-bit now.
Perhaps after SLAM is complete, I'll visit it and see if it makes any performance difference on Vista 64, since applications here have a native shell within which to acquire more memory after being edited. I don't personally have any performance issues though - even my saves only take 10 seconds or so. RAID too is a wonderful thing.
Keep toying with the idea however - there is a slim chance it could pay off and work.
Just an update on this idea for game speed, lag, and save times...
I went and backed up my TS3.exe, patched it with the generally accepted 4gb patcher on the web, went and edited all relevant ini settings to be a full factor larger (not just 2x, but 10x), and haven't seen it use any more memory than usual in the task manager (1.4-1.6gb). Going to keep toying with the idea, though I don't think it'll pay off without future 64-bit support from EA.
Lissa:
Moondance, my game with Awesome mod installed, takes 25 minutes to save. So I would like to try Indie mod--do you uninstall Awesome when you want to play the Indie neighborhood? If so, can I do that when I have Supreme Commander enabled? I've checked out the Indie mod, and though it looks good, would rather use Awesome, but if Indie will reduce my save times I may soon have no choice.
Navigation
[0] Message Index
[#] Next page
[*] Previous page