404 réponses à ce sujet

[dumael]

Cyonan wrote...

And nobody has answered my question yet: How many other developers do you see revamp as much of their game as you are asking them to do in just patches, and how many just leave it and address it in the sequel?

No studio changes much in my experience for a particular game. They're content to add things alright, but that's about it.

[Ramsutin]

Jesus Christ I did not see the outcome of this when this post was created. Some people....

[Tronar]

Reizo Ryuu wrote...

Ronnie Blastoff wrote...

My issue isn't so much as they are fixing the bugs, as much as wtf... why are there so many bugs when the game is released. Its rediculous how many problems were in the game when it first came out. Not just how many, but a specific bug in particular (vangaurd glitch). HOW THE F*CK DO YOU RELEASE THAT SHYT??? How did that make it past quality assurence? WHO!!! WHO gave that shyt the O.K. for release?

You are a ridiculously awful poster, just because it's called QA doesn't mean they can test every variable specifically because not every variable is known to them when testing starts.
Every single digital product releases with bugs, even your example of super mario on the NES was released with numerous glitches; this is simply the nature of any kind of programming that gets big enough.

QA is there to test and catch what they can before the game goes gold, they only have a set number of people that can test for a set period of time before the deadlines for making the master copy comes around; even if you would take a year for just pure testing (which is economically unfeasable ofcourse), the product will still ship with bugs/glitches simply because of a virtually unlimited amount of variables and the fact that fixing one bug can simply introduce another.

And yes, the userbase finding some bugs the QA team may or may not have found is simply because the userbase base is literally thousands of times larger than any QA team in the world which ofcourse drastically raises the posibility of many different variables to appear.

This thread is seriously disgusting.

Well, of course thousand players can find really bizarre bugs that a QA would most likely miss. No doubt about that. But the majority of reasonable players isn't asking for miracles here.

Let's take for example the Vanguard Glitch, which was already known since the DEMO!
I think it's a perfectly legitimitate question to ask, why Bioware couldn't fix that BEFORE releasing the game.

And please don't get me started on the work of Bioware's particular QA-team.

Unfortunately there are plenty of issues in the game where ONE SERIOUS PLAYTHROUGH would have been sufficient to detect the bug! No need for bizarre timings and specific configuration to have those happen.

You want a specific example? Although I REALLY like the idea as such, take "Hazard Reactor".

So far in EVERY game I played on Hazard Reactor there was at least ONE (if not many!) incident(s), where an enemy would walk THROUGH THE CLOSED(!) REACTOR DOORS!

It is a huge mystery to me, how on earth this could have been overlooked by the design team.

It doesn't matter if you play the game on Bronze or Platinum, as long as the enemy is strong enough to survive the reactor heat, it will walk through the CLOSED doors. I've seen Banshees, Primes, Atlasses and Praetorians do it. Also Scions, Rocket Troopers, Brutes and Phantoms. Hell even Dragoons were jumping through the closed doors in no time.

If I would invent something like the venting reactor, my FIRST and HIGHEST PRIORITY test item for the QA department would be to check, if everything works as intended, meaning:
1. does stuff get killed or at least damaged in the reactor?
2. if it does only get damaged, do they wait behind the doors until they open again?

My only explanation why this bug was only detected after the DLC had been released:
THERE WAS NOT TESTING DONE! NONE AT ALL.

So what is your response to that, Mr. "this thread is disgusting"?

Modifié par Tronar, 07 février 2013 - 08:23 .

[Ramsutin]

^Tell me all about your experience in this field again.

[Derek Hollan]

It is time to put this thread to rest.

No good comes from attacking things people really have no clue about.

First:  Bugs happen.  It is QA's job to bring it to the attention of the team.  Period.  It is not their job to fix it.  When a deadline for release of DLC comes and goes then the product, in whatever state it is in, is assessed on a cost vs time basis.

Second:  I don't come down to your job and slap the plunger out of your hand telling you you are doing it wrong.  Enough is enough.

Cheers