I see here, lists of bugs that people hope get fixed. Individual threads dedicated to certain bugs.
Complaints about others in new threads. People coming on or adding to other threads all the time. Mostly with no outline of information needed, and I wonder, as a person trying to collate all this information into something meaningful I can work with, how useless this is.
Someone (Bioware, since your developers are the ones who have to try to replicate/troubleshoot and fix these bugs), needs to develop a topic that includes, as each header, a bug. For that bug, there should be a webform that asks various technical questions relating to the conditions under which the bug occurred.
This information, in turn, would populate a simple database, which might actually give folks (devs) at a glance, what to focus on and what to ignore.
Such as: (This just happened to me.)
Game: Awakenings expansion (where this web form would be located is directed by this)
Problem: Can not enter abandoned warehouse to complete the personal quest for the Mage (what's his name?) -- this would be the specific form.
Then, on the form, questions like:
Platform ____Mac ___ps3____pc____xbox 360 (and the pc sectio might open up to get more system level info.
Game status: ____Imported character or ____Orlesian Warden
% of game complete: ______
Which main quests finished
which side quests finished
who was in your party
,,,.,,,,note....all of these would be checkbox multiple choice so that the database could be populated.
How long the game had been running at the time?
Any other pertinent infor that the devs can figure might have a bearing on this bug.
I mean the above is just an outline of hte start of an idea, but I know these webforms are not that difficult to create, depending on web platform, as I have done a few myself.
At the moment, it seems that one reason so few fixes come out is that ther is an amazing amoung of confusion about bug reporting int he first place. How can a dev fix a problem in something as "logical" as a program with so much disparate information? It would be a nightmare.
Why not implement something like this, then everyone with the problem could fill out the form, Bioware would get a good idea of the prevalence of the problem and on which systems, and the game state during the problem. Which, at the moment, I cann't even see how they are even getting this information.
This could be done so easily and orderly and make the revision cycle look more organized. Everyone could then see the scope and regular reports based on the information gathered could be passed back to us (since we're reporting bugs in a meticulous and thorough way...
One report per registerd game.
What say you?
Suggestion for organized collection of bug info
Débuté par
PatT2
, mars 29 2010 06:31
#1
Posté 29 mars 2010 - 06:31
#2
Posté 29 mars 2010 - 06:33
Actually, one report per occurrence on a registered game. Makes more sense. More info.
#3
Guest_LordReinhart_*
Posté 29 mars 2010 - 09:39
Guest_LordReinhart_*
Well the problem isn't that they don't know the bugs, it's just them actually fixing them ;[
#4
Posté 30 mars 2010 - 09:23
I'm not sure I agree with that so much as, if you look here for information abou tthose bugs, it's horribly confusing and disorganized. how can one know how many people something affects, if one person posts 20 times, and one hundred people don't post at all?
It's easy to oversimplify that "they just aren't ...." but if you were coding a fix, exactly where would you start, given the mishmash of information you're getting? Do you have to play test every single possible combination of states to determine exactly what is failing where, or if some far off variable is causing a problem? Without organizing the information, they're essentially on the hunt for a serial killer with no computer. We all (those of us who cared) realize it was the computerizing of information, and finally dna, and insitution of procedures that caught the green river killer...because they were awash in data, but no way to know how much of it applied to other disparate pieces.
to simply say they're not, without being there and knowing is far less helpful than my suggestion to make it easier. This is a programming thing, also, and they could sit at their desks all day, but without the right information, how do they know they're not just making things worse because they're not sure what the culprit acutally is?
You're not a computer programmer, are you LordReinhart?
It's easy to oversimplify that "they just aren't ...." but if you were coding a fix, exactly where would you start, given the mishmash of information you're getting? Do you have to play test every single possible combination of states to determine exactly what is failing where, or if some far off variable is causing a problem? Without organizing the information, they're essentially on the hunt for a serial killer with no computer. We all (those of us who cared) realize it was the computerizing of information, and finally dna, and insitution of procedures that caught the green river killer...because they were awash in data, but no way to know how much of it applied to other disparate pieces.
to simply say they're not, without being there and knowing is far less helpful than my suggestion to make it easier. This is a programming thing, also, and they could sit at their desks all day, but without the right information, how do they know they're not just making things worse because they're not sure what the culprit acutally is?
You're not a computer programmer, are you LordReinhart?
#5
Posté 31 mars 2010 - 12:50
It's been done.....
Bioware just chooses not to sticky well compiled and detailed information because its very existence is embarrassing to them...
Look here:
http://social.biowar...67/index/423972
Bioware just chooses not to sticky well compiled and detailed information because its very existence is embarrassing to them...
Look here:
http://social.biowar...67/index/423972





Retour en haut






