Bioware, rushing, and lots and lots of bugs...
#26
Posté 09 septembre 2010 - 12:27
Now Awakening... That game had so many giant bugs that I can't believe that it's a BioWare product. Please don't ever, ever rush something like that again. Please.
#27
Posté 09 septembre 2010 - 12:28
Thats Bioware's fault, not ours, why should the gameplay for the gamer suffer as a result? If it wasnt for us there would be no Grey Wardens!
Modifié par LucianTansey, 09 septembre 2010 - 12:31 .
#28
Posté 09 septembre 2010 - 12:29
Luckily I've had a mostly bug-free experience with Dragon Age so far, and the ones I have experienced have been fairly minor. What I mostly hope is that they have a faster and more comprehensive patching cycle for DA2 - I know a lot of players have been frustrated that BioWare knows about the error they've experienced but haven't managed to do anything about it in four patches and nearly a year.
#29
Posté 09 septembre 2010 - 12:32
#30
Posté 09 septembre 2010 - 12:32
In DAO I never noticed any major bugs apart from some wrong codex entries and once a wrong epilogue card. Awakening was worse and even there the only major bugs were that I didn't get Vellana's random encounter quest and Sigrun's sidequest. I never came across any game breaking bugs.
So I have to say I'm pretty pleased with their games. For me they're pretty much bug free, even when they make cuts they're never noticable. The worst game in that I played was kotor2 whose whole ending sequence was a broken mess.
#31
Posté 09 septembre 2010 - 12:32
Andrastee wrote...
Frankly, BioWare have never been very good with bugs. I think it's because there's so much content in their games, it's impossible to get rid of all potential errors. You should see the change list for the community patch released for BGII. (I think my favourite Baldur's Gate bug is the one with the cat that would report you for stealing.)
Luckily I've had a mostly bug-free experience with Dragon Age so far, and the ones I have experienced have been fairly minor. What I mostly hope is that they have a faster and more comprehensive patching cycle for DA2 - I know a lot of players have been frustrated that BioWare knows about the error they've experienced but haven't managed to do anything about it in four patches and nearly a year.
Again that reffers to my point about poor management on bioware's part
#32
Posté 09 septembre 2010 - 12:32
#33
Posté 09 septembre 2010 - 12:34
LucianTansey wrote...
Thats Bioware's fault, not ours, why should the gameplay for the gamer suffer as a result? If it wasnt for us there would be no Grey Wardens!
and if it wasnt for EA, Bioware wouldnt have the massive funding required to undertake such projects
we can't do anything about it. Just hope that the toolset for DA2 is advanced enough so that 3rd party modders can fix the bugs. That's what has been happening for DAO. I myself have worked on fixing crossbow, trap, resistance bugs
Modifié par Mecha Tengu, 09 septembre 2010 - 12:34 .
#34
Posté 09 septembre 2010 - 12:35
#35
Posté 09 septembre 2010 - 12:35
Dave of Canada wrote...
sided with the werewolves .
That would be an excellent bug, Werewolves were the best faction, heh.
#36
Posté 09 septembre 2010 - 12:35
Saibh wrote...
Pretty much. Some of the bugs are pretty sickening, and seem outright silly, as if they never even bothered to play. What, no one in your company bothered to not make Alistair king?
In DAO, no one in BioWare's QA department did any of these things: Played as a mage to Lothering (scaring one of the highwaymen off makes the associated quest impossible to complete), played as a dual-wielding rogue (dex bug on launch), or played the game for more than twenty minutes at a time.
In DAA, no one in BioWare's QA department did any of these things: played through to Velanna's companion quest, completed an easy Amaranthine quest before recruiting Sigrun, bothered to try to collect all the special magic armor in the Silverite Mines (Blackbiter leather?).
DAO had an extra, what, six months in order to 'bug test,' too, right? Whereas DAA came out a mere five months after DAO.
Awakening did seem quite rushed, and when games are rushed, quality suffers significantly. Given that DA2 is a full sequel and is coming out approximately a year and a half after the original, I think the absolute best we can hope for is that there will be no game stopping bugs.
#37
Posté 09 septembre 2010 - 12:36
Mecha Tengu wrote...
LucianTansey wrote...
Thats Bioware's fault, not ours, why should the gameplay for the gamer suffer as a result? If it wasnt for us there would be no Grey Wardens!
and if it wasnt for EA, Bioware wouldnt have the massive funding required to undertake such projects
we can't do anything about it. Just hope that the toolset for DA2 is advanced enough so that 3rd party modders can fix the bugs. That's what has been happening for DAO. I myself have worked on fixing crossbow, trap, resistance bugs
Thats all well and good for PC players, but I play on 360, and a gamer shouldnt have to rely on mods to fix the game himself, as a consumer, i have a right to assume the game at least has been playtested more than once.
#38
Posté 09 septembre 2010 - 12:36
Upsettingshorts wrote...
I'd take ambitious over bug free every day of the week and twice on Sunday as long as the patches come promptly.
So long as Bethesda isn't developing that ambitious game. Oblivion is my whipping boy for a long list of technical problems that will never go away. Can't even properly exit the game without a mod.
#39
Posté 09 septembre 2010 - 12:36
For instance, the line of code that causes the bug which resets attack speed to 1 if it reaches .5 or below, making the optimal use of Momentum and Haste together actually a detriment, is:
fSpeedEffects = 1.0f;
The fix to this bug is in bold below:
fSpeedEffects = 0.5f;
The bug that renders the entire Shattering Blows talent useless exists because the function call:
if (GetCreatureAppearanceFlag(oDefender, APR_RULES_FLAG_CONSTRUCT))
...never returns true, which it should when oDefender is of type APR_RULES_FLAG_CONSTRUCT. The code following that statement, only executing if it were to return true, is what applies the proper damage bonus against constructs. This is because GetCreatureAppearanceFlag calls the function GetM2DAInt, which I have come to learn looks up data in a 2DA file.
You see, APR_RULES_FLAG_CONSTRUCT is a constant hex value equal to 0x2. GetCreatureApperanceFlag uses GetM2DAInt to grab the 2DA data corresponding to "constructs" and checks it against the passed value, in this case APR_RULES_FLAG_CONSTRUCT.
Unfortunately, due to a mistake, the 2DA file attributes the hex value 0x1 to "constructs." Thus, 0x2 never equals 0x1, and you will never deal extra damage to a construct with this talent.
These are not delicate issues that require an inordinate amount of time to fix. These are typos that ruin entire characters.
I have not looked into dialog script errors, but I assume they are of similar fault.
Modifié par Maverick827, 09 septembre 2010 - 12:38 .
#40
Posté 09 septembre 2010 - 12:37
Seifz wrote...
Look, DA:O was by far the least buggy game that BioWare's released for the PC. Seriously. But, it did have some rather unforgivable bugs. For example, the dexterity bug. How was this giant, glaring bug not caught in testing? Those sorts of bugs did make the game feel a bit rushed. Still, overall, job well done on DA:O.
I don't recall either ME games have nearly so many bugs--for PC or console. I don't recall many of them having to do with direct story line, a la King Alistair or Morrigan's U BETRAYEEED MEEEEEEE!
Seriously, some of them are so basic. All they require is taking the other route. Play once with Anora as sole queen. No one did this?
#41
Posté 09 septembre 2010 - 12:38
#42
Posté 09 septembre 2010 - 12:40
jonluke93 wrote...
I have only had one gamebreaking bug and that was in Awakening when you are on the roofs in Amaranthine and there are enemies below. That sucked
I only avoided that because I was an archer and it let me kill from above. Getting stuck there would have REALLY upset me!
#43
Posté 09 septembre 2010 - 12:41
The community was able to fix many of the bugs for them.
Out of interest have Bioware fixed the Silverite mine bug yet? that was gamebreaking.
Modifié par Faz432, 09 septembre 2010 - 12:45 .
#44
Posté 09 septembre 2010 - 12:42
Dave of Canada wrote...
While there's a lot of bugs, I have a certain limitation to QA (due to how hard their job is, especially for long games like Origins) but... Witch Hunt's immersion breaking bug? HOW was that missed? It makes me worry that not all my choices will import correctly into DA2 and that my Warden who did everything great will actually be a flying cow that saved Flemeth, sided with the werewolves and such.
Indeed, I enjoyed Witch Hunt up until what I considered my most personal and important choice in Orgiins was completely contradicted, this was especially galling after playing Shadow Broker for ME2 which in terms of bugs on 360 was smoother than a certain androids bum.
#45
Posté 09 septembre 2010 - 12:43
Ya I could never hit anyone I spent a good 20 minutes trying to get Nathaniel to shoot the danm badguys but he wouldn't do it. I had to reload all the way back to when Oghren and Anders became Grey Wardens. And that was my first playthrough of Awakening so that definitely pissed me off.LucianTansey wrote...
jonluke93 wrote...
I have only had one gamebreaking bug and that was in Awakening when you are on the roofs in Amaranthine and there are enemies below. That sucked
I only avoided that because I was an archer and it let me kill from above. Getting stuck there would have REALLY upset me!
#46
Posté 09 septembre 2010 - 12:44
Saibh wrote...
Pretty much. Some of the bugs are pretty sickening, and seem outright silly, as if they never even bothered to play. What, no one in your company bothered to not make Alistair king?
To be fair, the "Decision Reset" bug is pretty easy to get around. Just don't import saves that are post post-epilogue. But also to be fairer, for a game that lets you play after the campaign, this is a huge bug.
#47
Posté 09 septembre 2010 - 12:44
jonluke93 wrote...
I have only had one gamebreaking bug and that was in Awakening when you are on the roofs in Amaranthine and there are enemies below. That sucked
you obviously never used ranged weapons or bothered to use traps
#48
Posté 09 septembre 2010 - 12:45
You know, I didn't get that bug everyone is talking about is this bug only on 360 because I played on PS3?Bobad wrote...
Dave of Canada wrote...
While there's a lot of bugs, I have a certain limitation to QA (due to how hard their job is, especially for long games like Origins) but... Witch Hunt's immersion breaking bug? HOW was that missed? It makes me worry that not all my choices will import correctly into DA2 and that my Warden who did everything great will actually be a flying cow that saved Flemeth, sided with the werewolves and such.
Indeed, I enjoyed Witch Hunt up until what I considered my most personal and important choice in Orgiins was completely contradicted, this was especially galling after playing Shadow Broker for ME2 which in terms of bugs on 360 was smoother than a certain androids bum.
#49
Posté 09 septembre 2010 - 12:47
Actually I did but ok.Mecha Tengu wrote...
jonluke93 wrote...
I have only had one gamebreaking bug and that was in Awakening when you are on the roofs in Amaranthine and there are enemies below. That sucked
you obviously never used ranged weapons or bothered to use traps
#50
Posté 09 septembre 2010 - 12:49





Retour en haut




