85 réponses à ce sujet

[Avrii]

If you / i play the game a couple of hours the loading times of new maps are really slow (over 2-3min),
then i quit the game and restart it.. next loading scenes are really fast for the next minutes / hours (depends).

pls fix it.. maybe fail @ carbage collecting @memory?

sorry for bad english
(german)

[Laxe84]

I've noticed this as well. Thought it was my pc running hot or something... When loading after starting the game it loads between 5-10 seconds. Then after a few hours of playing it takes a while (never timed it but I would say a minute or two as well). Makes it quite frustrating when loading my last save game after being wiped out.

[ByblosHex]

It can't be a memory leak or it would affect everyone. I've had the game running for well over 24 hours without any slow down.



or maybe its specific to a certain area?

[Gaesadair]

ByblosHex wrote...

It can't be a memory leak or it would affect everyone.

This is not true. The memory not being freed might happen only when a certain driver is being called, or only on certain processors with certain chipsets due to differences in race condition resolution; there can be many system-specific reasons for memory leaks.

[ByblosHex]

Its a forums, so im not going to be 100% completely detailed and specific in every post I make. Obviously it could be a memory leak.

[Docjam]

I'm definately noticing some problems and there's a few scripted events that always trigger some sort of leak even if you JUST restarted the game.. do the event.. and your game will be f'ed up again (skill damage not taking place until 10 seconds after the animation, cutscenes not playing for 5 minutes after combat ended, loooooooooooong load screens, etc)..



One of them is the back alley fight after clearing the ruffians out of the pearl.



every time I do that fight.. either the cut scene won't play after combat ends.. I'll "lag" when doing skills during the fight, or the game will crash after I load into the marketplace after the fight is done and I've moved on (after having a really long load screen)..

[JironGhrad]

setting processor affinity fixes the slow down on around 75% of machines (according to the data I've been able to collect) setting it to CPU 1 only on 2 core units and CPU's 2 and 3 on Quad core units and CPU's 4,5,6 and 7 on i7's... after more than a week of researching and trying fixes with people on here I can definitively say that a majority of AMD-based Phenom, X2 and X4 processors have this issue as well as several series' of new Intel Core 2 Duo and Core 2 Quads. First gen i7s (920s and 950s) are the only two I've been able to link to this specifically...

[Pathalone]

JironGhrad wrote...

setting processor affinity fixes the slow down on around 75% of machines (according to the data I've been able to collect) setting it to CPU 1 only on 2 core units and CPU's 2 and 3 on Quad core units and CPU's 4,5,6 and 7 on i7's... after more than a week of researching and trying fixes with people on here I can definitively say that a majority of AMD-based Phenom, X2 and X4 processors have this issue as well as several series' of new Intel Core 2 Duo and Core 2 Quads. First gen i7s (920s and 950s) are the only two I've been able to link to this specifically...

So, how does one set affinity on the CPU?

[Hurrrr]

Err...please differentiate slow-downs from load-times, game frame rates getting choppy is a slowdown right?



Or do you mean the load times in this case?



Dunno how CPU affinity would affect the load times, except slowing mine down as Id only have one core chipping away at it!?



Dunno most of the techno babble, been out of the loop for a few years, so correct but don't flame plz

[GhoXen]

The more I play/replay this game, the less regretful I am about the time I spent 400 bucks on some memory sticks more expensive than my CPU on whim.

[Hurrrr]

God bless solid state hard-drives.



Wish theyd be a little fecking cheaper but they do seem to rock.

[Jam442]

Setting the game to run only on CPU 0 seemed to help me. though time will tell.

and for Pathalone: bring up the task manager with ctrl alt delete, hit the processes tab, and look for daorigins.exe.

right click and choose set affinity, clear all checks except for one. I did cpu zero.

edit. ohh and you need to have the game running too

Modifié par Jam442, 14 novembre 2009 - 03:22 .

[jercrow]

I tried the processor affintity trick with no major difference in load times. It seems to have drawn out the process somewhat so that it took slightly longer to get to the point of needing to save and restart. On the other hand, I experienced stutter and lag in a few larger battles that I never had before in comparably sized battles. While the long transition times are annoying, better that than lag time in battle!



Windows XP Home (2002) SP 3

AMD Athlon 64 X2 dual core 4600+ at 2.41 GHz

2 GB Ram

NVIDIA GeForce 8600 GTS

[Krobon]

They are still looking at it I believe, there is another post on the forum about this somewhere. They aren't sure what has caused it yet.



This problem is the same for nearly all computers however, no matter the specs. I'm sure they will fix it in the next patch.

[Docjam]

Hurrrr wrote...

Err...please differentiate slow-downs from load-times, game frame rates getting choppy is a slowdown right?

Or do you mean the load times in this case?

Dunno how CPU affinity would affect the load times, except slowing mine down as Id only have one core chipping away at it!?

Dunno most of the techno babble, been out of the loop for a few years, so correct but don't flame plz

It's not a framerate drop, it's in load times, which would include loading cutscenes after a battle.

For me I also notice poor responsiveness in combat as a symptom.  Framerate is normal, animations go off, but the effects of those animations are delayed.  I'll throw a fireball on my mage.. the boom will go off animation wise.  but the mobs hit by it won't take damage or be knocked down for several seconds, they'll still be moving around and attacking and may even run out of the area of the fireball's effect!  then they'll just suddenly get knocked over and take fire damage!  When that happens it's time to save, exit the game, and restart it.

[wruiter]

My problem...

when I start to talk to someone my frames go from 55 to 1, sometimes i can't even continue. I've done what seems like all the quick fix's that apply to my PC and none have helped. load times seem fine for me its only when I start to talk to an NPC. The save game then reload game trick does not work, setting the game to run off one core does not work, deleting all saves does not work and I've updated all my drivers still with no luck. At this point I can't Continue I'm in the Dwarf are I've done all side and main quests and I have to do this place to continue.

_________________

PC Specs:

Windows 7 64bit

Intel Core 2 Duo 2.4GHz

EVGA Nvidia GTX 260

G.Skill 8GB of ddr2 800

EVGA 780i Motherboard

Creative Sound Blaster X-Fi XtremeGamer

22" Acer monitor 1680x1050

640GB Hard Drive Western Digital 7200rpm

[Titius.Vibius]

Listen to JironGhrad, his fix really does work until a patch comes around that can address the perceived memory leak.

[goat-roper]

Well, for me the loading screens were terrible... i7920, 6GB Ram Dual 275 OC cards. So I did not think it was horse power issue. On a whim, I disabled the hyper threading capability on my i7 and screens went from 2 minutes to 2 seconds. I could not believe the difference it makes... If you have hyper threading capability - try disabling it !!!!

[ironshifter11]

affinity has absolutely not a thing to do with load times.....omg!? It control cores/threads
this game isn't a 100% port but it still has comprimises though, think about console load times, ask your self in other games have if you ever had to wait as long for screens to load? or better yet lets be totally honest and say that any main stream pc rig really would not have any issue streaming one encounter to another altogether.
Btw I think something is definitely wrong with the game, either a memory leak or over all degradation, I had to walk awy for sa @4 hour come back and peek at my desk top, guess what message I get, hard drive full....from 200gb to 485gb maxing it out.
I-720
6gbDDR3
ATI 5870
WD 500gb
Asus P6T Deluxe V2
WIN7

Modifié par ironshifter11, 16 novembre 2009 - 09:37 .

[JironGhrad]

ironshifter11 wrote...

affinity has absolutely not a thing to do with load times.....omg!? It control cores/threads
this game isn't a 100% port but it still has comprimises though, think about console load times, ask your self in other games have if you ever had to wait as long for screens to load? or better yet lets be totally honest and say that any main stream pc rig really would not have any issue streaming one encounter to another altogether.
Btw I think something is definitely wrong with the game, either a memory leak or over all degradation, I had to walk awy for sa @4 hour come back and peek at my desk top, guess what message I get, hard drive full....from 200gb to 485gb maxing it out.
I-720
6gbDDR3
ATI 5870
WD 500gb
Asus P6T Deluxe V2
WIN7

You clearly don't understand what CPU affinity is,  how multicore processing works, or what a memory leak is either.  The issue (and I have documentation now for well over 100 cases) is that load times on machines that exceed the requirements to run the game (sometimes substantially as in the case of the guy who switched off his i7's hyperthreading) are experiencing what appears to be issues with long load times and degraded performance. 

In a significant portion of these situations, the slow down is the result of the way that CPU's (mostly AMD but there are Intel processors with this issue as well) are passing the application back and forth between them.  By setting CPU affinity to a single CPU (Dual Cores and some Quad Cores) or two (Quad Cores) the Operating System will run nothing else on that processor.  So if you have a 2.4Ghz Dual Core and set affinity to only CPU 1 (Core 2) then it will make use of the entire 2.4Ghz which is significantly faster than it otherwise might be. 

A memory leak is a situation where memory is allocated (either by an application like a game or the OS) to the program and then left unused.  Because the memory is going unused the program (or OS) keeps adding additional RAM in an effort compensate until the RAM is used up, the page file may overflow and the system crashes. A memory leak is not something that can be fixed by tweaking hardware on any machine, nor can it be avoided by any user.  If a program has a true memory leak it will affect all users who operate the program and I can say with utmost confidence (after a stress test the other night, my game had been running continuously for 40 hours and I didn't see a load time over 45 seconds) that the game may have issues with how it handles processor interaction but the slow downs aren't actually a true memory leak. For those who are still reading and are interested.  I'm running a Pentium 4 3.2Ghz Hyper-threaded Single Core Processor, Over-clocked to 4.9Ghz (and technically this processor doesn't meet the minimum requirements to run the game), with 2Gb of RAM, a 512mb Radeon X1650 Series AGP graphics card (also reputed to be near the bottom of the pile) on Windows XP Pro SP3 (32-bit).  If anyone should be loading slow and lagging while playing, it's me; but I'm not.

[ZootCadillac]

Jiron has explained it in a way that most of you should be able to understand now.

Setting the cpu affinity is helping some people with game lag and stuttering issues and it's worth a try ( personally my game has been running sweet on my AMD X2 5200+ BE which is regularly overclocked and underclocked ) because you won't break anything and it's easily changed back.

There is very likely a memory leak. I have the game running for hours on end (it's always on ) and i do find the load times increasing as time goes on but I find that save and exit, reload is hardly a burden to deal with this. My load times don't struggle until a good 4-6 hours of game runtime and then the worse I can get is around a minute, maybe more in the Dwarf city. This may have something to do with me running a ram optimizer which is constantly clawing back unused and 'lost' allocated memory. I also have 8gb of usable RAM and 25GB available for swap space.



The main thing to remember is that your core model has nothing to do with a memory leak. It's a programming error and it's going to happen to everyone whatever their system it simply depends upon your system as to when and how badly it will affect you.



The bottom line is that if you have long load times between transitions you need to reload your game. The only fix lies with the devs and a patch and blaming your core or number of them is a non-issue regarding a memory leak.

[JironGhrad]

ZootCadillac wrote...

Jiron has explained it in a way that most of you should be able to understand now.
Setting the cpu affinity is helping some people with game lag and stuttering issues and it's worth a try ( personally my game has been running sweet on my AMD X2 5200+ BE which is regularly overclocked and underclocked ) because you won't break anything and it's easily changed back.
There is very likely a memory leak. I have the game running for hours on end (it's always on ) and i do find the load times increasing as time goes on but I find that save and exit, reload is hardly a burden to deal with this. My load times don't struggle until a good 4-6 hours of game runtime and then the worse I can get is around a minute, maybe more in the Dwarf city. This may have something to do with me running a ram optimizer which is constantly clawing back unused and 'lost' allocated memory. I also have 8gb of usable RAM and 25GB available for swap space.

The main thing to remember is that your core model has nothing to do with a memory leak. It's a programming error and it's going to happen to everyone whatever their system it simply depends upon your system as to when and how badly it will affect you.

The bottom line is that if you have long load times between transitions you need to reload your game. The only fix lies with the devs and a patch and blaming your core or number of them is a non-issue regarding a memory leak.

Ah, but you contradicted yourself... load times have virtually nothing to do with memory... they're entirely related to the processor. And as I pointed out, if it doesn't affect everyone it's not a leak.  My typical load time is 30-45 seconds (larger outdoor areas take longer and with my testing have no pattern of increasing it takes 45 seconds to enter the woods regardless of how long the game has been running), and as I pointed out, if you don't restart a memory leak will crash the system. A processor transfer problem (which is what I'm fully convinced this is) can create the effective appearance of a memory leak because you crash.  But the crash is caused by the CPU trying to transfer the program to the other core when the L2 cache is full.

[ZootCadillac]

What I was trying to say that if there is a memory leak which may or may not be the case, that if there is at the moment people are going to have to suck it up because a fix is not in our hands. ( that's where I was aiming, not suggesting long load times were NOT processor related but that if they were due to memory then we wait for a patch )

From startup on this game I don't see a transition load time of more than 10 seconds usually so after 6 hours running when they are getting to over 30 secind and up to a minute I'm pretty sure that's got nothing to do with my processor which would have to have the problem all of the time, unless of course it's running out of address space in the RAM )

[JironGhrad]

I think it's more likely Zoot, that you're experiencing a cache buffering issue (which is why I'm so convinced it's processor related). It may well be game programming that's causing the processor to waste L2 cache as it passes the game application from core to core.



The particular truth is that I wish people would stop slinging around "memory leak" to sound smarter. The simple answer is to ask the question, "Is everyone having a problem?" If even 1 person says "no problem" then it's probably not a memory leak, The moral of the story is that a few minutes on Google can turn the "sound smarter" into actually being smarter.

[NikiJohnElvis]

AMD FUSION for gameing and AMD OVERDRIVE

it worked like a charm for me, no more long load times, better grafic performance,...

The game is finaly playable for me trough this



AMD Phenom™ 9500 Quad-Core Processor (4 CPUs), ~2.2GHz

4094MB RAM

GeForce 9800 GT



Try it you will like it