5587 réponses à ce sujet

[denrios]

I just cannot believe the attitude of some of you folks. It will be out when it is done, believe me the bean counters are wringing their hands and whipping the developers over the missed dates. Sucks to be a developer at Bioware right now. Chin up guys I know how you feel!

[Thelios0]

From the info on the pc patch, the xbox already had the "patch" contents the pc received later...

[ShadoWxSnipa]

Bio-Boy 3000 wrote...

Still the same old us and them groups that are posting in this thread. Either you belong to the complaining faction or you align with the people that complain about the complainers faction. XD

im just watching and reading lol cuse its funny but im not saying im not mad/sad

[Fleb]

The level of anticipation within this thread is palpable. The phrase, it's done when it's done springs to mind

[masawolf]

oh grow up people. don't get your panties in a twist due to unforeseen circumstances stop act like a bunch of spoiled children that wants candy now and be patient and WAIT! I know I will wait on it.

[Ealdayen]

Note to self...check forums and not website

[Hrodberht]

Stanley Woo wrote...

Dragon Age1103 wrote...
So your long supportive fans really have to be treated like children when the bills are getting our of hand? We can't know the reason for the delay or is it just hard to find in all 170 pages! lol. Was it really b/c Bioware felt the DLC was too short? B/c $5=hour of gameplay would make me one happy gamer

I dunno, DragonAge1103. Based on the behaviour of many in this thread, treating our community like children would be easier, quicker, and less stressful to us. But we don't do that.

We like to treat our community like mature human beings capable of complex reasoning, civil discussion, and independent thought, no matter how they might appear otherwise when ranting and whinging and carrying on.

Chris Priestly has already given you some information, and some clarification. He has also mentioned there is no ETA on a release date or further information yet. The "reason for the delay" you keep harping on has already been given to you. No, it's nothing specific, but the specifics do not affect you. Whether it's bugs, scheduling, a mandate from higher up, a clumsy intern, my iced tea habit, or aliens, the product is still affected and we're dealing with it so that you can have the product you've been looking forward to.

Certain folks within the community believe that, unless we cater to your every whim and always do things you agree with, we are not being open and honest and that we are unprofessional, rude, or worse. If the community can disabuse itself of that belief, maybe we can have better and more informative discussions? And showing more patience than a child also helps if you don't want to be seen as one. I'm just saying, is all.

.



Look at the beginning of this paragraph-

Chris Priestly has already given you some information, and some clarification.  He has also mentioned there is no ETA on a release date or further information yet. The "reason for the delay" you keep harping on has already been given to you

Now look at the rest of the paragraph-

No, it's nothing specific, but the specifics do not affect you. Whether it's bugs, scheduling, a mandate from higher up, a clumsy intern, my iced tea habit, or aliens, the product is still affected and we're dealing with it so that you can have the product you've been looking forward to.

Um, you're contradicting yourself a bit.  First you say Chris has given us "clarification", and that the reason for the delay has been given to us.  You then clearly demonstrate that neither of those things is true.

[jennamarae]

Stanley Woo wrote...

And I'd like to address a comment to whoever said all the testing should hae been done by now, so how could it be a bug that's caused this? It's actually pretty easy for a bug to cause something like this. Even if testing for a game is "done," there is still a lot of time between "done" and when the game appears on store shelves. While waiting for things like certification, approval and manufacturing, testing can still continue. So, time-wise, testing can happen even when the game is "done." This is how you get things like zero-day patches.

Now see? That is a an actual answer to a question that I asked, and possibly others did as well. Thank you.

[Thelios0]

Fleb wrote...

The level of anticipation within this thread is palpable. The phrase, it's done when it's done springs to mind

The wait on the Team Gizka KOTOR 2 cut content patch comes to mind....

[PrinceOfFallout13]

masawolf wrote...

oh grow up people. don't get your panties in a twist due to unforeseen circumstances stop act like a bunch of spoiled children that wants candy now and be patient and WAIT! I know I will wait on it.

2 months 2 MONTHS! of false promises so dont you dare say have patience

anyway does anyone know if duncan items are only the swords or will the armor be in aswell?

[Jayphil]

not a bug then.... so you're just teasing us... ah bioware you are such a tease

[sparkyclarky24]

I dont mind waiting really. Look at it from their viewpoint. We're lucky it's even coming out.

[Svensonreloaded]

the game is for people they are 18 years or older pls , the people they under this age , leave the page yet xD

[Darth_Trethon]

You know Stanley I think that your explanations will simply fall on deaf ears. Why? This is a side effect of your successful hype machine. It's what makes your games sell and successful and all that but when you fail to deliver there is this.....180 pages of rage and more to come all in one day.

[steelerfan75]

i bet they cancel it and roll it into the expansion that is suppose to be out in march

[Skydiver8888]

Stanley Woo wrote...

Abriael_CG wrote...
While I will never discount the amount of rudeness i'm by now used to see every time there's a delay in the gaming market, If I may, I would say that, while no set in stone ETA is understandable, letting us know if the delay is a matter of hours, days, weeks or months would definitely help make many feel better.
I hope you understand that "there's a delay, there's no ETA, sorry" leaves people a tad wanting

Since the breaking of a promised date is what got people so up in arms in the first place, do you think that giving them a timeframe is really going to help?

And I'd like to address a comment to whoever said all the testing should hae been done by now, so how could it be a bug that's caused this? It's actually pretty easy for a bug to cause something like this. Even if testing for a game is "done," there is still a lot of time between "done" and when the game appears on store shelves. While waiting for things like certification, approval and manufacturing, testing can still continue. So, time-wise, testing can happen even when the game is "done." This is how you get things like zero-day patches.

Another concept that people have problems grasping is that software, complex as it is, can almost never be completely, 100% bug-free. That's just unreasonable if you have a product that needs to get released. During the later stages of a project, the managers "triage" the bugs. They make the hard decisions on what bugs can be fixed in the time and with the people available, and which bugs are minor enough to leave in. As the project deadline looms closer, these decisions get harder and harder to make and the bugs that are allowed through are, comparitively, bigger. Really serious stuff like crashes or causing your computer to explode in green Jell-O are given priority, but other things can get through. This is how you get things like software patches days, weeks, months, even years after release.

Finally, there's the "infinte monkeys" factor. Even working at full capacity 24 hours a day, there's only so many things that can be found by the dozen or so QA that projects get. They might have filed a million bugs each during the project, and all of them might have been approved by triage, and they might not have found anything else between "done" and store shelves, but statistically, you can throw a few more people at the game and they will see something that was missed. Add in a few hundred thousand folks with a few hundred thousands different Pc configurations or play styles, and you have that many more "testers." No one likes it, but that's how you get folks complaining about "paying to be a tester." No malice involved or intended, it's just the math.

Not saying a bug did cause any of this. I just thought I'd address that particular question since I knew the answer, and it's a little distraction for all y'all.

Thank you, Stan Woo! (hands you a pineapple)

As a former paid game tester/QA puke myself, these threads full of armchair developers really burn my britches.  It's really tough not to snark all over everyone (sometimes I give in) because I know more than they do about the process.  Hopefully people read your calm and reasoned post and take it down a notch. 

[fanman72]

Stanley Woo wrote...

Abriael_CG wrote...
While I will never discount the amount of rudeness i'm by now used to see every time there's a delay in the gaming market, If I may, I would say that, while no set in stone ETA is understandable, letting us know if the delay is a matter of hours, days, weeks or months would definitely help make many feel better.
I hope you understand that "there's a delay, there's no ETA, sorry" leaves people a tad wanting

Since the breaking of a promised date is what got people so up in arms in the first place, do you think that giving them a timeframe is really going to help?

And I'd like to address a comment to whoever said all the testing should hae been done by now, so how could it be a bug that's caused this? It's actually pretty easy for a bug to cause something like this. Even if testing for a game is "done," there is still a lot of time between "done" and when the game appears on store shelves. While waiting for things like certification, approval and manufacturing, testing can still continue. So, time-wise, testing can happen even when the game is "done." This is how you get things like zero-day patches.

Another concept that people have problems grasping is that software, complex as it is, can almost never be completely, 100% bug-free. That's just unreasonable if you have a product that needs to get released. During the later stages of a project, the managers "triage" the bugs. They make the hard decisions on what bugs can be fixed in the time and with the people available, and which bugs are minor enough to leave in. As the project deadline looms closer, these decisions get harder and harder to make and the bugs that are allowed through are, comparitively, bigger. Really serious stuff like crashes or causing your computer to explode in green Jell-O are given priority, but other things can get through. This is how you get things like software patches days, weeks, months, even years after release.

Finally, there's the "infinte monkeys" factor. Even working at full capacity 24 hours a day, there's only so many things that can be found by the dozen or so QA that projects get. They might have filed a million bugs each during the project, and all of them might have been approved by triage, and they might not have found anything else between "done" and store shelves, but statistically, you can throw a few more people at the game and they will see something that was missed. Add in a few hundred thousand folks with a few hundred thousands different Pc configurations or play styles, and you have that many more "testers." No one likes it, but that's how you get folks complaining about "paying to be a tester." No malice involved or intended, it's just the math.

Not saying a bug did cause any of this. I just thought I'd address that particular question since I knew the answer, and it's a little distraction for all y'all.

I don't think people understand this.  From my experience, whether working in a programming or engineering role many managers and customers involved won't understand and simply don't care about the technical nuances.  They just want it "done" and from the customer perspective a cheap price regardless of the effort put into it in the first place.  It's a pain in the ass frankly, and one of the reasons I got out of a customer oriented technical role.  


That being said please please get RtO as soon as possible :happy:.  Take it as a compliment.  If it were a **** game to begin with I wouldn't care and probably wouldn't even buy an expansion, but its not

Modifié par fanman72, 06 janvier 2010 - 12:42 .

[AndreaRhaegar]

Well...what can i say, i was waiting for RTO so bad. I know so many things can go awry in software developing, it's just a little bit weird that this problem came out just the day the DLC was scheduled to be released.

I will wait and pray, hoping to get it as soon as possible. Few days, the better.



May the Maker and Andraste his bride be with us.

[xLyTwiZiDxLy]

Does anyone think it will be possible it would come out tommrow

[jennamarae]

steelerfan75 wrote...

i bet they cancel it and roll it into the expansion that is suppose to be out in march

I doubt that will be out before September quite honestly.

[Lumilulumi]

I would rather them delay it, then release it with a major problem and then wait on a patch to fix it, as the patch would have to go through the X-box and Sony process before it gets out to us.

[Gorthaur the Cruel]

steelerfan75 wrote...

i bet they cancel it and roll it into the expansion that is suppose to be out in march

Yeah totally that sounds logical (sarcasm).

[sparkyclarky24]

i know people are pretty pissed but come on.



You can live.

whatever it is that caused it (personally i think it's an internal **** up, not a bug) has happened, and theres nothing I or you can do, and moaning wont help.

It's only a game guys (to people who are like...over-reacting)

[DemonGrave]

I found this thread way too late. I had just bought the points for it and was looking for it in the game and it wasn't there. Then I found this thread after an hour of searching for why it wouldn't show up lol. (sigh)......... I hate my life now

[ShadoWxSnipa]

Skydiver8888 wrote...

Stanley Woo wrote...

Abriael_CG wrote...
While I will never discount the amount of rudeness i'm by now used to see every time there's a delay in the gaming market, If I may, I would say that, while no set in stone ETA is understandable, letting us know if the delay is a matter of hours, days, weeks or months would definitely help make many feel better.
I hope you understand that "there's a delay, there's no ETA, sorry" leaves people a tad wanting

Since the breaking of a promised date is what got people so up in arms in the first place, do you think that giving them a timeframe is really going to help?

And I'd like to address a comment to whoever said all the testing should hae been done by now, so how could it be a bug that's caused this? It's actually pretty easy for a bug to cause something like this. Even if testing for a game is "done," there is still a lot of time between "done" and when the game appears on store shelves. While waiting for things like certification, approval and manufacturing, testing can still continue. So, time-wise, testing can happen even when the game is "done." This is how you get things like zero-day patches.

Another concept that people have problems grasping is that software, complex as it is, can almost never be completely, 100% bug-free. That's just unreasonable if you have a product that needs to get released. During the later stages of a project, the managers "triage" the bugs. They make the hard decisions on what bugs can be fixed in the time and with the people available, and which bugs are minor enough to leave in. As the project deadline looms closer, these decisions get harder and harder to make and the bugs that are allowed through are, comparitively, bigger. Really serious stuff like crashes or causing your computer to explode in green Jell-O are given priority, but other things can get through. This is how you get things like software patches days, weeks, months, even years after release.

Finally, there's the "infinte monkeys" factor. Even working at full capacity 24 hours a day, there's only so many things that can be found by the dozen or so QA that projects get. They might have filed a million bugs each during the project, and all of them might have been approved by triage, and they might not have found anything else between "done" and store shelves, but statistically, you can throw a few more people at the game and they will see something that was missed. Add in a few hundred thousand folks with a few hundred thousands different Pc configurations or play styles, and you have that many more "testers." No one likes it, but that's how you get folks complaining about "paying to be a tester." No malice involved or intended, it's just the math.

Not saying a bug did cause any of this. I just thought I'd address that particular question since I knew the answer, and it's a little distraction for all y'all.

Thank you, Stan Woo! (hands you a pineapple)

As a former paid game tester/QA puke myself, these threads full of armchair developers really burn my britches.  It's really tough not to snark all over everyone (sometimes I give in) because I know more than they do about the process.  Hopefully people read your calm and reasoned post and take it down a notch. 

You sound like u didnt even know what a computer was Burn ure britches lol thats hilaroius from like 30 years ago