I did one better... took a series of screen caps of Task Manager: Before I run the game, while it's running without campain map lag, and then after the lag has been going for a few minutes. Note that Task Manager popped me back to the desktop, and I have no idea what that may do to the game's memory imprint versus when it's actually the active window.Quote:
Originally Posted by sapi
http://www.goldeneaglecomics.com/pic...foreLaunch.JPG
http://www.goldeneaglecomics.com/pic...unningOkay.JPG
http://www.goldeneaglecomics.com/pictures/AfterLag.JPG
After I quit the game, it looked so close to identical with the pre-game state that I didn't even cap it again.
So unless I am missing something glaring, the numbers I'm getting don't look suggestive of any memory leaks. The available memory is only VERY slightly lower after the lagging was going, but presumably this is not nearly enough to cause any memory issues, or this particular issue, and is probably just due to the game needing a little more memory for legitimate purposes as I got deeper into the campaign.
As I said though I could be wrong or have missed something obvious, so if anyone has a word of confirmation or contradiction, let me know as I'm sure some people here know more than I do about these kinds of things.