1286 réponses à ce sujet

[SamimaS]

I'd bet my bottom dollar that auto attack will be available, for a price!

[Vaille]

"Nathan Frederick wrote...

We're looking into these, and other issues. We do not currently have an ETA for a patch.

There will not be a patch by the end of the week - the time it takes between leaving the hands of internal testing (once we come up with a solution), through the distribution process and into your hands is more than a week alone, and completely outside our control."

This is why we think the feature never was implemented. If it was only an issue with the manufacturers not including the file, then what's there to "look into" and why do they have to"come up with a solution?" They send the file for certification, it's included in a patch, and we have it.

Modifié par Vaille, 09 mars 2011 - 07:37 .

[TassadarCRG]

so Bioware, a patch is coming to fix the lost promised function ????

[Vmode]

Mousers wrote...

I have to agree with a previous poster regarding Chris's post and the post on the technical forum. They don't compliment each other and looks very fishy. If Chris's post is true, then what they gave the Master to patch into the game that was going out.. and was already approved since it was going to Master, should be able to be patched sooner than later. Unless they are going for fixing many bugs and do one big patch rather than several. Which wasn't mentioned.

Which post on the technical forum are you referring to?

[Tekman9]

Duncaaaaaan wrote...

Who knows. But its really not as bad as it sounds. It will play exactly like it would with auto attack, except you press A twice every second.

lololol

[Tekman9]

Also, you guys are getting too lawyer on these different comments. It is quite possible that they internally tested it and did forget it. When you release DLC/patches it has to go through a microsoft (or sony, but im more familiar with the way microsoft does DLC/patches) certification process so they make sure people are releasing a ton of broke DLC/patches that is bricking peoples xboxes.

Just because Bioware tested something and 'forgot' to put it on the CD doesnt preclude it from going thru the normal DLC/patch rigors, which usually include at least a week of testing.

Im speaking as someone that knows a lot about 'waiting' for patches being a sports gamer, and as also as a programmer (not gaming industry tho)

[Mousers]

Vmode wrote...

Mousers wrote...

I have to agree with a previous poster regarding Chris's post and the post on the technical forum. They don't compliment each other and looks very fishy. If Chris's post is true, then what they gave the Master to patch into the game that was going out.. and was already approved since it was going to Master, should be able to be patched sooner than later. Unless they are going for fixing many bugs and do one big patch rather than several. Which wasn't mentioned.

Which post on the technical forum are you referring to?

social.bioware.com/forum/1/topic/301/index/6414722

This is the 360 Technical thread regarding when a patch will be out for the AA and other bugs. The BW post is on page 1.

[untoldsarcasm]

I can't believe that there is still no official response to this that isn't hidden away in these forums.

[Mousers]

Tekman9 wrote...

Also, you guys are getting too lawyer on these different comments. It is quite possible that they internally tested it and did forget it. When you release DLC/patches it has to go through a microsoft (or sony, but im more familiar with the way microsoft does DLC/patches) certification process so they make sure people are releasing a ton of broke DLC/patches that is bricking peoples xboxes.

Just because Bioware tested something and 'forgot' to put it on the CD doesnt preclude it from going thru the normal DLC/patch rigors, which usually include at least a week of testing.

Im speaking as someone that knows a lot about 'waiting' for patches being a sports gamer, and as also as a programmer (not gaming industry tho)

Granted and true. However, the implication given by Chris's post is what, at least my opinion, I have been referring to  in my logical thinking manner.

When the game is done, it goes for approval from the various places including the console companies.
Once approved it goes to Master, final spot for a master disc to be made so they can be mass produced for shipping.
The AA code was written, tested that it will work being added to the already finished product, sent and approved by the console houses, and sent to Master to be added to the Game Master game already in their department.

Whew, they got it done, the file works with the existing game by just adding a file to the disk. Bad news is, as Chris states, the Mastering department messed up.

The file has already been approved by the console houses.  It could be the file needs "red tape" approval again because it will go out as a patch and not as an addition to the game disc as was previously approved. I see this as a week for re-approval and getting the file setup for auto DL.

If it is longer then a) They are going to bundle many bug fixes in one patch. The AA code was never written.

I give them the benefit of the doubt and go with A.
Because of the past/present forum threads on the AA issue, I think it would be in BW best interest to get that "already finished, tested, approved" file for the  AA uploaded to the customers asap. It would fix so much in customer confidence, trust and  respect. Then get the rest out that is on the long time chain once done.

[didymos1120]

untoldsarcasm wrote...

I can't believe that there is still no official response to this that isn't hidden away in these forums.

edit: scratch that.  I was clearly responding to some entirely different post I apparently imagined.

Modifié par didymos1120, 09 mars 2011 - 09:14 .

[djackson75]

Mousers wrote...

Tekman9 wrote...

Also, you guys are getting too lawyer on these different comments. It is quite possible that they internally tested it and did forget it. When you release DLC/patches it has to go through a microsoft (or sony, but im more familiar with the way microsoft does DLC/patches) certification process so they make sure people are releasing a ton of broke DLC/patches that is bricking peoples xboxes.

Just because Bioware tested something and 'forgot' to put it on the CD doesnt preclude it from going thru the normal DLC/patch rigors, which usually include at least a week of testing.

Im speaking as someone that knows a lot about 'waiting' for patches being a sports gamer, and as also as a programmer (not gaming industry tho)

Granted and true. However, the implication given by Chris's post is what, at least my opinion, I have been referring to  in my logical thinking manner.

When the game is done, it goes for approval from the various places including the console companies.
Once approved it goes to Master, final spot for a master disc to be made so they can be mass produced for shipping.
The AA code was written, tested that it will work being added to the already finished product, sent and approved by the console houses, and sent to Master to be added to the Game Master game already in their department.

Whew, they got it done, the file works with the existing game by just adding a file to the disk. Bad news is, as Chris states, the Mastering department messed up.

The file has already been approved by the console houses.  It could be the file needs "red tape" approval again because it will go out as a patch and not as an addition to the game disc as was previously approved. I see this as a week for re-approval and getting the file setup for auto DL.

If it is longer then a) They are going to bundle many bug fixes in one patch. The AA code was never written.

I give them the benefit of the doubt and go with A.
Because of the past/present forum threads on the AA issue, I think it would be in BW best interest to get that "already finished, tested, approved" file for the  AA uploaded to the customers asap. It would fix so much in customer confidence, trust and  respect. Then get the rest out that is on the long time chain once done.

The problem comes in the timing.. The game went for mastering 24 days before release.. There's NO WAY I am believing that nobody at Bioware knew that the feature was left out any more than maybe 3 days AT MOST after it went gold. I am not buying that nobody at Bioware got a release copy, popped it in a console, and saw that the feature wasn't there.

Now once that happens, the right thing to do would be to patch it up, send it to microsoft for testing, and have it ready for a day 1 patch.. In the interim, you make a public statement that says "we made a big error in leaving the feature out, we apologize, the patch will be available day one via Live or PSN download".. If they did that, they would have looked dumb for the screw up, but it would have done a lot of good PR in that they would have looked like they cared about their error.

Instead, they said nothing.... they closed threads, and ignored questions in chats...  then on the eve of release, made one statement buried on page 5 of a message board thread... There hasn't been one public statement made at all to this moment..

If you didn't get to go on this website the night before release, you would have no idea the feature was missing. So you get the game home, open it up, and have a big WTF moment.. Guess what, stores don't take back opened games... Good luck sending your opened game back to Amazon.....

THAT is the issue..

[didymos1120]

Mousers wrote...

Because of the past/present forum threads on the AA issue, I think it would be in BW best interest to get that "already finished, tested, approved" file for the  AA uploaded to the customers asap. It would fix so much in customer confidence, trust and  respect. Then get the rest out that is on the long time chain once done.

That they most definitely should do, even if it does mean they have to just turn around and do it again immediately for any other fixes in the works. 

[Vmode]

Mousers wrote...

Vmode wrote...

Mousers wrote...

I have to agree with a previous poster regarding Chris's post and the post on the technical forum. They don't compliment each other and looks very fishy. If Chris's post is true, then what they gave the Master to patch into the game that was going out.. and was already approved since it was going to Master, should be able to be patched sooner than later. Unless they are going for fixing many bugs and do one big patch rather than several. Which wasn't mentioned.

Which post on the technical forum are you referring to?

social.bioware.com/forum/1/topic/301/index/6414722

This is the 360 Technical thread regarding when a patch will be out for the AA and other bugs. The BW post is on page 1.

*slips into corporate analysis slippers again*

From what I can tell that the only post from a Bioware person in there was the one made by Nathan Frederick and not Chris. Now, I have no idea what these two people actually do in the company, but given the fact that they where apparently made at pretty much the same time when the problem was first highlighted in a public manner it's higly possible that on (or both) where just post of assumptions.
It's quite possible they had some general idea how to they where going to handle things but hadn't, at that time, nailed down the details. So the people that responded resorted to posting assumptions based on what they thought was probably, resulting in varying messages to customers. Then later on as new facts emerged and the company got a detailed strategy together the assumptions they'd made back then, which had been resonable at the the time, no longer turned out to be accurate.

It's a common thing, especially with larger companies to get different messages from different people when you first encounter a problem and CS agents don't get any definitive information from their managers but have to say something in order to blunt the rage of angry customers. So they make estimates based on the snippets of information they are privy to.

Again: all hypothetical speculation on my part.

Also, then patching software every company has a process they go throug. No matter how minute the change, they have to go through several steps to ensure they don't end up making things worse (and again, here we have the problem of Microsoft and Sony also demanding time to approve distribution via their networks).
This is why they often prefer to hold of a bit and fix several more issues in one patch rather then releasing a bunch of smaller ones to fix individual problems, because it saves them time (and time, as we all know, is money). And given the fact that there is already proof the game has several other types of glitches (including highly unbalancing infinite gold/experience ones) I'm guessing we'll be waiting quite some time for any sort of patch to fix this particular issue.

In other words: Sucks to be us.

PS: Excuse any spelling and grammatical mistakes of mine. English is not my first language.

[Mousers]

untoldsarcasm wrote...

I can't believe that there is still no official response to this that isn't hidden away in these forums.

Yes it would be nice to have a sticky topic where there is one place for everyone to go and for them to respond, when they are ready.

But if you stand in their shoes, best way to get rid of a fire (which is the bugs and not including AA as promised) is with the ole proverbial blanket. Silence. And when you must say something don't shout it out ie sticky thread. Just answer a question passively inside an exsisting thread. Do I agree with this procedure, heck no. Do bigger gaming houses do this, no. Do bigger gaming houses communicate frequently when customers have big concerns, you bet! It is why they are bigger.

So the good news is with regulars here, and those that find little tidbits, we can find out what is happening by coming here. Just need to keep it bumped to stay on the first page.

[unixbomber]

 For someone who already has borderline carpal tunnel, this has made the game unplayable.

Discomfort issues aside, I can't see the enjoyment of smashing the same button over and over. This is different than the abilities, which generally have some tactical side effects and to are best used with some manner of timing. At first you may think "Wow, the combat does seem a lot faster and more engaging", but 5 minutes and 300 button presses later, I understand completely why most games have auto-attack for the base attack as a default.

I am glad they give an option for those who apparently need something to do with the 3 seconds between ability recycles, but not being able to enable auto-attack at release has been extremely disappointing.

Modifié par unixbomber, 09 mars 2011 - 09:35 .

[djackson75]

Mousers wrote...

untoldsarcasm wrote...

I can't believe that there is still no official response to this that isn't hidden away in these forums.

Yes it would be nice to have a sticky topic where there is one place for everyone to go and for them to respond, when they are ready.

But if you stand in their shoes, best way to get rid of a fire (which is the bugs and not including AA as promised) is with the ole proverbial blanket. Silence. And when you must say something don't shout it out ie sticky thread. Just answer a question passively inside an exsisting thread. Do I agree with this procedure, heck no. Do bigger gaming houses do this, no. Do bigger gaming houses communicate frequently when customers have big concerns, you bet! It is why they are bigger.

So the good news is with regulars here, and those that find little tidbits, we can find out what is happening by coming here. Just need to keep it bumped to stay on the first page.

What is actually baffling me is the major video game websites(IGN, Gamespot, Gametrailers, 1up, destructoid, joysiq, etc...) not running a story on this issue. Since it's on message boards pretty much everywhere, there's no way that the big guys don't know it's an issue.  Regardless of what people may think of those entities personally, they are the big news presenters... This whole thing just stinks..

[Haexpane]

Tekman9 wrote...

Duncaaaaaan wrote...

Who knows. But its really not as bad as it sounds. It will play exactly like it would with auto attack, except you press A twice every second.

lololol

lolx2

[Tekman9]

Mousers wrote...

Tekman9 wrote...

Also, you guys are getting too lawyer on these different comments. It is quite possible that they internally tested it and did forget it. When you release DLC/patches it has to go through a microsoft (or sony, but im more familiar with the way microsoft does DLC/patches) certification process so they make sure people are releasing a ton of broke DLC/patches that is bricking peoples xboxes.

Just because Bioware tested something and 'forgot' to put it on the CD doesnt preclude it from going thru the normal DLC/patch rigors, which usually include at least a week of testing.

Im speaking as someone that knows a lot about 'waiting' for patches being a sports gamer, and as also as a programmer (not gaming industry tho)

Granted and true. However, the implication given by Chris's post is what, at least my opinion, I have been referring to  in my logical thinking manner.

When the game is done, it goes for approval from the various places including the console companies.
Once approved it goes to Master, final spot for a master disc to be made so they can be mass produced for shipping.
The AA code was written, tested that it will work being added to the already finished product, sent and approved by the console houses, and sent to Master to be added to the Game Master game already in their department.

Whew, they got it done, the file works with the existing game by just adding a file to the disk. Bad news is, as Chris states, the Mastering department messed up.

The file has already been approved by the console houses.  It could be the file needs "red tape" approval again because it will go out as a patch and not as an addition to the game disc as was previously approved. I see this as a week for re-approval and getting the file setup for auto DL.

If it is longer then a) They are going to bundle many bug fixes in one patch. The AA code was never written.

I give them the benefit of the doubt and go with A.
Because of the past/present forum threads on the AA issue, I think it would be in BW best interest to get that "already finished, tested, approved" file for the  AA uploaded to the customers asap. It would fix so much in customer confidence, trust and  respect. Then get the rest out that is on the long time chain once done.

It doesn't matter that it was already tested once.  I work in software, theres plenty of **** we need to have tested even though it shouldnt even be possible for it to cause a problem.  Microsoft isnt going to take someones word for it, then find out they have 40k bricked consoles from a bad patch.  

And to the other guy commenting about the 'timing' of the issue.  Consider this:  Microsoft allows 2 (this is what i recall off the top of my head) free patches or title updates per game.  After that, the developer/publisher needs to pay for the ability to release another patch.  Thats why you hardly ever see xbox games with more than 2 patches outside of the HUGE titles like Madden.  (tho I think NCAA fb released 3 patches this year, bravo).  They could very well know of this issue weeks ago like you say, but dont find it cost effective enough to use up a free patch on.  They are probably waiting a little bit to get more of a comprehensive patch out.

[djackson75]

Tekman9 wrote...

Mousers wrote...

Tekman9 wrote...

Also, you guys are getting too lawyer on these different comments. It is quite possible that they internally tested it and did forget it. When you release DLC/patches it has to go through a microsoft (or sony, but im more familiar with the way microsoft does DLC/patches) certification process so they make sure people are releasing a ton of broke DLC/patches that is bricking peoples xboxes.

Just because Bioware tested something and 'forgot' to put it on the CD doesnt preclude it from going thru the normal DLC/patch rigors, which usually include at least a week of testing.

Im speaking as someone that knows a lot about 'waiting' for patches being a sports gamer, and as also as a programmer (not gaming industry tho)

Granted and true. However, the implication given by Chris's post is what, at least my opinion, I have been referring to  in my logical thinking manner.

When the game is done, it goes for approval from the various places including the console companies.
Once approved it goes to Master, final spot for a master disc to be made so they can be mass produced for shipping.
The AA code was written, tested that it will work being added to the already finished product, sent and approved by the console houses, and sent to Master to be added to the Game Master game already in their department.

Whew, they got it done, the file works with the existing game by just adding a file to the disk. Bad news is, as Chris states, the Mastering department messed up.

The file has already been approved by the console houses.  It could be the file needs "red tape" approval again because it will go out as a patch and not as an addition to the game disc as was previously approved. I see this as a week for re-approval and getting the file setup for auto DL.

If it is longer then a) They are going to bundle many bug fixes in one patch. The AA code was never written.

I give them the benefit of the doubt and go with A.
Because of the past/present forum threads on the AA issue, I think it would be in BW best interest to get that "already finished, tested, approved" file for the  AA uploaded to the customers asap. It would fix so much in customer confidence, trust and  respect. Then get the rest out that is on the long time chain once done.

It doesn't matter that it was already tested once.  I work in software, theres plenty of **** we need to have tested even though it shouldnt even be possible for it to cause a problem.  Microsoft isnt going to take someones word for it, then find out they have 40k bricked consoles from a bad patch.  

And to the other guy commenting about the 'timing' of the issue.  Consider this:  Microsoft allows 2 (this is what i recall off the top of my head) free patches or title updates per game.  After that, the developer/publisher needs to pay for the ability to release another patch.  Thats why you hardly ever see xbox games with more than 2 patches outside of the HUGE titles like Madden.  (tho I think NCAA fb released 3 patches this year, bravo).  They could very well know of this issue weeks ago like you say, but dont find it cost effective enough to use up a free patch on.  They are probably waiting a little bit to get more of a comprehensive patch out.

I did not know that, and if that's the case, that's fine... The only problem left is the silence on the part of Bioware... they really still should have made it known that this was an issue right away, and they still haven't made a public confirmation that it is an issue at all yet... This message board is seen by however many people are registered on it... they need to make it known...

[Tekman9]

unixbomber wrote...

 For someone who already has borderline carpal tunnel, this has made the game unplayable.

Discomfort issues aside, I can't see the enjoyment of smashing the same button over and over. This is different than the abilities, which generally have some tactical side effects and to are best used with some manner of timing. At first you may think "Wow, the combat does seem a lot faster and more engaging", but 5 minutes and 300 button presses later, I understand completely why most games have auto-attack for the base attack as a default.

I am glad they give an option for those who apparently need something to do with the 3 seconds between ability recycles, but not being able to enable auto-attack at release has been extremely disappointing.

exactly, from playing 2 seconds of combat in the demo I was like 'wtf are they thinking'  Its not timing, or skill based.  Its just mashing for mashings sake.  And its a LOT of mashing.  

[Magnus90]

I just hope theres some way to have get the autto-attack option available

[dwv0303]

Tekman9 wrote...

Mousers wrote...

Tekman9 wrote...

Also, you guys are getting too lawyer on these different comments. It is quite possible that they internally tested it and did forget it. When you release DLC/patches it has to go through a microsoft (or sony, but im more familiar with the way microsoft does DLC/patches) certification process so they make sure people are releasing a ton of broke DLC/patches that is bricking peoples xboxes.

Just because Bioware tested something and 'forgot' to put it on the CD doesnt preclude it from going thru the normal DLC/patch rigors, which usually include at least a week of testing.

Im speaking as someone that knows a lot about 'waiting' for patches being a sports gamer, and as also as a programmer (not gaming industry tho)

Granted and true. However, the implication given by Chris's post is what, at least my opinion, I have been referring to  in my logical thinking manner.

When the game is done, it goes for approval from the various places including the console companies.
Once approved it goes to Master, final spot for a master disc to be made so they can be mass produced for shipping.
The AA code was written, tested that it will work being added to the already finished product, sent and approved by the console houses, and sent to Master to be added to the Game Master game already in their department.

Whew, they got it done, the file works with the existing game by just adding a file to the disk. Bad news is, as Chris states, the Mastering department messed up.

The file has already been approved by the console houses.  It could be the file needs "red tape" approval again because it will go out as a patch and not as an addition to the game disc as was previously approved. I see this as a week for re-approval and getting the file setup for auto DL.

If it is longer then a) They are going to bundle many bug fixes in one patch. The AA code was never written.

I give them the benefit of the doubt and go with A.
Because of the past/present forum threads on the AA issue, I think it would be in BW best interest to get that "already finished, tested, approved" file for the  AA uploaded to the customers asap. It would fix so much in customer confidence, trust and  respect. Then get the rest out that is on the long time chain once done.

It doesn't matter that it was already tested once.  I work in software, theres plenty of **** we need to have tested even though it shouldnt even be possible for it to cause a problem.  Microsoft isnt going to take someones word for it, then find out they have 40k bricked consoles from a bad patch.  

And to the other guy commenting about the 'timing' of the issue.  Consider this:  Microsoft allows 2 (this is what i recall off the top of my head) free patches or title updates per game.  After that, the developer/publisher needs to pay for the ability to release another patch.  Thats why you hardly ever see xbox games with more than 2 patches outside of the HUGE titles like Madden.  (tho I think NCAA fb released 3 patches this year, bravo).  They could very well know of this issue weeks ago like you say, but dont find it cost effective enough to use up a free patch on.  They are probably waiting a little bit to get more of a comprehensive patch out.

That's all well and good and certainly understandle, but why not just say that? Why the stonewall? Why all the "well, we just don't know what we're going to do"? It just seems fishy, which is why I think people are ticked off.

[Mousers]

Stanley Woo wrote ....
there is already a thread discussing auto-attack. Please take your discussion there. Thank you.

And what didn't copy is the link contained in the word 'there'. It is this thread!

Thank you Stanley for sending AA concerns to this thread. All here are passionate, for our own reasons, to have AA patched. And shows we have made enough intelligent posts to have BW lurk or AA customer opinions.

Good job posters. Lets keep it bumped.

Thank you Tekman for pointing out the 2 free patch/upgrade. It makes more sense now that they will bundle as much as they can in 1 patch and save the second for the fallout from the first or a couple biggies that might take weeks to solve/code/test/etc.

It would be nice to get just a little post though. ie "Hugs guys, we hear ya, we're working hard, no eta but will let you know when we can pin it down"

[Tekman9]

id guess the stonewall probably because they just finished working like 100 hour weeks for god knows how long.... they probably dont care to troll the forums right now =P

[Pompeii69]

I don't much care if there is a 2 free patch policy in place for MS, Bioware royally screwed up and useers deserve this option NOW for placing their faith in Bioware. And if it costs them, well then next time they wont screw up quite so badly. Either way, there's been more than enough time to come up with something to get this out to it's users. I too work in software, and am well aware that when a huge f***up occurs, it's all hands on deck, and get it fixed ASAP.