Hi. I seem to have stumbled upon a problem with Situation Comedy leaking memory. (And lots of it.)
AMD Athlon XP 3000+ on a nForce 2 motherboard
ATI Radeon 9800 128MB with Catalyst 6.11 drivers
The game seems to start hogging memory from the minute you start playing, and it gets progressively worse and worse as you play. The game can start out using about 20MB of memory, and I've seen it end up at over 650MB, with my swap file pinned at over 1GB. (Which seems a little excessive for a game with a 256MB memory requirement
.) This of course leads to Windows starting to swap memory, and consequently jerky graphics in-game. Below are a couple of screenshot of the task-manager showing the game hogging memory. (I forgot to take a screenshot of the 650MB incident, but 370MB is still too much. The swap_file.gif shot shows the swap-file growing rapidly as the game is running.) Minimizing the game at any point seems to release all memory hogged by it, but as you start playing again, the problem returns.
How to reproduce:
Walk around any location from end to end over and over again, or travel through all of them a lot. (The problem seems more pronounced at locations with lots of textures.)
Since locations with lots of textures amplify the leak, I have a hunch that it might be related to texture/vertex/shader memory not being released as it should. This would explain the minimizing behaviour too as that destroys any device contexts the game is using, and thus any buffers bound to that context. This could possibly be a driver problem, but it's hard to say. (Knowing ATI, it wouldn't surprise me if it was!) I'll have a go with the latest ATI drivers and report back if that solves it.
I hope you'll be able to look into this problem, as it would be quite serious on low-memory setups. (I was able to play through the game even with the bug here.)
(The forum seems to resize gifs attached, and in jpeg they were to lagre.)
EDIT: Just tested Catalyst 6.12 and nope, no dice. Started a new game and by the time I had gone trough all locations I could access it was at almost 600MB. (Screenshot up there with the others; more_memory.gif)