338 réponses à ce sujet

[Thandal N'Lyman]

Darth_Trethon wrote...

At this point the biggest and most important fix I care about is still missing.....why aren't they fixing the Sentinel armor in Awakening and that special sword so they can appear properly?

Sorry, just can't get worked up about a particular piece of gear that doesn't happen to work correctly from one game environment to the next.

Stuff is... well... just stuff.  It wears out, it breaks, it gets lost.  Not a big deal.  Even losing Starfang between Origins and Awakening just meant that I had to make do.  Pissed, but moved on.

Claiming that "Sentinel Armor" not appearing is somehow on par with "it crashes and dumps the player to the desktop every time there's a large combat scene" (which is what "the biggest and most important fix" means) is just absurd!

Game mechanics (e.g "stop the crashes")  first.  Plot points/flags/triggers (e.g. Morrigan/Alistair/Zevran dialogue fixes)  second.  Attributes (e.g. "dex for daggers", or pickpocketing) third.  Abilities for items (e.g. "weakens nearby Darkspawn") fourth.  Items themselves?  A very, very distant fifth!  After all, there's always other stuff.

Modifié par Thandal NLyman, 14 juin 2010 - 04:26 .

[Chairon de Celeste]

That a fix isn't confirmed yet doesn't meam they
don't work on it

[Franpa]

Apex Sammoth wrote...

Feraele wrote...

Apex Sammoth wrote...

Lord Gremlin wrote...

Please, fix PS3 Blight Queller trophy bug already! It's ridiculous: this trophy is glitched and never unlocks. It's not uncommon and such things are usually getting fixed. So please, fix it already.

Also: PS3 version looks better than 360 and people should understand that bugs have nothing to do with raw processing power or something. Nothing at all. It's perfectly possible to create a game that runs perfectly on PSP and almost unplayable on 360 and PS3.

The PC version Looks better then Both I fail to see the point of this argument on a patch thread. What your not understanding about what was said in that post was that the way the games are developed on the PS3 is a bit harder to port over compared to the 360. So it is a bit easier to patch the 360 over the PS3 simply because they are developed on the same format as the PC.  Actually there are some major bugs with Dual Cores / Etc and other PC Configs with this game so yes Processing Power sometimes has some issues. If the game is coded wrong not to use certain resources it can cause anything from Memory Leaks to the well known %100 Processor issue with this game.

Hmmm that could be whats causing "some" of the slow motion moving of characters that I see from time to time on my PC.     I have an AMD core duo machine.   I've seen the 100% processor issue, many times.    Always thought it was some sort of memory leak,  but as I read in the PC tech forums,  (or somewhere)  the layman always refers to "memory leaks" when sometimes its not a memory leak but something else.   What that might be ..I don't know.

Anyways hope the Bioware team is on top of this.    Even still, if I am good about logging out and restarting, or rebooting my machine,  I can go and play again.     Just annoying crashing in Denerim just before the Final Battle, after killing the first darkspawn general etc.   lol       Or sometimes when I am about to finish off the Archdemon.    A little frustrating.     But I always tell myself, hey another chance to do it BETTER.  lol 

Correct and that is what I call Gamebreaking. This is not a Dex bug or a quest line bug. This is a MAJOR problem. You should not have to restart the game or even change any core affinity. Im sorry but, I don't buy into the Game Works but you have to do "X".  Esp when the BOX says I am well above the Sys Req. Keynote here is I don't have to do anything when playing other game including games that have higher System Req.

I do hope there is some sorta fix for this in the Upcomming patch. Any Info on these fixes would be nice Bioware ?

The problem described isn't a memory leak, memory leaks are when a part of a program becomes unstable either due to bad coding or defective hardware and repeatedly allocates RAM to it self over and over until there is no RAM left at which point it either lags badly or crashes.

The 100% CPU is NOT a bug and it has been that way since the Windows 95 days. There are ways developers can reduce CPU usage when the CPU isn't required but it comes at the cost of accurate timing/switching between threads. You typically see such energy saving measures in hobby programs like Emulators and mobile applications for laptops etc.. Windows XP, Vista and 7 all feature I believe special "Intel" or "amd" drivers which will split the load of single threaded processes over multiple cores/processors seamlessly which makes it very hard to see if a program truly uses 100% of a CPU core without setting the programs CPU Affinity to a single CPU/Core.

[oblivionenss]

Franpa wrote...

Apex Sammoth wrote...

Feraele wrote...

Apex Sammoth wrote...

Lord Gremlin wrote...

Please, fix PS3 Blight Queller trophy bug already! It's ridiculous: this trophy is glitched and never unlocks. It's not uncommon and such things are usually getting fixed. So please, fix it already.

Also: PS3 version looks better than 360 and people should understand that bugs have nothing to do with raw processing power or something. Nothing at all. It's perfectly possible to create a game that runs perfectly on PSP and almost unplayable on 360 and PS3.

The PC version Looks better then Both I fail to see the point of this argument on a patch thread. What your not understanding about what was said in that post was that the way the games are developed on the PS3 is a bit harder to port over compared to the 360. So it is a bit easier to patch the 360 over the PS3 simply because they are developed on the same format as the PC.  Actually there are some major bugs with Dual Cores / Etc and other PC Configs with this game so yes Processing Power sometimes has some issues. If the game is coded wrong not to use certain resources it can cause anything from Memory Leaks to the well known %100 Processor issue with this game.

Hmmm that could be whats causing "some" of the slow motion moving of characters that I see from time to time on my PC.     I have an AMD core duo machine.   I've seen the 100% processor issue, many times.    Always thought it was some sort of memory leak,  but as I read in the PC tech forums,  (or somewhere)  the layman always refers to "memory leaks" when sometimes its not a memory leak but something else.   What that might be ..I don't know.

Anyways hope the Bioware team is on top of this.    Even still, if I am good about logging out and restarting, or rebooting my machine,  I can go and play again.     Just annoying crashing in Denerim just before the Final Battle, after killing the first darkspawn general etc.   lol       Or sometimes when I am about to finish off the Archdemon.    A little frustrating.     But I always tell myself, hey another chance to do it BETTER.  lol 

Correct and that is what I call Gamebreaking. This is not a Dex bug or a quest line bug. This is a MAJOR problem. You should not have to restart the game or even change any core affinity. Im sorry but, I don't buy into the Game Works but you have to do "X".  Esp when the BOX says I am well above the Sys Req. Keynote here is I don't have to do anything when playing other game including games that have higher System Req.

I do hope there is some sorta fix for this in the Upcomming patch. Any Info on these fixes would be nice Bioware ?

The problem described isn't a memory leak, memory leaks are when a part of a program becomes unstable either due to bad coding or defective hardware and repeatedly allocates RAM to it self over and over until there is no RAM left at which point it either lags badly or crashes.

The 100% CPU is NOT a bug and it has been that way since the Windows 95 days. There are ways developers can reduce CPU usage when the CPU isn't required but it comes at the cost of accurate timing/switching between threads. You typically see such energy saving measures in hobby programs like Emulators and mobile applications for laptops etc.. Windows XP, Vista and 7 all feature I believe special "Intel" or "amd" drivers which will split the load of single threaded processes over multiple cores/processors seamlessly which makes it very hard to see if a program truly uses 100% of a CPU core without setting the programs CPU Affinity to a single CPU/Core.

Try .net framework 4.0 is said to fix it.

Modifié par oblivionenss, 14 juin 2010 - 07:37 .

[Yrkoon]

Thandal NLyman wrote...

Darth_Trethon wrote...

At this point the biggest and most important fix I care about is still missing.....why aren't they fixing the Sentinel armor in Awakening and that special sword so they can appear properly?

Sorry, just can't get worked up about a particular piece of gear that doesn't happen to work correctly from one game environment to the next.

Stuff is... well... just stuff.  It wears out, it breaks, it gets lost.  Not a big deal.  Even losing Starfang between Origins and Awakening just meant that I had to make do.  Pissed, but moved on.

Claiming that "Sentinel Armor" not appearing is somehow on par with "it crashes and dumps the player to the desktop every time there's a large combat scene" (which is what "the biggest and most important fix" means) is just absurd!

Game mechanics (e.g "stop the crashes")  first.  Plot points/flags/triggers (e.g. Morrigan/Alistair/Zevran dialogue fixes)  second.  Attributes (e.g. "dex for daggers", or pickpocketing) third.  Abilities for items (e.g. "weakens nearby Darkspawn") fourth.  Items themselves?  A very, very distant fifth!  After all, there's always other stuff.

I, for one, don't see the need to catagorize bug fixes into "levels of importance".  Nor do I think this has to be an "either fix this, or else fix that" thing.

The smaller the bug, the easier it is to fix I would think, which means one patch can contain the core game stability fixes  AND a bunch of the lesser 'cosmetic' fixes, which are probably nothing more than simple coding oversights and wouldn't take much dev time to address and squash anyway..

Modifié par Yrkoon, 14 juin 2010 - 08:52 .

[Callidus Thorn]

Yrkoon wrote...

Thandal NLyman wrote...

Darth_Trethon wrote...

At this point the biggest and most important fix I care about is still missing.....why aren't they fixing the Sentinel armor in Awakening and that special sword so they can appear properly?

Sorry, just can't get worked up about a particular piece of gear that doesn't happen to work correctly from one game environment to the next.

Stuff is... well... just stuff.  It wears out, it breaks, it gets lost.  Not a big deal.  Even losing Starfang between Origins and Awakening just meant that I had to make do.  Pissed, but moved on.

Claiming that "Sentinel Armor" not appearing is somehow on par with "it crashes and dumps the player to the desktop every time there's a large combat scene" (which is what "the biggest and most important fix" means) is just absurd!

Game mechanics (e.g "stop the crashes")  first.  Plot points/flags/triggers (e.g. Morrigan/Alistair/Zevran dialogue fixes)  second.  Attributes (e.g. "dex for daggers", or pickpocketing) third.  Abilities for items (e.g. "weakens nearby Darkspawn") fourth.  Items themselves?  A very, very distant fifth!  After all, there's always other stuff.

I, for one, don't see the need to catagorize bug fixes into "levels of importance".  Nor do I think this has to be an "either fix this, or else fix that" thing.

The smaller the bug, the easier it is to fix I would think, which means one patch can contain the core game stability fixes  AND a bunch of the lesser 'cosmetic' fixes, which are probably nothing more than simple coding oversights and wouldn't take much dev time to address and squash anyway..

So you then classify a bus that crashes the game to be just as important as one that stops armour appearing? I'm sorry, but that that's just ridiculous. The greater affect a bug has on the gameplay, the more it needs to be fixed, therefore it's more important. Implying that all bugs are equally important sounds like you're trying to justify a "everything broken in the game must be fixed" viewpoint, which just isn't feasible. Every game has bugs to some degree, if they don't affect gameplay too much, they don't really need to be fixed. They can't fix everything, an "Either this, or that" approach is inevitable, and I'd rather they stopped the game breaking bugs than make sure a set of armour appears.

[Reggler]

Yrkoon wrote...

The smaller the bug, the easier it is to fix I would think

Not necessarily - small bugs can be hard to spot, while some that seem rather complex may actually be very
easy to fix. And sometimes, you spend days looking for the spot in the code something goes wrong at, only to find that the change needed is really minor.

This is why I'm not mad about patching taking long, only that we were kept in the dark about any progress. But since this is no longer the case: Thank you for the updates, Bioware!
Please keep us informed in this way, and in return I promise to not be angry anymore. Noble, ain't I

Modifié par Reggler, 14 juin 2010 - 09:20 .

[BrunoB1971]

Just 2 add my 2 cents, i think that evry bug is important. A bug means that the product is not working as intended.



Now the problem is, is it really a bug or not.



Now also you need to prioritze what needs to be fixed first but also make sure that everything is fixed no matter what. Like i said i would rather see Bioware take more time to do a correct patch than trying to do a MacGyver band aid quick fix.



I am sure that they have a debugger for the game to spot troubelsome coding. Plus the game is broken in parts for different functions of the game. So therefore you can look into a specific module to troubleshoot the problem.



The dev tool that they have given the fans is an example of a debugger because you can go in and change things and fix them.



I think the problem why it is takign so long to debug is that they have to do the change or changes, test it and make sure it does not unbalance the game in some shape or form.



People can say they have a bug and they issue a fix but if it unbalances the game then they have to make sure it does not, they may have to wash, rinse and repeat several times before coming to a point where it is acceptable.



I am not a fool and i completely understand the complexity of this game. all the little parts have to come together to form a cohesive thing and that is why it is harder to fix than let's say a first person shooter because there is tons of statistics that come into play to make the game.



It is like translating a dictionnary for one language to another, you need to make sure that what you do here does not invalidate what is said some place else.



That is why QA is so important in thsi kind of time. If they always do a mediocre job and let pass too many things then the game will pay and the devs will continuously have to fix the game.



I think the QA cycle at this time have to be serious about what they are doing and reject anything that is unacceptable instead of letting things pass that will come and bit you in the butt later down the road. They have to do this within time constraints but they have to do a proper job too...



nuff said for now...

[Drewbahr]

I can't promise to stop being angry like Reggler here, but I'm in the same boat - I understand that bugs can take time to fix, but was (and still am) very upset at the fact that Bioware wasn't actually saying ANYTHING about their progress in fixing any of the game-breaking bugs that their game has.

[ladydesire]

Callidus Thorn wrote...

So you then classify a bus that crashes the game to be just as
important as one that stops armour appearing? I'm sorry, but
that that's just ridiculous. The greater affect a bug has on the
gameplay, the more it needs to be fixed, therefore it's more
important. Implying that all bugs are equally important
sounds like you're trying to justify a "everything broken in the
game must be fixed" viewpoint, which just isn't feasible. Every
game has bugs to some degree, if they don't affect gameplay
too much, they don't really need to be fixed. They can't fix
everything, an "Either this, or that" approach is inevitable,
and I'd rather they stopped the game breaking bugs than
make sure a set of armour appears.

That's just it; to those people that haven't noticed the other bugs (for whatever reason), a set of armor that doesn't display properly is gamebreaking. Is it something that should take priority over game crashes? No, but it should still be fixed at some point. It would also be nice if Bioware would make clear whether some things that are classified as bugs by players are actually working as intended or not (like +healing received items).

[Reggler]

@Drewbahr: True, that was bugging me as well - but they are making ammends by posting threads like this one. If they keep it up, I'm placated.



@BrunoB1971:

Unfortunately, a debugger rarely delivers the exact spot of erroneous code - if it did, my own job would be ever so easy And quite often, it's not a single spot, but a problematic interleaving of several innocent pieces of code.

I totaly agree with you about them needing to be especially precise about QA at the moment though.

[ChaosRaident]

what is this patch for? ps3,xbox,pc or all?

[Reggler]

ChaosRaident wrote...

what is this patch for? ps3,xbox,pc or all?

See OP, Xbox has been mentioned.


@Julian_Kraynog:
I have the same issue - however, I run Dragon Age on a single core system, so I'm not surprised that stuff that most probably relies on multi-threading behaves strangely. I'm guessing that damage calculations are in a different thread than graphics and movement.
So if you run a single core system as well, this might not actually be a bug, but rather a problem of being below the minimum requirements.

Modifié par Reggler, 14 juin 2010 - 11:44 .

[Servius the bear]

Not been having issues at all Runs perfectly. But I always patch up if a patch comes out.

[Drewbahr]

Servius the bear wrote...

Not been having issues at all Runs perfectly. But I always patch up if a patch comes out.

"Not having issues" is not the same as "bug-free game".  I'm going to go out on a limb here and assume that you play on the PC - considering the "I always patch up if a patch comes out" is one hint, as is the "no issues" statement.

If that is the case, then you're lucky - the PC has received extensive patch support compared to the PS3 and 360 versions of the game.  Not to mention, the PC benefits from having a player base that can build mods to work around the bugs and issues that the release version of the game has.  The 360 and PS3 do not benefit from that.

If you're on a PS3, or worse yet - a 360 - then consider yourself quite fortunate to have not encountered any bugs.

[Servius the bear]

I would never put these games on consoles. I am one for consoles are for racing and footy games only.



Now out of the many systems I run. I run two sep systems for my games. One runs with out game patches at all and the other runs with game patches. I have not seen any issues. Even those having issues with DLC's. I have never had those issues nor been able to recreate there problem.



So I can only speculate on a fix going by what they say. Now to modding etc I have done that for more than ten years of my games carreir. When I started playing comp games way back in the old days.

[Lintanis]

why shouldnt consoles have rpg's??????????

Been playing rpg's on consoles since the Sega Mega Drive lol

[ladydesire]

Reggler wrote...


@Julian_Kraynog:
I have the same issue - however, I run Dragon Age on a single
core system, so I'm not surprised that stuff that most probably
relies on multi-threading behaves strangely. I'm guessing that
damage calculations are in a different thread than graphics
and movement.
So if you run a single core system as well, this might not
actually be a bug, but rather a problem of being below the
minimum requirements.

He might also be on PS3, as there have been similar complaints from PS3 owners.

[Servius the bear]

Theres just not as much freedom I feel on Consoles. I have always been like that.

[Reggler]

ladydesire wrote...
He might also be on PS3, as there have been similar complaints from PS3 owners.

Interesting, thanks for pointing this out. I was looking around for info on this "bug" when I started playing Dragon Age when it came out, but didn't find much. I may have to look again some time.

[Thandal N'Lyman]

Yrkoon wrote...

I, for one, don't see the need to catagorize bug fixes into "levels of importance".  Nor do I think this has to be an "either fix this, or else fix that" thing.

The smaller the bug, the easier it is to fix I would think, which means one patch can contain the core game stability fixes  AND a bunch of the lesser 'cosmetic' fixes, which are probably nothing more than simple coding oversights and wouldn't take much dev time to address and squash anyway..

I will assume that this comment comes from someone who has not had to mange complex, interdependent, multi-person projects in heterogeneous technical environments.  If there are infinite resources to devote to the effort, than everything can be "Priority One".  Given that this is the real, not the ideal world, and that someone has to decide how to allocate whatever (by definition, limited) resources they have available, then assigning severity/importance ratings is an essential (and early) step.  "First things first" is a useful tenet, but someone actually has to determine what's "first".

[Zy-El]

Speaking as one playing on the PC, I'd rather Bioware fix the major, game-breaking bugs that modders cannot. I trust Qwinn and other modders to catch the minor bugs/script errors and with Bioware doing the major bugs, I will have as close to a "perfect" game in Dragon Age as I could hope for. I'm glad they're also tackling the Awakening bugs which are quite extensive.

The Vigilance appearance bug is not something I'd consider major or game-breaking by any stretch. Get real, people, it's just a sword graphic and does not take away from the weapon's performance in battle! You're going to lose the sword in the end anyways so don't get too emotionally attached to it!

[ladydesire]

Zy-El wrote...

Speaking as one playing on the PC, I'd rather Bioware fix the
major, game-breaking bugs that modders cannot. I trust
Qwinn and other modders to catch the minor bugs/script
errors and with Bioware doing the major bugs, I will have as
close to a "perfect" game in Dragon Age as I could hope for.

Speaking as a modder that is working on a custom companion mod (I also hope I'm speaking for other modders doing that) I would rather have Bioware fix game dialog issues that the modding community has fixed, so there is a unified base for companion mod compatibility. As it is, we have to either incorporate community fixes into our projects, or warn players using our companion mods of incompatibility issues.

[Zy-El]

Yes, that would be my preference too, LadyD, but Bioware only has so much resources devoted to patching. Only they can fix the game-breakers that modders can't touch.

Just tell everybody to install Qwinn's Fixpatch as a base install. He has fixed the majority of scripting and dialogue bugs with the help of the very same modders who worked on the specific dialogue mods.