Aller au contenu

Photo

Bioware, rushing, and lots and lots of bugs...


417 réponses à ce sujet

#1
Wishpig

Wishpig
  • Members
  • 2 173 messages
First off, let me say, the more new pics, info, ect released on DA2, the more hyped I get. It just keeps looking and sounding cooler and cooler. While I had faith bioware would make a good product, I certainly had my worries at first... allot of them. But they are almost all dead and buried at this point ;)

I do have one big worry still left though, and one that just seems to be getting more and more prevelent in bioware products.

Bugs. And not the creepy crawly kind. The game breaking, fun raping, experiance ruining kind.

I get it. You cannot avoid bugs, especially with PC games (with systems you have pretty consitent tech to test... not so with PCs which range extremely).

But, as of late, bioware games are f*in plagued with issues big and small. DA:O was pretty bad. My first playthrough had several game-breaking bugs and many other annoying smaller ones. Awakening was even worse, to many, almost unplayible. And the DLC has been plagued with bugs as well, to the point I don't buy them on release (a good call with Witch Hunt...)

Also, as of late, it seems games and DLC are coming out faster and faster... I have no doubt that has a very bad effect on bugs as less time = less time spent cleaning up and finding bugs. Rushed games = buggy games. Fact.

People called it with Awakening, many said it seemed rushed and would must likley suffer from bugs. They were right. Now people are saying the same with DA2. Like I said, I think DA2 looks fantastic, but even if they started making the game before DA:O was even finished (which I doubt), the game would have a very short development time compared to other sequels.

Anyone else worried, and any devs willing to give a few comforting words?

#2
Saibh

Saibh
  • Members
  • 8 071 messages
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?

#3
Guest_distinguetraces_*

Guest_distinguetraces_*
  • Guests
:-(

#4
SelphieSK

SelphieSK
  • Members
  • 769 messages
That's pretty much the only thing bugging me (ha!) so far: the prospect of bugs ruining my enjoyment.

#5
Wishpig

Wishpig
  • Members
  • 2 173 messages

SelphieSK wrote...

That's pretty much the only thing bugging me (ha!) so far: the prospect of bugs ruining my enjoyment.


ZING!

Wishpig approves +.05

#6
NonCanon

NonCanon
  • Members
  • 203 messages
I'm so worried that it's being rushed. I want something finished, not something rushed and buggy. Although I didn't suffer from game-breaking bugs during my DA:O playthroughs, Awakening was almost unbearably buggy. /:

#7
AndrahilAdrian

AndrahilAdrian
  • Members
  • 651 messages
This is my worry too. Recently Bioware seem to have been turning into Obsidian. Witch Hunt and Lair of the shadow broker both had game breaking bugs (of the epic fail variety). Awakening was buggy. DA didn't have anything game breaking, but the choices sometimes contradicted themselves, indicating lack of polish. The only recent game to escape this was ME2 (probably because it is Bioware's flagship franchise). Considering how quickly DA2 is coming out, I believe I have cause to be very worried. I may not play DA2 until a few patches come out.

Modifié par AndrahilAdrian, 09 septembre 2010 - 12:02 .


#8
upsettingshorts

upsettingshorts
  • Members
  • 13 950 messages
While I don't disagree in principle this strikes me as a wonderful opportunity to get on one of my many soapboxes - I keep them in the garage - and rant about a pet peeve.

The phrase "game breaking."

A game breaking bug is one that quite literally does not allow one to continue the game, either due to crash or unbreakable loop error. People tend to use the term for anything that ruins their enjoyment of the game, not halt their progress. The only game breaking bug in DA:O I am aware of was the one in A Paragon of Her Kind where you could find yourself stuck between the two options given a certain set of circumstances. Using the phrase for annoyances cheapens it, and that annoys me.

/steps off box.

Now - no, I think it's unreasonable to get worried about bugs because we have quite literally no idea what to expect. Number of bugs isn't like WHIP in baseball in that the number one year is indicative of what to expect the next year. In short: We'll see.

Modifié par Upsettingshorts, 09 septembre 2010 - 12:02 .


#9
SelphieSK

SelphieSK
  • Members
  • 769 messages

Wishpig wrote...

SelphieSK wrote...

That's pretty much the only thing bugging me (ha!) so far: the prospect of bugs ruining my enjoyment.


ZING!

Wishpig approves +.05


+.05?!
I'll never get approval bonuses at that rate! :o

#10
Stanley Woo

Stanley Woo
  • BioWare Employees
  • 8 368 messages
i'm surprised that I agree so strongly with someone named "Upsettingshorts."

#11
Blastback

Blastback
  • Members
  • 2 723 messages
This is definatly my biggest concern. Espesially in light of the fact that some bugs like the ones causeing Vigilence and the Armor of the Sentinal have been hinted at being unfixable for consoles. How the heck could anyone miss that those two didn't look right on consoles anyway?

#12
Wishpig

Wishpig
  • Members
  • 2 173 messages

Upsettingshorts wrote...

While I don't disagree in principle this strikes me as a wonderful opportunity to get on one of my many soapboxes - I keep them in the garage - and rant about a pet peeve.

The phrase "game breaking."

A game breaking bug is one that quite literally does not allow one to continue the game, either due to crash or unbreakable loop error. People tend to use the term for anything that ruins their enjoyment of the game, not halt their progress. The only game breaking bug in DA:O I am aware of was the one in A Paragon of Her Kind where you could find yourself stuck between the two options given a certain set of circumstances. Using the phrase for annoyances cheapens it, and that annoys me.

/steps off box.

Now - no, I think it's unreasonable to get worried about bugs because we have quite literally no idea what to expect. Number of bugs isn't like WHIP in baseball in that the number one year is indicative of what to expect the next year. In short: We'll see.


I consider a game breaking bug...

A. A point in the game or a reoccuring situation that causes frequent crashes.
B. A point where the story where you can get stuck and must reload. Obviously the worst kind.

Maybe it's unfair to consider A "game-breaking" as many see "game-breaking" as B. But it still BREAKS my game... so... yeah.

I ran into quite a bit of A and a B situation three times (once with the Paragon quest and twice at the Zevran recruitment scene). So I was frustrated somewhat.

For you last part, it is totally fair to get worried about bugs. As they have been getting worse of late in bioware games and the fact is rushed games with short development times are almost always plaugued with bugs. We obviously can't condemn the game, but it is an fair and educated guess worth discussing.

Modifié par Wishpig, 09 septembre 2010 - 12:13 .


#13
Blessed Silence

Blessed Silence
  • Members
  • 1 381 messages

Upsettingshorts wrote...

While I don't disagree in principle this strikes me as a wonderful opportunity to get on one of my many soapboxes - I keep them in the garage - and rant about a pet peeve.

The phrase "game breaking."

A game breaking bug is one that quite literally does not allow one to continue the game, either due to crash or unbreakable loop error. People tend to use the term for anything that ruins their enjoyment of the game, not halt their progress. The only game breaking bug in DA:O I am aware of was the one in A Paragon of Her Kind where you could find yourself stuck between the two options given a certain set of circumstances. Using the phrase for annoyances cheapens it, and that annoys me.

/steps off box.

Now - no, I think it's unreasonable to get worried about bugs because we have quite literally no idea what to expect. Number of bugs isn't like WHIP in baseball in that the number one year is indicative of what to expect the next year. In short: *in Duncan's voice* You'll see.


Fixed it for you.

#14
SelphieSK

SelphieSK
  • Members
  • 769 messages

Blessed Silence wrote...

Upsettingshorts wrote...

While I don't disagree in principle this strikes me as a wonderful opportunity to get on one of my many soapboxes - I keep them in the garage - and rant about a pet peeve.

The phrase "game breaking."

A game breaking bug is one that quite literally does not allow one to continue the game, either due to crash or unbreakable loop error. People tend to use the term for anything that ruins their enjoyment of the game, not halt their progress. The only game breaking bug in DA:O I am aware of was the one in A Paragon of Her Kind where you could find yourself stuck between the two options given a certain set of circumstances. Using the phrase for annoyances cheapens it, and that annoys me.

/steps off box.

Now - no, I think it's unreasonable to get worried about bugs because we have quite literally no idea what to expect. Number of bugs isn't like WHIP in baseball in that the number one year is indicative of what to expect the next year. In short: *in Duncan's voice* You'll see.


Fixed it for you.


Seeing how Duncan ended... :?

#15
Bruddajakka

Bruddajakka
  • Members
  • 1 508 messages
Pretty sure it's being rushed. And a lot of things in Origins were unfinished. Seriously look at some of the restoration patches, and try to honestly tell me it wasn't. Now we get WH which was probably made in like....a week or two considering GoA just came out. I mean seriously how the heck can you release a product that's supposed to have an auto save at the end, and it doesn't. Did anyone even play through it first?



And then you get things like them removing/limiting skills because they don't want to bother doing animations/revising the skills between the classes.

#16
upsettingshorts

upsettingshorts
  • Members
  • 13 950 messages
"Art is never finished, only abandoned.” - Leonardo da Vinci


#17
JigPig

JigPig
  • Members
  • 657 messages

Bruddajakka wrote...

Pretty sure it's being rushed. And a lot of things in Origins were unfinished. Seriously look at some of the restoration patches, and try to honestly tell me it wasn't. Now we get WH which was probably made in like....a week or two considering GoA just came out. I mean seriously how the heck can you release a product that's supposed to have an auto save at the end, and it doesn't. Did anyone even play through it first?

And then you get things like them removing/limiting skills because they don't want to bother doing animations/revising the skills between the classes.


A game that started development in 2004 is unfinished because it has some cut content?
How long were they supposed to spend on it? Decades?

#18
Wishpig

Wishpig
  • Members
  • 2 173 messages

Upsettingshorts wrote...

"Art is never finished, only abandoned.” - Leonardo da Vinci


Lol, thats actually a really cool quote... I gotta remember that one.

#19
LucianTansey

LucianTansey
  • Members
  • 39 messages
I agree that with RPG's in general, and worryingly so with DA, holes in conversation options that cause bugs seem to a prevailent frequency. It almost comes across as lack of playtesting, which is just poor management on Bioware's part.



I for one, play RPG's like DA, for the history, story & background as much as the action, and bugs that glitch or ignore my choices, are "game breaking" for me. If the game doesnt recognise my choices, whats the point?

#20
Bruddajakka

Bruddajakka
  • Members
  • 1 508 messages

JigPig wrote...

Bruddajakka wrote...

Pretty sure it's being rushed. And a lot of things in Origins were unfinished. Seriously look at some of the restoration patches, and try to honestly tell me it wasn't. Now we get WH which was probably made in like....a week or two considering GoA just came out. I mean seriously how the heck can you release a product that's supposed to have an auto save at the end, and it doesn't. Did anyone even play through it first?

And then you get things like them removing/limiting skills because they don't want to bother doing animations/revising the skills between the classes.


A game that started development in 2004 is unfinished because it has some cut content?
How long were they supposed to spend on it? Decades?


If needed. Not as if the game was going any where.

#21
contown

contown
  • Members
  • 252 messages

Stanley Woo wrote...

i'm surprised that I agree so strongly with someone named "Upsettingshorts."


Come on, Mr. Woo. You have to see that the bug problem has been getting worse. Even if they're not "game breaking," as you define it, a lot of the bad ones are easily enjoyment breaking. Especially the ones that ruin the ending of a story-centric 40 hour game.

#22
Bobad

Bobad
  • Members
  • 2 946 messages
Well it's not just a worry for PC gamers, on xbox playing Awakenings I have to do things in a certain ways to prevent such things as approval bugs, not exactly game breaking but not exactly as intended either, requiring a couple of restarts and some reading up on independant forums to work around :(.



I still enjoyed it though.

#23
JigPig

JigPig
  • Members
  • 657 messages

Bruddajakka wrote...

JigPig wrote...

Bruddajakka wrote...

Pretty sure it's being rushed. And a lot of things in Origins were unfinished. Seriously look at some of the restoration patches, and try to honestly tell me it wasn't. Now we get WH which was probably made in like....a week or two considering GoA just came out. I mean seriously how the heck can you release a product that's supposed to have an auto save at the end, and it doesn't. Did anyone even play through it first?

And then you get things like them removing/limiting skills because they don't want to bother doing animations/revising the skills between the classes.


A game that started development in 2004 is unfinished because it has some cut content?
How long were they supposed to spend on it? Decades?


If needed. Not as if the game was going any where.



That's the kind of mentality that shows you have zero knowledge of the video game industry.

#24
Mecha Tengu

Mecha Tengu
  • Members
  • 1 823 messages

contown wrote...

Stanley Woo wrote...

i'm surprised that I agree so strongly with someone named "Upsettingshorts."


Come on, Mr. Woo. You have to see that the bug problem has been getting worse. Even if they're not "game breaking," as you define it, a lot of the bad ones are easily enjoyment breaking. Especially the ones that ruin the ending of a story-centric 40 hour game.


they have no choice but to rush, EA is keeping bioware on a tight leash

#25
Orbweaver

Orbweaver
  • Members
  • 84 messages
In the past, I've been known to return games for the following reasons:



1. Installation errors. Any time I have to go into the registry on my computer to modify ANYTHING just to get a few files to do what they're supposed to. When I've double checked that my computer meets the necessary requirements to run the game, this is the number one reason I'll get a refund and won't look back.



2. Insanely long load times because the game is checking and rechecking a file several thousand times, instead of the once per instance that it's supposed to do.



3. Consistent crash to desktops after multiple patches have been installed to fix the issues involved. What good is the game if I can't play through it?



Anyway, that's my shortlist on "game breaking" experiences.