161 réponses à ce sujet

[andysdead]

enderandrew wrote...

Again, if the leak affects all AMD quad-core processors, it should affect me. If it affected all Windows 7 users, it should affect me. If it affected all 64-bit users, it should affect me. If it affected AMD/ATI video cards, it should affect me.

I've heard all those things. Yet I don't have a memory leak.

It can't be that it affects all AMD quad-core processors. The only way I could even see that being a possibility is if the game has optional SSE5 instructions for those processors, but I HIGHLY doubt that. They don't even put out 64-bit binaries, nor take advantage of DirectX 10 or 11. I really highly doubt they're using SSE5 instructions.

It can't possibly affect all Windows 7, 64-bit, or ATI users either.

It is only affecting a subset of users.

What game companies should do is allow the game to be started in a debug mode with verbose logging via a command line switch. When players have problems, they start the game in verbose logging mode, and upload logs to EA support.

That would enable them to better identify the actual issues at hand.

I, formerly, was running an AMD Phenom 9500 and a GeForce 9800gt. With those specs I was experiencing this load time bug.

I then upgraded to a GeForce GTX275, and while my graphics capability significantly improved, the load time bug still existed.

I then upgraded my processor to a Phenom II 940, which for all intents and purposes solved the problem.

At first I believed the problem to be completely gone; however, upon further playing, I have realized that the increasing load times bug is still an issue...  it's just much less obvious than it was before, and only becomes apparent after a few hours of playing.

This leads me to believe that it is likely a problem with most if not all AMD processors, and while some may not exhibit the problem as quickly or obviously as others, the problem still exists, and the reason that folks like you aren't reporting any issue is because you haven't been playing long enough at a single sitting to experience it.

[Gliese]

I more or less take memory leaks for granted after playing Oblivion, FO3 and several other games recently plauged by them. I don't consider it a serious problem as long as it's cleared by a reload or console command every few hours. It needs to be fixed but I'd rather attention was focused on bugs and broken mechanics first that are out of the player's control without modding.



I'm holding off on dling the new patch until the rally issue has been taken care of.

[Olduwan]

I dunno what Bioware did, but this patch fixed all the problems for me. I turned off cpu affinity, but still letting ati drivers override video settings (uncheck let application control settings). No crashes and graphical glitches are gone!



I have a core 2 duo with 4gb of ram and radeon 4870.

[Vantharas]

All I'm going to say is for me this patch is garbage. I use to be able to play the game. Then I patched to 1.02 now its saying unable to find supported video card lol.

[roybm]

im a bit disappointed with what the patch gave us.

I do not really care if an enemy drops more health potions, or a empty corpse is lootable.

Why did they not fix the loading times, memory leaks, and crashes so many people are having?

It is as if they just patched the game and made it easier than it already was for all the crying kids that complained about lack of potions and money, and said forget the other problems.



As andysdead said... yes there is a HUGE problem with loading times after playing for 2 or more hrs. I am almost positive this is from a memory leak. It happens when I have had the game going for about 3 or more hrs and all of a sudden everything in the game seems to take up to a minute to load (even when opening the inventory in game)



I am hoping this is just a quick fix patch to calm people down some and the stuff that needs to be fixed will be fixed in the next one.



:: Praying Bioware does not become EA and not care about their customers ::

[Gary Lancel]

I hadn´t any problem playing patch 1.01. But after the patch 1.02 I had a crash on Windows XP (AMD 5200+ dual core processor).



Blue screen and restart.



I think its because that 100% CPU issue that overheated the chipset. I never had this type of crashed with any other game.



I am disapointed. I thought they would fix that.

[Carcassjelly]

Dragon Age runs great so far.. my i7-920 proc. and outdated 4850 seem to be holding up. Nothing can be as bad of an experience as freakin Bioshock, aka to me as pc crasher!

[kristheb]

enderandrew wrote...

I still average about 4 second load times. I've never seen these horribly long load times or memory leaks.

lucky us

[Selvec_Darkon]

Little disappointed nothing has addressed the sudden drop in load times and framerate in this patch. Thought that would be right up there for things urgently needing fixing.

It's nothing to do with a memory leak I have been told. But rather the game is simply a RAM hog. It overuses RAM, fills up 2gb's really fast. Basically the game needs to have it's RAM use looked at, as it has a bloody stranglehold on it which gets worse as the game fills up said memory.

I'd hazard a guess at people not noticing the issue probably using 62bit OS's and 4 gigs, or over, of ram.

Modifié par Selvec_Darkon, 08 décembre 2009 - 10:58 .

[BrunoB1971]

as i have posted people would need to start using "event viewer" ( google it up) it is a tool used by most IT people to troubleshoot pc's. For example i used event viewer and was able to determine that an nvidia installer was not erasing a specific dll when i was updating my nvidia video driver which let me pc to have mutliple versions of the same dll which then cause the game i was playing to crash because the pc did not know which version of that specific dll to use.



the learning curve to use this tool is somewhat minimal, the hardest part of this is finding the tool and then learning where to go and read the reports the event viewer generates.



A lot of people are saying that they have this and that about the game but they really have no clue if it is really the game or their hardware or a windows or software problem outside the game. event viewer would help you put you on the right track on fixing the problem.



Plus if people start reporting here that nv4cpld.dll is appearing a lot of times as a cause of crash around the same time as i was playing the game instead of saying that the game crashes all the time, then they would know that nv dll's are from nividia and that the cause of the crash is related to an nvidia driver that is not jiving with the game.



People need to start using the windows diagnostics tools to help themselves and make EA and Bioware see that what you are saying is true with a "true" reason to support your statement. I have read at least hundreds of time over that the game as memory leaks...then prove to EA what is at fault...it is as simple as that, otherwise there is no reason for them to do anything "just because you say so"....





peace

[Roshin]

Matthew Young CT wrote...

most people have no dlc issues

Which is nice for those people, but it doesn't help those of us who do. I thought that technical issues like this would be a priority, but I guess not.

[Matthew Young CT]

im quite sure its a priority. something simply being a priority doesnt make it simple to fix though. it likely got bumped to 1.03

[ArminW68]

Folks, you all need to cool down a bit, follow the golden rule (engage brain before complaining ) and run a little reality check before engaging in the usual internet hobby of bickering about things you don't have the slightest clue about.

I don't know a thing about EAs or Bioware's priorities, I have no idea just how many people are working on bugfixing, patching and QA/QC. But a bit of common sense and general project management will apply.

Having a look at the patch details reads like a comprehensive list of "known issues that are quick and easy to fix".

Everything in there can probably be done by altering the game's data files, logic scripts and single modules. Most probaly require little to no actual programming/decompiling/debugging work and will be handled by a completely different group of people than those who work on things like the actual game engine, data handlers, graphic engine and the like. HAve a look at the dcredits for one. Different teams, entirely different type of work needing to be done.

So, is there any reason not to fix the quick and easy things, while another team works on the tough ones that require much more effort, probably reprogramming parts of the engine, excessive testing? Hardly.

Now, on EA/BWs information policy, that's an entirely different matter. Would it really hurt to publish patch 1.02 with a short statement along the line of  "OK folks, here's one with a lot of quick and easy fixes while we're still woking on the more complicated technical issues. Those will be done asap, we apologize for the inconvenience"?

Now, would it?

[roybm]

Event viewer is not going to always post when a " Memory Leak " is occurring in a game.

That is something EA/Bioware will have to fix on their own since we do not have the source code for the game, and im taking a wild guess here but i am sure the average user here is not a pro at c++, and code debugging. (I am sure some are good at it but that would not really consider them as average now would it)

The only easy way to know if the game is causing a memory leak would be to open task manager and see if the game is using excessive amounts of memory. (still this may not tell you 100% if it is)

A leak occurs when the memory is not freeing itself up properly and just keeps trying to store it where there is not room for it anymore. This is where we are getting them huge slowdowns after having the game running 3+ hours.

Also keep in mind that not every computer will have this problem as everyone's computer is different.

All we can really do is give our hardware specs, OS of choice, the problem occurring and hope a fix will come from it.



I think it would be a safe bet to say its this game causing it (not hardware), since no other game / software I use is suffering from this problem.

I am tech savvy, but no code debugger. If i was, trust me, I would have posted the exact problem, than i would have fixed it myself and released a patch for it before EA/Bioware came up with one

[amrose2]

Load time optimization should've been priority



It was the very first thing they fixed in The Witcher too, and for good reason: It's the most gamebreaking

[Foufoug]

ArminW68 wrote...

Folks, you all need to cool down a bit, follow the golden rule (engage brain before complaining ) and run a little reality check before engaging in the usual internet hobby of bickering about things you don't have the slightest clue about.

I don't know a thing about EAs or Bioware's priorities, I have no idea just how many people are working on bugfixing, patching and QA/QC. But a bit of common sense and general project management will apply.

Having a look at the patch details reads like a comprehensive list of "known issues that are quick and easy to fix".

Everything in there can probably be done by altering the game's data files, logic scripts and single modules. Most probaly require little to no actual programming/decompiling/debugging work and will be handled by a completely different group of people than those who work on things like the actual game engine, data handlers, graphic engine and the like. HAve a look at the dcredits for one. Different teams, entirely different type of work needing to be done.

So, is there any reason not to fix the quick and easy things, while another team works on the tough ones that require much more effort, probably reprogramming parts of the engine, excessive testing? Hardly.

Now, on EA/BWs information policy, that's an entirely different matter. Would it really hurt to publish patch 1.02 with a short statement along the line of  "OK folks, here's one with a lot of quick and easy fixes while we're still woking on the more complicated technical issues. Those will be done asap, we apologize for the inconvenience"?

Now, would it?

+1 ^^

[BrunoB1971]

roybm wrote...

Event viewer is not going to always post when a " Memory Leak " is occurring in a game.
That is something EA/Bioware will have to fix on their own since we do not have the source code for the game, and im taking a wild guess here but i am sure the average user here is not a pro at c++, and code debugging. (I am sure some are good at it but that would not really consider them as average now would it)
The only easy way to know if the game is causing a memory leak would be to open task manager and see if the game is using excessive amounts of memory. (still this may not tell you 100% if it is)
A leak occurs when the memory is not freeing itself up properly and just keeps trying to store it where there is not room for it anymore. This is where we are getting them huge slowdowns after having the game running 3+ hours.
Also keep in mind that not every computer will have this problem as everyone's computer is different.
All we can really do is give our hardware specs, OS of choice, the problem occurring and hope a fix will come from it.

I think it would be a safe bet to say its this game causing it (not hardware), since no other game / software I use is suffering from this problem.
I am tech savvy, but no code debugger. If i was, trust me, I would have posted the exact problem, than i would have fixed it myself and released a patch for it before EA/Bioware came up with one

I agree with you, But by the same token i am wondering if some drivers are mature enough to make the game work properly, especially video drivers from Ati which seem to plague player.


the best thing would be an error reporting tool from the game itself...why there is none, i do not know, you would imagine that a huge game like this would require a tool like this for debugging and it should have been there on release since there is no way to make a big huge rpg without having bugs....

peace

[Gunny5821]

I wasn't having problems before and none now so thats a good thing. The one thing I did notice is my online connection stays connected, where as before it was timing out.



Gunny

[purplesunset]

Hmmm...two things about this patch worry me:

1. It doesn't address the various technical issues that people have been having (at least not directly, perhaps indirectly?)

2. 

Many of the fixes affecting balance, gameplay, or plot scripting are
already included in the Xbox 360 and PlayStation 3 versions of Dragon
Age: Origins .

Does anyone else see something wrong about number 2?

Remember back when Bioware said that the delay  and the inclusion of consoles would not  affect the PC? Then how come the consoles have already implemented things which are broken on the PC?

[andysdead]

roybm wrote...

there is a HUGE problem with loading times after playing for 2 or more hrs. I am almost positive this is from a memory leak. It happens when I have had the game going for about 3 or more hrs and all of a sudden everything in the game seems to take up to a minute to load (even when opening the inventory in game)

I don't think it's a true memory leak.

My RAM and hard disk space have not changed, the only things I've changed have been the processor and GPU, and the thing that improved the situation was the processor.

If I had upgraded my hard drive and seen improvement, or increased the amount of RAM i have and seen an improvement, then it would likely be a memory leak problem.

What we are experiencing right now may mimick the effects of a memory leak, but I don't believe it is one.

[purplesunset]

What we are experiencing right now may mimick the effects of a memory leak, but I don't believe it is one.

Yesterday, I spent almost the entire day reading forums around the internet about the technical issues people have been having with Dragon Age. (So you could imagine my dissappointment with 1.02)

I even used google's wonderful cache system to read the archived Dragon age forums.

I learnt a lot of things that I wanted to share with you guys in one LONG, GIANT THREAD, but I will have to hold back on that and contact some DA mod creators first (they have way more technical knowledge than me).

You're right though. It's not a memory leak, although for all intents and purposes, it behaves like one.

Dragon Age seems to be a game which is programmed to use up as much resources as possible in a short time. If you've got any RAM available, it will suck all that up in a fast amount of time. For some systems, this would be a great way to optimize performance. But for people with older cards and dual cores, and quad cores, this could also potentially lead to severe performance issues that look like but is not a memory leak.

Modifié par purplesunset, 08 décembre 2009 - 02:36 .

[Matthew Young CT]

ya theres no way its a memory leak, or just a memory leak. too many people are getting it soon after starting the game with 8gig memory, others never get it, many get it without the game using much memory.



theres something wrong obviously, but memory leak it does not appear to be.

[gibb0n85]

andysdead wrote...

roybm wrote...

there is a HUGE problem with loading times after playing for 2 or more hrs. I am almost positive this is from a memory leak. It happens when I have had the game going for about 3 or more hrs and all of a sudden everything in the game seems to take up to a minute to load (even when opening the inventory in game)

I don't think it's a true memory leak.

My RAM and hard disk space have not changed, the only things I've changed have been the processor and GPU, and the thing that improved the situation was the processor.

If I had upgraded my hard drive and seen improvement, or increased the amount of RAM i have and seen an improvement, then it would likely be a memory leak problem.

What we are experiencing right now may mimick the effects of a memory leak, but I don't believe it is one.

True, it seems like faulty memory management than leaking; a leak would cause the game to try to write to unallocated memory.  I have 6 gig of ram (64 bit OS) , the game only seems to use under a gig for me. Not that it could use 6 anyway being a 32 bit app. 

[agentjake4]

Is there a way to downpatch to 1.01?

[Matthew Young CT]

doubt it it modifies various files in the patching process. would need to reinstall