1600 réponses à ce sujet

[Dahelia]

goofyfoot3184 wrote...

ok lets get this strait bioware can not release dlc on time or even give a actual release date and they have the nerve to announce a official expansion in march. one thing at a time children. when will return to ostagar be avalibale and what was the issue? will there be any repercussions for employees involved with this not being released on the 5. and what percentage of a chance is there that the expansion will be released withing 2 months of your so called release for it in march?

Oo! Let us talk about this! Maybe the wish to multitask? Who knows, it might not even be released in March really, it isn't close to March yet...close but not close enough, we will have to wait.

[What a Twist]

goofyfoot3184 wrote...

ok lets get this strait bioware can not release dlc on time or even give a actual release date and they have the nerve to announce a official expansion in march. one thing at a time children. when will return to ostagar be avalibale and what was the issue? will there be any repercussions for employees involved with this not being released on the 5. and what percentage of a chance is there that the expansion will be released withing 2 months of your so called release for it in march?

Well the expansion had a video, and from the looks of it a lot of the heavy lifting is complete.

I doubt there will be a delay.

[Dahelia]

Eurypterid wrote...

Dahelia wrote...

Alright...back on topic. If it really comes out a month later....I'm gonna be mad..I wish to know what this delay was and why it has caused such a huge problem....please.

My instinct is that once they figure out exactly what caused the issue and are closing in on a fix (or have it fixed), they'll give us more info.

Maybe, they might not....

[What a Twist]

Eurypterid wrote...

Dahelia wrote...

Alright...back on topic. If it really comes out a month later....I'm gonna be mad..I wish to know what this delay was and why it has caused such a huge problem....please.

My instinct is that once they figure out exactly what caused the issue and are closing in on a fix (or have it fixed), they'll give us more info.

You tease

[EricXIII]

Eurypterid wrote...

Dahelia wrote...

Alright...back on topic. If it really comes out a month later....I'm gonna be mad..I wish to know what this delay was and why it has caused such a huge problem....please.

My instinct is that once they figure out exactly what caused the issue and are closing in on a fix (or have it fixed), they'll give us more info.

still as i said before a small update on the matter wouldnt hurt

[Mechnic]

Twist wrote "there was a bug. end of the line". NO there is not a "was" there is an "is" and it is not a "BUG" it is an "ISSUE". So ur alphabet soup is not working very good.

[Eurypterid]

goofyfoot3184 wrote...

ok lets get this strait bioware can not release dlc on time or even give a actual release date and they have the nerve to announce a official expansion in march. one thing at a time children. when will return to ostagar be avalibale and what was the issue? will there be any repercussions for employees involved with this not being released on the 5. and what percentage of a chance is there that the expansion will be released withing 2 months of your so called release for it in march?

Separate teams for DLC and expansions. The problems with one do not imply there will be problems with the other. And I highly doubt you'll ever get a response to whether or not there were repercussions for employess involved with this.

[bzombo]

goofyfoot3184 wrote...

ok lets get this strait bioware can not release dlc on time or even give a actual release date and they have the nerve to announce a official expansion in march. one thing at a time children. when will return to ostagar be avalibale and what was the issue? will there be any repercussions for employees involved with this not being released on the 5. and what percentage of a chance is there that the expansion will be released withing 2 months of your so called release for it in march?

why do you want people fired? and with us not knowing the specific problem, who are we to think anyone should be fired? obviously, i don't know, but i think that once everything is straightened out someone will tell us what went wrong. bioware has been good that way. due to the previous dates not working i think they're hesitant to give us a new date. let's also think of this: chris said he'd tell us when there's new info. with that in mind, do we really want him popping on every hour to say, "nothing new yet." wouldn't that get old and repetitive? let's just wait for there to be something new to tell us. plus, if they're on here, they're not working on fixing the problem.

[Wozearly]

Bioware Release Team: "So, guys - Return to Ostagar's all ready to ship, right? I mean, you have fixed all the issues that came up in the November and December testing, right?"

QA Test Lead: "Well...we thought we had. But when we ran the final version through we found we still had one or two issues that mean lots of users would have game-breaking bugs, or be unable to play RTO at all."

Release Team: "What? So what are we going to do now?"

QA Lead: "Well, I'd suggest we delay the release and give us time to fix these bugs before shipping."

Release Team: "But the community's already angry we missed the first date. There'll be a huge backlash if we do that."

Chris Priestly (for it is he!): "Yes, but remember how they felt about the bugs in the main release? If we ship content we know is flawed, they'll be all over us and the support team before you can say '...the cake is a lie'."

Release Team: "So we have a choice between delaying to fix the content and get things right, which will ****** off the players...or releasing something we know has big problems in it, which will ****** off the players."

QA Lead: "That's about it, yeah."

Release Team: (sighs) "Well, its probably better we sort things out now than tie ourselves in knots and have to delay Awakening because we've been run ragged dealing with shouting people at EA Support because of RTO. Okay, we'll delay the release. Chris, can you go and tell the community about this?"

Chris Priestly: "Oh, ****. Okay, here we go. Posting...sent"

Bioware Community: "RTO delayed? RAWRRRR!!!" (cue sound of fifty people screaming abuse at Chris in an epic attack of shooting the messenger)


Okay, so the above probably didn't happen quite like that in reality...but seriously guys, as someone who has spent the vast majority of his posting time on here helping to find solutions for people who can't even install the game, I'd really rather Bioware were happy with the release - even if that involves a delay and an unfortunate last-minute announcement because they'd hoped to fix things in time to keep the 5th Jan as a release date.

Modifié par Wozearly, 06 janvier 2010 - 09:07 .

[jsachun]

Kakashi92 wrote...

DocSun wrote...

You know... I gotta stick up for Chris and the rest of the Bioware team. They have delivered us a good and enjoyable product with DA:O. And they are working on fixing the bugs we do have with it.

About RtO: Yes it sucks to be delayed but come on people... 1) They did tell us whats up. Somthing is wrong with it and they want to make it better so that we can enjoy it to the fullest. Now while thats not a technical answer like "its a bug with code line x" but we should not need that. They are on our side guys, they want us to enjoy it and so they are trying to make it possible.
2) They only refuse to give an ETA because you all ****ed and moaned the last two times when it was given and not held up, now you **** cus they dont give you one. Its hard for them because in essence they can't win with your logic.

In the end. It will be out, when its out, and it shall be good. Until then go back to your normal lives. We all have normal lives right?

Well Said

Actually that's not true at all. As far as Bioware was concerned, the release date was to be determined by Certifying Parties of the relative platforms and had nothing to do with Quality Assurance. As far as they were concerned It was all tested at their end and ready to go. Why do I smell backdoor business deal between the developer & one or some of the platform parties, so that it can all be released at the same time (Help I'm trying to sell my consoles??!!??!!).

[Cavegeta]

Dahelia wrote...

Alright...back on topic. If it really comes out a month later....I'm gonna be mad..I wish to know what this delay was and why it has caused such a huge problem....please.

Me too.  Not mad so much, as that if it does come out a month later that puts it in conflict with ME2 and other stuff thats already coming out this month and next.  I imagine Bioware's probably maddest of all that the Holiday Season window wasn't met at the end of the season.

[What a Twist]

Mechnic wrote...

Twist wrote "there was a bug. end of the line". NO there is not a "was" there is an "is" and it is not a "BUG" it is an "ISSUE". So ur alphabet soup is not working very good.

It was confimed that a bug was the cause. And we don't know if the bug is still there or not, I assume they've fixed it since they have had all day.

The bug being there still or not doesn't matter. The DLC is not out yet, and im a sad panda.

[bzombo]

Dahelia wrote...

goofyfoot3184 wrote...

ok lets get this strait bioware can not release dlc on time or even give a actual release date and they have the nerve to announce a official expansion in march. one thing at a time children. when will return to ostagar be avalibale and what was the issue? will there be any repercussions for employees involved with this not being released on the 5. and what percentage of a chance is there that the expansion will be released withing 2 months of your so called release for it in march?

Oo! Let us talk about this! Maybe the wish to multitask? Who knows, it might not even be released in March really, it isn't close to March yet...close but not close enough, we will have to wait.

the devs have said there is a separate dlc team. my guess is the dao devs are working on the expansion and the dlc team is working on rto.

[EricXIII]

What a Twist wrote...

Mechnic wrote...

Twist wrote "there was a bug. end of the line". NO there is not a "was" there is an "is" and it is not a "BUG" it is an "ISSUE". So ur alphabet soup is not working very good.

It was confimed that a bug was the cause. And we don't know if the bug is still there or not, I assume they've fixed it since they have had all day.

The bug being there still or not doesn't matter. The DLC is not out yet, and im a sad panda.

confirmed from who?give me a link of a bioware stuff that saying that the dlc has been delayed because of a bug

[Broken1477]

What a Twist wrote...

Dahelia wrote...

What a Twist wrote...

..They would be an interesting couple.

You have not heard the half of the excuses of delaying I have heard...have not lol....

Our cat is on fire?

That's not funny.  I happen to have a pretty stupid cat who thinks candles are his friends.  I have had to extiguish him before.  Mental retardation in cats is a serious problem.

[Dahelia]

bzombo wrote...

Dahelia wrote...

goofyfoot3184 wrote...

ok lets get this strait bioware can not release dlc on time or even give a actual release date and they have the nerve to announce a official expansion in march. one thing at a time children. when will return to ostagar be avalibale and what was the issue? will there be any repercussions for employees involved with this not being released on the 5. and what percentage of a chance is there that the expansion will be released withing 2 months of your so called release for it in march?

Oo! Let us talk about this! Maybe the wish to multitask? Who knows, it might not even be released in March really, it isn't close to March yet...close but not close enough, we will have to wait.

the devs have said there is a separate dlc team. my guess is the dao devs are working on the expansion and the dlc team is working on rto.

Maybe both teams should come together for a few things, maybe it will get things done faster...but two teams get things done quicker. I don't know...

[Deiser]

Sephris_Lor wrote...

Dahelia,

It was posted by Chris Priestly on his personal page, (click in his name below, or just go to the first page of this thread to see what he said). .

What info are you talking about? The only thing he posted is that he's the bearer of good and bad news. He never made an announcement today.

Modifié par Deiser, 06 janvier 2010 - 09:11 .

[Gorthaur the Cruel]

EricXIII wrote...

What a Twist wrote...

Mechnic wrote...

Twist wrote "there was a bug. end of the line". NO there is not a "was" there is an "is" and it is not a "BUG" it is an "ISSUE". So ur alphabet soup is not working very good.

It was confimed that a bug was the cause. And we don't know if the bug is still there or not, I assume they've fixed it since they have had all day.

The bug being there still or not doesn't matter. The DLC is not out yet, and im a sad panda.

confirmed from who?give me a link of a bioware stuff that saying that the dlc has been delayed because of a bug

What else could it really be besides a bug?

[darkshadow136]

EricXIII wrote...



confirmed from who?give me a link of a bioware stuff that saying that the dlc has been delayed because of a bug

The closest thing to admitting there is a bug is in this thread. social.bioware.com/forum/1/topic/9/index/541856&lf=8

[What a Twist]

EricXIII wrote...

What a Twist wrote...

Mechnic wrote...

Twist wrote "there was a bug. end of the line". NO there is not a "was" there is an "is" and it is not a "BUG" it is an "ISSUE". So ur alphabet soup is not working very good.

It was confimed that a bug was the cause. And we don't know if the bug is still there or not, I assume they've fixed it since they have had all day.

The bug being there still or not doesn't matter. The DLC is not out yet, and im a sad panda.

confirmed from who?give me a link of a bioware stuff that saying that the dlc has been delayed because of a bug

Eury indorectly confimed it, I forget what thread it was in. He/she was replying to a post about this being a "bug" and eury said "While that may be the case, they haven't actually stated it is a bug"

[Deiser]

Solostran85 wrote...

What else could it really be besides a bug?

As others have pointed out, it could very well be multiconsole politics, certification issues.... pretty much anything really.

[EricXIII]

What a Twist wrote...

EricXIII wrote...

What a Twist wrote...

Mechnic wrote...

Twist wrote "there was a bug. end of the line". NO there is not a "was" there is an "is" and it is not a "BUG" it is an "ISSUE". So ur alphabet soup is not working very good.

It was confimed that a bug was the cause. And we don't know if the bug is still there or not, I assume they've fixed it since they have had all day.

The bug being there still or not doesn't matter. The DLC is not out yet, and im a sad panda.

confirmed from who?give me a link of a bioware stuff that saying that the dlc has been delayed because of a bug

Eury indorectly confimed it, I forget what thread it was in. He/she was replying to a post about this being a "bug" and eury said "While that may be the case, they haven't actually stated it is a bug"

even if this is true eury cant know anything about the delay that we dont she is a forum moderator not a bioware employee

[Jimmy Fury]

I suspect that the expansion will actually be ready to go in Feb. but they put the March date on it to ensure they don't run into the same problems they've had with RtO.



As for how the bug could only show up at the last minute... When I was playing Warden's Keep for the first time, I ran into a craaaaazy glitch that teleported me out of a certain major battle and back into the middle of the conversation with a certain dead person. Once I got out of the Convo I found that that dead person was still in the other room and was stuck performing an action... I couldn't interact with dead-person in any way and I couldn't leave the room because the system thought the fight was still going on.

That's a major glitch. It also only happened once out of the dozen times I've gone through the Keep.

The morals of this story are:

1. bugs are bugs. They don't always have to show up but they can be huge problems.

2. Explaining bugs can easily sound like the ramblings of a complete loon if that loon is trying to avoid spoilers...

[jennamarae]

Eurypterid wrote...

Sorry for the delay in responding here, but I was out.

That's completely fair, but you've taken my point out of context. What I was referring to was I've seen long-time BioWare customers state they're either not going to buy anything from BioWare again or are having serious second thoughts. BioWare has, IMO, a great track record with their games and I'd have thought it would take more than the delay of RtO (eveni if it was handled less well than people would have liked) to make them jump ship.

No worries, I figured you'd get to it when you got a chance. No pitchforks here, I promise!

I understood your point, I was just giving my view as a first time customer. I've seen several people post in the forums that the lack of communication and constant delays are typical from other Bioware games, so it seems some don't think they have that great of a track record when it comes to customer relations which are arguably just as important as having a good product. So perhaps it's not just the RtO fiasco, but a culmination of events that have gotten them to the point of trying to decide if the product is worth the hassle involved. Just an idea, since I can't presume to speak for anyone but myself.

As a new customer, all you can do is go by first impressions. If that isn't a good impression, I can understand why you'd hesitate to do business with them again.

Sadly, you're one of the few who does understand that point...

To put this in perspective, this particular game has crashed on me more than any other game I've bought in the last 5 years. But I've bought a lot of BioWare games, and been on their forums for a long time. I'm impressed enough with them that I'll still do business, chalking up my issues with this game as an anomaly. We'll see what happens with ME2 and any other games coming down the pipe. If they're all crash-prone as well, then I'll have to take stock of the situation. But as things stand for me, with my experience with BioWare to this point, this isn't enough to make me walk away. They've been great for a long time and they get a lot of leeway from me because of that.

That's fair. I've had similar experiences with other game companies where I was willing to give them the benefit of the doubt based on past experiences and hold off on passing judgement. As far as first impressions go though, at this point Bioware isn't making a very good one with the silent treatment. I'm not writing them off just yet because I believe in second chances and the base game is still great despite all the bugs I've run into. But it would be extremely helpful if they could keep their fan base updated when it comes to these types of things. I know you have no control over that and can't do much about it, so I don't expect you to. It just would be nice if those in a position to do so, would.