Results of three hours play.
Time - Point in time after starting from rebooting the computer and hitting the Resume choice in the main menu.
Load Time - The time it takes in seconds from the Loading... appearing to being in the actual area. On the travel map this means that I didn't start the stop watch until the Loading appeared in the bottom right corner.
Transition # - The transition number from starting the game, so if it's 8 then it's the 8th transition since hitting the Resume option.
Activity - start and destination of the transition.
So the format will be :
Time (hh:mm), Load Time, Transition #, Activity
00:00, 17.9, 0, Pressing resume to being in game.
00:00, 5.2, 2, From camp(Lothering) to Redcliffe.
00:20, 8.7, 8, Inside Redcliffe Tavern to outside.
00:40, 8.3, 10, Inside Redcliffe Tavern to outside.
01:00, 12.4, 13, Inside Redcliffe Windmill to Castle Dungeon.
01:20, 16.3, 17, Castle Courtyard to Inside Keep.
01:40, 25.8, 21, Castle Courtyard to Redcliffe Village.
02:00, 2.3, 27, Honnleath to Wilhelm's Cellar.
02:20, 12.7, 29, Honnleath to Random encounter Dwarven merchant.
02:40, 19.3, 31, Lake Calenhad to Random Encounter Leliana's Assassins.
03:00, 8.7, 33, Soldier's Peak to inside Keep.
Ok, one thing I picked up on is that the longer you are in an area the worse the load times get, so big areas like The Deep Roads and The Circle of Magi + Fade can get pretty bad. This seems consistant with what's been happening. I will test both these areas in the next couple of days.
Another thing is that the DLC areas seem to be totally free of this phenomenon.
Hope this helps.
Edit: Oops, I forgot the memory shot. I'll add that with the next data capture which will be the Circle of Magi.
I'll also save it before doing the capture so that after I do the first run I'll start the game again forcing to use a single CPU and capture the data again to see if there is any difference.
Modifié par Palathas, 20 janvier 2010 - 11:44 .