148 réponses à ce sujet

[Nova Rayne]

I just checked the Call to arms upgrade on war cry on the Legionnaire, and it seems like I only get the 200% armor bonus from the rear. No video to post (PS4 Scrub) But I was taking 30ish from the front, 60ish form the rear. Warcry> 30ish from the front, 1 from the rear. Tested on a vint archer.

[HeroicMass]

Someone said the shield classes are bugged too but it looks like its just the reaver and katari. Still, 2/12 is 2 classes too many.

 

Templar and Lego tested fine for me.  Only Reaver and Katari after I had the chance to go through all of the classes.  Good to have this out there as I love the 2H classes and look forward to this correction being in place.

 

I wonder how much change in opinion will happen on the Katari once this is implemented.

[Ben Gadura]

It surprises me that no one mentioned this thread:

http://forum.bioware...rk-compilation/

People found out that armor buffs only increase rear armor.

[J. Peterman]

ok so bioware employe are insecure in them self so they think everyone is against them and hand out warning for for that, well done

if I was hostile I would not use word, I am a physical person and if I was to turn hostile it would be easier for me to jump on a plane and talk to them one on one.

and not to mention I take pills now so I cant be agressive

 

Okay........

[VilniusNastavnik]

Unfortunately, I am not sure if I can see an issue here. You appear to be taking more damage when being hit from the flank, which would not support the current big with the Katari and Reaver.

 

I did have a thought, however: The Templar and Legionnaire may appear affected to a less degree because of the shield artificially inflating to the front defense somehow, but but still be bugged. I can't really tell.

 

As Penguins said, Wraiths ignore armour by design.

Yeah, routine is fine for Lego, I was thinking more about threatening.. damage jumps from 1 to 35 and upwards with some enemies doing 150+ damage on threatening.. just does not seem right.

I play threatening as my primary difficulty with mates.. never noticed that it was anywhere near this damaging until I did a damage test run. 

[Trickshaw]

After seeing Penguin's video I logged my Hunter just to check and noticed that the damage for both flank/rear and front are identical so something's not right. So front has the same multiplier as rear or vice versa. Given how much damage Hunters take ANYWAY I'm prone to lean towards front having the same multiplier as rear.

[HeroicMass]

After seeing Penguin's video I logged my Hunter just to check and noticed that the damage for both flank/rear and front are identical so something's not right. So front has the same multiplier as rear or vice versa. Given how much damage Hunters take ANYWAY I'm prone to lean towards front having the same multiplier as rear.

 

I tested the hunter and it came out fine for me.  After testing all classes, only the 2H characters were impacted.

[Trickshaw]

I tested the hunter and it came out fine for me. After testing all classes, only the 2H characters were impacted.

So you're saying you had less damage from front and more damage from rear? If so, do you recall what armor you were wearing?

[HeroicMass]

So you're saying you had less damage from front and more damage from rear? If so, do you recall what armor you were wearing?

I did. I used one of each tier for the tests. Cant remember which color though I doubt it woukd matter

[HeroicMass]

Back on topic:



So the Hunter is clear... I am unable to log in at this time, but maybe we should compile similar tests with all classes to be safe?

I tested them all. Only issues I noticed were reaver and katari.

[HeroicMass]

The only thought I had on it: Is there any way that the Templar and Legionnaire could still have the bug but somehow be skewed because of the added armour from the shield?

The variance in damage from front to rear was in line with other classes. It was just lower

[BWEAmelia]

Update:

 

As mentioned in this thread : www.reddit.com/r/DragonAgeCoOp/comments/2p7rv2/armor_turn_the_bolt_tests/ 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. That is intended, but since the string does not contain that information it can be confusing.

 

I stole Penguin's Reaver for my own to test locally and found that the reason his Reaver was taking more damage from the front than the rear is because the passive ability "Adamant" may have an issue with the bonus that it grants. There are a number of other abilities that could exhibit this behavior ( including War Cry ) and we have a designer taking a look right now to confirm suspicions / fix the issue.

 

Be Excellent to Eachother.

 

Thanks,

Amelia

[BWEAmelia]

I thinl the anger comes from the fact that we as the community seem to be reporting bugs that really should have been picked up by qa. When the armor bug was reported, it obviously wasnt tested properly because we can now see that at least 4 classes out of 12 are infact bugged. If i had not had posted this test, the case would still be closed.

Im neutral in all of this and id just like the game fixed, which is why i post videos, but i do find myself asking if i should be testing potential bugs for bioware when im not on their payroll.

Its all very frustrating and im not surprised some users are lashing out at the devs, because for Amelia to come out and say that they have one of the best QA in the business is just a bit of a slap in the face given lots of bugs that really should have been detected (such as this one) just havent. Ive had evenings where i cant complete a single game because the game is such a mess. Crashes, disconnects and key bugs happen a lot more than what is acceptable in my opinion.

That said, comparing bioware to hitler is ridiculous.

 

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. 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. In fact most mechanical products usually ship with "bugs" ( the auto industry recalls are a good example ). Every software product you use, down to your operating system ships with outstanding bugs that the development companies are aware of, and a whole lot that they are unaware of ( think Microsoft 0-day exploits ). If you have a fancy toaster, it probably shipped with a known issue.

 

I'll share quickly an anecdote one of my professors who previously worked in the auto industry shared with us when I was in college: While working on the software that runs in vehicle's entertainment systems a bug was found where the feature of the device that attenuated ( made the radio quieter / louder ) the radio based on road speed ( radio gets louder as you go faster to overcome road noise, quieter as you slow ) would make the radios on this new model of vehicle quieter, but never again raise the volume, essentially muting and bricking the entertainment system in the car. Since the vehicle was already on the assembly line they issued an order to the assembly line workers to snip the wire that ran from the radio to the road speed sensor on the vehicle, essentially disabling the feature with a pair of wire snips.

 

Another fun example is perhaps the Mars Climate Orbiter that crashed because of a software bug ( not using SI units ) http://en.wikipedia....Climate_Orbiter. The cost of the lander alone is $327 Million dollars. So it seems even NASA's QA ( whom are some of the best in the world ) lets a couple through now and then.

 

Anyway, some hearty food for thought. My intent is not to derail the thread to discuss the history of Software QA, but to merely offer some more information in the hopes of greater understanding. I know that you're unhappy with certain things in the game, but becoming hateful and unruly is truly the worst path to getting any traction, and will only result in spinning yourself up. Getting angry, as I've mentioned many times before, will have no effect on the speed that we can patch the game. It may, however, reduce the amount of community issues that are brought up when we consider priority issues if our devs are pushed away from our forums because of a lack of value and an abundance of static.

 

Be Excellent to Eachother.

 

Thanks,

Amelia

[KalGerion_Beast]

Thanks for the update!  If the lack of armor is related to Adamant then thats good news to me.  Armor buffs (relatively) for all warriors coming soon.  

[Saboteur-6]

 

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. 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. In fact most mechanical products usually ship with "bugs" ( the auto industry recalls are a good example ). Every software product you use, down to your operating system ships with outstanding bugs that the development companies are aware of, and a whole lot that they are unaware of ( think Microsoft 0-day exploits ). If you have a fancy toaster, it probably shipped with a known issue.

 

I'll share quickly an anecdote one of my professors who previously worked in the auto industry shared with us when I was in college: While working on the software that runs in vehicle's entertainment systems a bug was found where the feature of the device that attenuated ( made the radio quieter / louder ) the radio based on road speed ( radio gets louder as you go faster to overcome road noise, quieter as you slow ) would make the radios on this new model of vehicle quieter, but never again raise the volume, essentially muting and bricking the entertainment system in the car. Since the vehicle was already on the assembly line they issued an order to the assembly line workers to snip the wire that ran from the radio to the road speed sensor on the vehicle, essentially disabling the feature with a pair of wire snips.

 

Another fun example is perhaps the Mars Climate Orbiter that crashed because of a software bug ( not using SI units ) http://en.wikipedia....Climate_Orbiter. The cost of the lander alone is $327 Million dollars. So it seems even NASA's QA ( whom are some of the best in the world ) lets a couple through now and then.

 

Anyway, some hearty food for thought. My intent is not to derail the thread to discuss the history of Software QA, but to merely offer some more information in the hopes of greater understanding. I know that you're unhappy with certain things in the game, but becoming hateful and unruly is truly the worst path to getting any traction, and will only result in spinning yourself up. Getting angry, as I've mentioned many times before, will have no effect on the speed that we can patch the game. It may, however, reduce the amount of community issues that are brought up when we consider priority issues if our devs are pushed away from our forums because of a lack of value and an abundance of static.

 

Be Excellent to Eachother.

 

Thanks,

Amelia

 

 

Excellent points Amelia, thank you for keeping us informed.

[CRCError1970]

 

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.

So the QA department MAYBE found the bugs and documented them... Then some other department said "**** QA! Ship it anyway." Gotcha.

Also, using other companies failures as defense is a copout. If I did something wrong at work and I pulled the "Well, NASA screwed the pooch on math once, so I should get a pass.", I'd likely get in deeper hot water for using a lame defense. Other peoples failure are not a free pass for your own.

I'm not a professional software QA guy by any long shot, but through NORMAL play it was obvious the Destruction DLC was broken within an hour of downloading it. I don't know what kind of test platforms you guys are using, but if what I see on the forums is any indication, you guys are straight up LYING if you say you haven't seen these issues by now. It happens to any given player multiple times a day from what I've seen and heard from others.

Now I know you can't publicly admit failure because shareholders. But all we are asking is that you fix the crap and take QA more seriously over shareholders. If we don't purchase your next product, there aren't going to be shareholders to pay lip service to.

[Stinja]

As mentioned in this thread : www.reddit.com/r/DragonAgeCoOp/comments/2p7rv2/armor_turn_the_bolt_tests/ 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. That is intended, but since the string does not contain that information it can be confusing.

 

Will the comments for abilities be updated in-game to better reflect the actual effects then?

 

If you're worried too much information may overwhelm some people, you could enable an option like Diablo 3 which has basic information by default, and a user selectable option for "advanced" information with things like numbers and details of effects.

 

I do not go to this Reddit thing, so it's good to have information posted on the Bioware official forums, where one would normally expect all information of Bioware games to be disseminated.  Cheers.

[Shadohz]

[snip]

I like this one. She has spunk. I made the other ones cry. 

 

Spoiler

 

inb4badanalogyhelost

[Saboteur-6]

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.

[HeroicMass]

Just did a few tests on the reaver after promoting without adamant and the damage values were correct. Havent tested katari because of time and being at lvl 9

Thanks Amelia

[Boatzu]

 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.