12 réponses à ce sujet

[Cry4dawn69]

It seems that the new patch has created a memory lead in the game. Playing for about 3 hrs and I am in the Dwarf city. When I first went into the city it was fine loading. But after walking back and forth from section to section I was starting to notice my load times were really bad.. Taking any where from 5-7 mins to load each section of the city. I am guessing we have a memory leak issue as my computer is more then capable of handling this game. Hasn't been a problem since the 1.01 patch. Worked fine before

[JironGhrad]

system specs? a lot of people are finding the Ozrammar section taxing for their machines... especially multicore AMDs

[jayheld90]

its happening to everyone (maybe not everyone, but most), and it was before the patch. happens to me, too. if you save, quit and restart the game, it goes back to normal. just have to do it every hour or two.

[Kavita]

You are not alone with this problem, i have a triplecore amd cpu, 4 mg ram and radion ati gpu card. the load time can be up to 10 min after 2-3 hours play time, move around starting to be a problem aswell like my chars moveing rly slow,. when i restart the game i have 5 sec load time and everything is rly good

[behemothdan]

Same here. The longer your gaming session, the longer the load times seem to be. As stated, quit the game and restart to get your nice quick load times back.

[Shilarva]

behemothdan wrote...

Same here. The longer your gaming session, the longer the load times seem to be. As stated, quit the game and restart to get your nice quick load times back.

Its not always the longer you play though. Sometimes huge area transitions too....like in Dwarf town, going from commons to deep roads....or commons to diamond...or commons to proving. 10+ mins, after a fresh load, to go to Jarvia's.

[Sidrat2009]

So they have memory usages problems - hopefully it can and will be fixed in a future patch.



Either that or it's a tactic of BioWare to get you to realise just how long you've been playing for.

[Cry4dawn69]

Ok yes I am running a Quad Core with 8 gigs of ram. Last night was the first time I have played for like 8 hrs so that makes sense. Kinda figured log out and back in would fix it but was to tired to try. So the game has memory leak issues as I suspected. God damn I love this game

[Pyroclase]

Not sure its a memory leak per se. My system RAM (of which i ony have 2gig, 32 bit XP SP3) is never taxed beyond 55-60% although my processor (Athlon X2 64, 4600+) never seems to run below 95% usage and almost always 100%. When the loading times get longer though, the CPU use actually drops to below 50% for the time the PC seems to idle, then as the HDD kicks in (anything up to 2 mins after initiating loading) , loading the post transition cut scene or the next major area, it pops back to 100%. (all percentages viewed from my logitech G15 screen). So i am split between a memory leak on the graphics card (HD4850, 1gig) or the inability of the CPU to drop unwanted threads. Although the latter is yet to be checked out.

[Hrtlsmoe]

I don't even have a Amd processor i have a Intel Core duo E 8500 @ 3.16 mhz.. and my vid card is a Nvidia Geforce Gtx 260 with 3.25 gb of ram on the system.. I have all my vid settings on high.. this also happened to me.. I've been reading that this is a issue through out the game so .. i'm a bit worried. i've been hearing people randomly saving and restarting or just empty in saved folder i've yet to try this

Modifié par Hrtlsmoe, 10 novembre 2009 - 07:53 .

[bassanio95]

It feels like a memory leak. Loading was fine before the patch. Now the system slows way down after a 2-3 hours of play. Restarts help for now, but I'm sure they'll patch that up fairly quick.

[ChandlerL]

Agreed, it likely isn't an actual leak. The memory footprint doesn't grow much during play.- More likely an issue with the management, allocation, and reallocation of resources during play.

[JironGhrad]

There's an issue AMD X2s that won't drop threads as pyro pointed out... any fix for that would have to come from AMD and they've not got a reliable solution... the best answer is to set processor affinity to the 2nd core only this prevents the CPU from absorbing all the resources

Certain newer high-end intel chips are also reportedly doing this... processor affinity solves it also though

Modifié par JironGhrad, 10 novembre 2009 - 08:29 .