Most likely every problem we have found now are probably reported somewhere at some time by the QA, but for whatever reason weren't fixed in time.
That's not actually very likely. No one can find 100% of bugs. Two BW employees have indicated that they were not aware of an issue with the armour, for example.
Guest_Mortiel_*
That's not actually very likely. No one can find 100% of bugs. Two BW employees have indicated that they were not aware of an issue with the armour, for example.
Not every Bioware employee knows about every bug, either. So both you and Boatzu could be correct.
Not every Bioware employee knows about every bug, either. So both you and Boatzu could be correct.
I'm still pretty confident that it's not very likely (or even possible) that they could have found every bug.
To assume that all bugs will be found before a game ( especially as large as DAI ) ships is also quite naive, as that is never the case in any game, nor any software product.
That's not actually very likely. No one can find 100% of bugs. Two BW employees have indicated that they were not aware of an issue with the armour, for example.
Thats true about 100%, it was an exaggeration to say every bug. To an extent I meant it as a way to say most of the bugs we are finding now is probably documented by the QA somewhere. Especially big stuff like the key bug.
BWEAmelia is 100% correct. I have done work as a QA engineer and we find bugs that dont get fixed in the final product all the time. If it works the same way as it does in the companies I have worked at you submit bug reports based on a priority system. Showstopper bugs being the highest priority. If anyone is to blame for a game breaking bug(a showstopper) its the people that look over the list of bugs that are reported by QA and okays them as an acceptable amount of problems for an official final release. Most likely every problem we have found now are probably reported somewhere at some time by the QA, but for whatever reason weren't fixed in time.
As a Industrial Automation Engineer, I have not once delivered a system that contained a single bug. I spend those extra hours out of the office to iron them out personally at home if they are found during testing. A single bug in the industry could put dozens of lives in danger.
As a Industrial Automation Engineer, I have not once delivered a system that contained a single bug. I spend those extra hours out of the office to iron them out personally at home if they are found during testing. A single bug in the industry could put dozens of lives in danger.
I agree, and wish all companies worked this way. The company that I used to work for actually was in the news fairly recently for having more than a few problems. I will leave it up to speculation who it was though. Hint, I did testing on laptops.
Guest_Mortiel_*
I agree, and wish all companies worked this way. The company that I used to work for actually was in the news fairly recently for having more than a few problems. I will leave it up to speculation who it was though. Hint, I did testing on laptops.
You worked for CuisinArt? No way?!?!
I just hope BW Dev's that read this and lurk on the forums debating whether or not to share progressive info with the community, don't get put off by comments like CRCError's. While the most vocal are often the most frustrated, there's plenty of chill people enjoying your game.
I thought about that before posting truth be told.
It just aggravates me when dev's break silence to deliver lip service and excuses.
When they released Patch 2 it caused some graphical issues that were easily fixed with a command line work-around. They had that hotfix out pretty damn fast and I commend them for that.
Then this DLC came out with a game breaking bug damn near a month ago and they haven't fixed it yet. Yes I'm aware that there is a patch on the horizon... But game breaking bugs, bugs that should never have made it out of development, should be addressed quickly.
As a Industrial Automation Engineer, I have not once delivered a system that contained a single bug. I spend those extra hours out of the office to iron them out personally at home if they are found during testing. A single bug in the industry could put dozens of lives in danger.
While I applaud you spending your own personal time to ensure life-endangering bugs don't happen in your industry...
... I honestly think there's sort of a big difference between a bug that could potentially threaten lives and a bug that affects your ability to play a video game.
I understand people are frustrated, but I also think there's a little bit of a perspective issue happening as well.
It seems they werent aware of the key bug either, several devs didnt know about it. I recieved PMs for more details aswell.That's not actually very likely. No one can find 100% of bugs. Two BW employees have indicated that they were not aware of an issue with the armour, for example.
i think we all missed your presence here.
It seems they werent aware of the key bug either, several devs didnt know about it. I recieved PMs for more details aswell.
I just dont believe that QA picked this bug up. If it was a known shippable then i dont even have words to describe the person responsible for that decision.
This is the weirdest part to me. Most of us here have seen the key bug or dlc dogs flipping out in the walls since it happens so frequently. How does it slip past a QA team when it seems like a majority of the playerbase encountered the bug? The key bug happened before patch too, just less frequently and mostly just against red templars but I saw it at least a dozen times prepatch too. Just have to get a little happy on the firestorms with red templar assassins and its bound to happen..
i am so bumped playing Reaver at perilous it dosen't matter what armor i am wearing 1 hit from any one and i am dead ...
Either one of two things has taken place.This is the weirdest part to me. Most of us here have seen the key bug or dlc dogs flipping out in the walls since it happens so frequently. How does it slip past a QA team when it seems like a majority of the playerbase encountered the bug? The key bug happened before patch too, just less frequently and mostly just against red templars but I saw it at least a dozen times prepatch too. Just have to get a little happy on the firestorms with red templar assassins and its bound to happen..
Aside from it being shipped if QA did find them; No one then went to QA afterward to compile the most prominent bugs and glitches to know what needs addressing with the next patch. Possibly yet another team that is a bit lax on the job, I'd say.
War Cry with its passive upgrade has an undocumented effect in that its buff wears off slowly over the duration of the ability starting at 4 seconds in.
Can we make tool tip accuracy a priority? The community is more than happy to help sus out the bugs, but it makes it a little difficult when we don't even know how the abilities are supposed to behave.... Help us to help you?
While I applaud you spending your own personal time to ensure life-endangering bugs don't happen in your industry...
... I honestly think there's sort of a big difference between a bug that could potentially threaten lives and a bug that affects your ability to play a video game.
I understand people are frustrated, but I also think there's a little bit of a perspective issue happening as well.
Whilst there is an industry difference.. the fact that we can spend the time to iron out all bugs before handing over a finished product means that so can bioware.. if they spent half the time they spent playing twitch feed videos over the past year they could have found and fixed a whole lot of problems.. If they had players test the game and not just their staff for QA.. again.. a lot of problems could have been fixed.
Aside from it being shipped if QA did find them; No one then went to QA afterward to compile the most prominent bugs and glitches to know what needs addressing with the next patch. Possibly yet another team that is a bit lax on the job, I'd say.
If this was true then bioware might have a bigger problem. When two teams within the same company that are working on the same project don't communicate with each other, that's a sign of mismanagement . I seriously hope that's not the case because a company being mismanaged has a high chance of failure (well, unless you are Wall Street, then the rule does not apply).
Guest_Mortiel_*
You've just lost it... Doing Twitch streams has little to do with overall productivity. It takes like, what, three to five people to operate a stream. The entire rest of the team is still working on the game.Whilst there is an industry difference.. the fact that we can spend the time to iron out all bugs before handing over a finished product means that so can bioware.. if they spent half the time they spent playing twitch feed videos over the past year they could have found and fixed a whole lot of problems.. If they had players test the game and not just their staff for QA.. again.. a lot of problems could have been fixed.
-SNIP-
Your QA work is nothing like game dev QA. They already spend long nights combing for bugs. Often times, they find a good number of them. The time it takes to fix said bugs is another matter.
-SNIP-
If 5 engineers can automate an entire mine site in 1 year without a single bug.. Bioware with all their resources should be able to present a game without any bugs in 4. They probably forgot to close a bracket or left a semi-colon out somewhere.
They probably forgot to close a bracket or left a semi-colon out somewhere.
kek, obviously its one of the loop conditions on the check for more mobs to fix the key bug.
BioWare has one of the best QA departments in the industry. As I've mentioned many times previously - just because QA files an issue does not mean that issue will get fixed prior to ship, that's not a decision they make. To assume that because a game shipped with bugs is a failure of the QA department is to have a naive view of how game development works. T
You are joking, right? The amount of game breaking bugs in this game is simply way too high. I'm not talking about small things like specific abilities or items not working, but instead about constant crashes, freezes (black screen when joining a game), connection to session lost and so on. At least 8 of of 10 tries to find a game end up in session lost. When I'm able to finally join a lobby, at least 1/3 of my games freeze when joining or I become unable to move or without any abilities.
BTW, I have over 15 years of software development experience, so I KNOW how things work (or how they should)
You are joking, right? The amount of game breaking bugs in this game is simply way too high. I'm not talking about small things like specific abilities or items not working, but instead about constant crashes, freezes (black screen when joining a game), connection to session lost and so on. At least 8 of of 10 tries to find a game end up in session lost. When I'm able to finally join a lobby, at least 1/3 of my games freeze when joining or I become unable to move or without any abilities.
BTW, I have over 15 years of software development experience, so I KNOW how things work (or how they should)
But NASA did this one thing this one time so its k
Patch 3 notes: http://blog.bioware....-patch-3-notes/
Correct me if i'm wrong but is the (2H) armor bug not being mentioned here? And does that mean it is not being addressed and fixed?
Patch 3 notes: http://blog.bioware....-patch-3-notes/
Correct me if i'm wrong but is the (2H) armor bug not being mentioned here? And does that mean it is not being addressed and fixed?
I have to confess, I'm not surprised that it didn't make it into this patch (or, is very unlikely to, from what I read.)
They still weren't aware of it until about a week ago, and at that point, they had only successfully tested it enough to determine that there was a problem somewhere, and that they believed it was with the Adamant upgrade (I think that's the name of it.)
Unfortunately, it's smack dab in the lower-middle of one of the Reaver's trees, making it a pre-requisite of a lot of abilities. There is still the option of not taking it, to avoid the issue, but it's kind of a dubious option.
Retour en haut