13 réponses à ce sujet

[Tulox]

I noticed when first running the game the mem usage is about 639k however as time goes on, this goes to 900k or even 1600k.  when its over 900 the game gets choppy (I noticed when holding tab to highlight stuff it gets much worse) hitting quick save often removes the chop but it doesn't bring the memory back down. Is this a known issue, or do i need to tune my pc to play this game (i can run X3: the Reunion full bore with no issues {that game is a Huge video hog} so its not my rig). 

[TallBearNC]

That's normal memory use for a game with HIGH HIGH rez textures and complex particle effects and zone artwork



I have X3 and it doesn't have nearly the texture quality and demands DAO has

[cheeseslayersmu]

Yes, there's a memory leak.

[TallBearNC]

I dont have the choppy issue, but I'm on a 64bit OS with 12GB of ram....



now where I DO get it is on my laptop.. win 7 32bit 4GB ram (but only 3 usable)... once the game uses about 1.7GB of ram load times get long and the game stutters... mainly because the swap file is being thrashed and there's little to no ram left to cache files. This is just a HIGH HIGH ram use game.



But yes BW can do somethings about it.. when you move from one zone to another they could add a user setting for a user to check saying something like "unload all unneeded textures" or something like that. Then the game would clear textures when you went form zone to zone...

[TallBearNC]

But I have seen no evidence of a leak. I've looked into exactly what's in the games memory address space, and it's all valid texture and file caching. The game is just being overzealous about it.

[Tulox]

TallBear, i have a Complex just outside mars with 150 stations in a single complex. That gets choppy on my second computer but the one i play DOA with has no issues, i guess thats what i was talking about. Thanks for the reply tho =)

[TallBearNC]

DAO has a lot of issues.. don't get me wrong... I just don't think it has a memory leak. I just think it's a RAM PIG and doesn't manage and unload textures properly based on a person's setup.



If the game had a TRUE mem leak, I wouldn't be able to play it for 12hrs non stop.. it would crash after just a few hrs of game play. I've seen no true evidence the game has an actual leak.



But.. be it a LEAK... or over use of RAM... BW still needs to adjust the game to not use so much

[daecath]

I have a saved game right before the demon battle in the fade for the mage's origin story. I can load the game with low texture, low detail, no fancy graphic fx, and only dialog sound enabled, and by the time I get done with the battle and the following conversation (less than 5 minutes), my memory use is up to 600MB. That's not a leak, that's a freaking black hole!

[Neccrid]

daecath wrote...

I have a saved game right before the demon battle in the fade for the mage's origin story. I can load the game with low texture, low detail, no fancy graphic fx, and only dialog sound enabled, and by the time I get done with the battle and the following conversation (less than 5 minutes), my memory use is up to 600MB. That's not a leak, that's a freaking black hole!

I know what you mean haha.  When I get done with combat sometimes it's just like I want to slam my head on my keyboard.  I keep my graphic and detail all high even though I get these problems because if I change to low still I will have problems so I might as well lag in style am i right?

[TallBearNC]

600MB is NOTHING by todays standards.. and y ou're only seeting PART of what the game is using... turn on the COMMIT CHARGE column in task manager to see what it's REALLY doing. On boot up the game INSTANTLY reserves about 1.2-1.4GB of RAM... and eventually go over 2GB after hours of playing...



600-900 wouldn't impact most any machines, and the memory most people see in task man is not the TRUE memory being reserved and used. You need to look at commit charge (which is pretty close to the ammount of virtual memory being used)

[TallBearNC]

Within 10mins of the game, the game WILL pre cache almost 1GB of textures so it doesn't have to load them off the hard drive later. The game is just "overzealous" about pre loading stuff. Although if it didn't load times would be even slower, but the other problem that brings on is people with 3GB or less suffer from the game taking up to 2GB, windows up to 1GB... and no more ram left to cache the HD, etc and the system starts hitting the swap file causing the game to stutter, etc, etc....

[daecath]

Commit charge is only at 1.7GB. The limit is 5GB (that must include the swap file since I only have 3GB ram). It's using roughly 1GB more than the idle system, and only half of what's available. So I still don't understand why it's not working. However, I must say this is getting exceptionally frustrating.

[Liucyfer]

Out of my experience: game just started, loadtimes less than 30s.



Pausing the game or just leaving it run for a couple of hours, loadtimes exceed 1 minute.



To me, it seems that the game will slow down more and more when time passes, but I'm here to play the game, so I don't check the system usage.



My setup: Velociraptor HDD (filled at more than 60 or 80%), 2 GB RAM, Win 7 32-bit.

[dbmccart]

TallBearNC wrote...

But I have seen no evidence of a leak. I've looked into exactly what's in the games memory address space, and it's all valid texture and file caching. The game is just being overzealous about it.

I personally believe that there is a serious memory leak with this program. I have monitored the progress of
it starts out at about 50,000 - 65,000 memory, however after about an hour or two this number increases to about 900,000 - 1,500,000 memory. I see no other explaination then a Memory Leak, as far as the texture theory goes no I highly doubt it. If this game seriously has that kinda of problem because of textures then maybe Bioware should have went ahead and taken the graphics up to about Mass Effects level that way it wouldn't seem quite as ridiculous to wait 3 minutes to load a screen. My common load times without the leak are none to 3 seconds. I have the game fully maxed out ingame and my GPU set to Quality(AAx8 = Edge Detect.) My GPU fully overclocked runs 48 C(with extensive cooling units) and the rest of my computer runs that or below. So that most likey means its not an overheating issue, at least not for me. Lets just hope Bioware fixes it soon.