1286 réponses à ce sujet

[HonourBorn]

Mick301981 wrote...
Won't affect me much, as I didn't even realize Origins had auto attack till my second playthrough:whistle:

HA! sorry that is halarious!

[Arrtis]

Scorpgul wrote...

djackson75 wrote...

They need to make a public statement... Not that it matters at this point... I'm sure there are plenty of people out there who aren't even going on the internet tonight, who believe it's in the game, only to purchase the game, get it home, and have a big "WTF" moment.

But that was probably the plan anyway... Can't return an open used game after all.

EXACTLY!!! GREEDY BASTARDS!!!

Be sure to return your game copy then.
If you can.

[SorrowAndJoy7]

Couldn't they theoretically split it into separate patches if it was too large to fit under the 360 guidelines.

[Moaradin]

I feel sorry for console players. Not because of the no auto attack, but because you have a console.


I only kid. I hope there is a fix soon. The game isn't out globally yet so you cant really complain until your actually playing it and its not there.

[leggywillow]

Mick301981 wrote...

 Wow, no auto attack on console, huh .  I have to admit Bioware messed up on this one. 

Won't affect me much, as I didn't even realize Origins had auto attack till my second playthrough:whistle:

(Yep, I actually pressed the A button to attack, all through my first playthrough)

/facepalm

Haha!  I'm glad I'm not the only one who did that!  I tapped away at that A button for at least 1 1/2 entire playthroughs of Origins before I realized that my Warden would continue attacking when my thumb took a break.  ::major facepalm::

I'm used to it now, though, so not having auto-attack is going to be a serious bummer.  It kept throwing me off during the demo, and I know it will take a while to get used to the button tapping again.    Hopefully that's the kind of thing they can release a patch for relatively quickly? 

[TJPags]

SorrowAndJoy7 wrote...

Couldn't they theoretically split it into separate patches if it was too large to fit under the 360 guidelines.

I don't know anything about programming, so I don't know.

They haven't been able to do it with the Silverite Mine bug patch.  I don't know if it's unique to that patch, or the nature of a patch (see first comment).

But this is why I'm not sure it even is fixable.

[djackson75]

Moaradin wrote...

I feel sorry for console players. Not because of the no auto attack, but because you have a console.


I only kid. I hope there is a fix soon. The game isn't out globally yet so you cant really complain until your actually playing it and its not there.

"you can't complain now, but you can complain 5.5 hours from now if you're on the east coast in America."

K.

[Arrtis]

leggywillow wrote...

Mick301981 wrote...

 Wow, no auto attack on console, huh .  I have to admit Bioware messed up on this one. 

Won't affect me much, as I didn't even realize Origins had auto attack till my second playthrough:whistle:

(Yep, I actually pressed the A button to attack, all through my first playthrough)

/facepalm

Haha!  I'm glad I'm not the only one who did that!  I tapped away at that A button for at least 1 1/2 entire playthroughs of Origins before I realized that my Warden would continue attacking when my thumb took a break.  ::major facepalm::

I'm used to it now, though, so not having auto-attack is going to be a serious bummer.  It kept throwing me off during the demo, and I know it will take a while to get used to the button tapping again.    Hopefully that's the kind of thing they can release a patch for relatively quickly? 

I thought that once too....didnt last that long though.
I did find myself forgetting once in awhile though.

[AkiKishi]

Chris Priestly wrote...

OK: Here is the story.

Auto-attack option for consoles was added in to the games late in the development cycle after the initial certification build was sent. The auto-attack functionality was sent to be added to the game for testing and approval. This was why staff said it was in game.

Due to an error during mastering, the auto-attack file was omitted during manufacture.

We apologize for this. It was meant to be in game, but it is not currently in the console versions. We are working on how best to distribute this to console users. When we have information, we will let everyone know.

Real classy, tell everyone after the pre-orders are paid for and cancelling means having to send stuff back by post. I've never been more glad that I chose to not pre-order than at this moment.

Modifié par BobSmith101, 07 mars 2011 - 11:32 .

[ErebUs890]

OMG I have to press buttons! Game must be crap!!!

[Johnny Shepard]

This was bad news. I hope you'll be able to fix it.

[djackson75]

ErebUs890 wrote...

OMG I have to press buttons! Game must be crap!!!

No dude... It's more like "OMG a feature they prominently said would be in the game isn't, and they misled everyone for a month"... 

Modifié par djackson75, 07 mars 2011 - 11:36 .

[MonkeyLungs]

ErebUs890 wrote...

OMG I have to press buttons! Game must be crap!!!

That's way off the mark and makes no sense.

[Mulsanne Blue]

Who cares? It really isn't that big of a deal.

[Dragoonlordz]

ishmaeltheforsaken wrote...

TJPags wrote...

Well, you say it must be a false assertion, then you explain that it is, in fact, a false assertion.

Let me say this:  If you and I are negotiating over something, and I tell you something is true, then find out it is not true, yet never correct the impession I gave until AFTER we sign the contract, thus making it too late for you to back out, I have, in fact and in law, lied.

It's catorgorized as a lie, same as if I told it to you right before you signed.

Not by Sylvius's definition. Whether it's "as bad" as lying is irrelevant to this particular discussion. I think it is as bad, but it's still not a lie. And nothing you've said goes toward proving that withholding information involves making a "false assertion." This is because that's objectively false. You can't assert anything with silence.

It's a lie... Stop saying it isn't when it clearly is. They have stated that auto-attack will be an option available to console gamers in the options menu of DA2, this turned out to not be true which makes it a lie regardless of intentions good or bad or mistakes. One thing was said but the opposite happened aka a lie.

ErebUs890 wrote...

OMG I have to press buttons! Game must be crap!!!

Well when I go into a Ferrari dealership, I go in to buy a Ferrari and love driving out in a Ford... 

On a more positive note I imagine they will get this sorted fast because this thread and others like it will keep popping up making their lives annoying having to suffer like we will regarding sore fingers from all the clicking delete or lock every 5 seconds as we will have to do clicking attack a few times every second.
 

Modifié par Dragoonlordz, 07 mars 2011 - 11:44 .

[Moaradin]

djackson75 wrote...

Moaradin wrote...

I feel sorry for console players. Not because of the no auto attack, but because you have a console.


I only kid. I hope there is a fix soon. The game isn't out globally yet so you cant really complain until your actually playing it and its not there.

The game isn't out. You cant complain about a feature missing from the game if it isn't out yet. If they can release a small patch right away, it will be no big deal. If it takes a week after release, then it will be a problem. 



"you can't complain now, but you can complain 5.5 hours from now if you're on the east coast in America."

K.

[SorrowAndJoy7]

Chris Priestly wrote...

OK: Here is the story.

Auto-attack option for consoles was added in to the games late in the development cycle after the initial certification build was sent. The auto-attack functionality was sent to be added to the game for testing and approval. This was why staff said it was in game.

Due to an error during mastering, the auto-attack file was omitted during manufacture.

We apologize for this. It was meant to be in game, but it is not currently in the console versions. We are working on how best to distribute this to console users. When we have information, we will let everyone know.

THIS IS MY NIGHTMARE!!!
But seriously, that information best be when it's coming out and hopefully soon... I don't want any well we tried b.s. We were told multiple times it would be a part of the game and this is the best Bioware could do in regards to informing us that it's not? Rude... Don't get me wrong, I LOVE Bioware, but this should be a news and announcements post at the very least. Deceiving buyers even if unintentionally is an announcement worthy piece of info that an honest company would do their best to get out.

P.s. i'm so glad I went out of my way to calm many peoples fears that it was part of the game after they played the demo only to look like an ass clown now <_<

Modifié par SorrowAndJoy7, 07 mars 2011 - 11:40 .

[Bobad]

I can just about live with this for the moment.

However it makes me wonder what kind of testing the game went through (recalls FO:NV 360 save bug) If this matter slipped through what awful bugs might we encounter?.

[GulfWarVet]

MS is quicker than Sony at certification of patches, especially in SCEE land. Minimum at least a month if not longer, thats if they even bother, it was never intended to be in the game on consoles the way I read it.

They had a good three weeks to be working on a patch and to have let the console community know there was an issue and they were actively working on a fix ready for launch.

They Didn't.

To come out know ONLY after retail version have been sold is down right disgraceful and disrespectful to their so called "new" customer base they were aiming for, oh wait the customer base they wanted didn't need auto attack as they weren't RPG players but COD players who only press R1!! LMAO

Origins was my first Bioware game, DA2 will be my last.

I haven't seen anything from this DEV that trumpets so called dev of the decade titles the fanboys throw around willy nilly.

Hell they couldn't even unlock the saves on the PS3 after 2 years of being asked!!

Looks like they dumbed themselves down on the console side as well as the game.

If they want to throw away their creativity for a fast buck thats down to them, but no more of my bucks will be filling the coffers.

6 P's of business BIOware try and learn them.

Prior Preparation and Planning Prevents Pisspoor Performance.

You failed Epically.

[AkiKishi]

djackson75 wrote...

No dude... It's more like "OMG a feature they prominently said would be in the game isn't, and they misled everyone for a month"... 

Has this made the rounds to other game sites yet?

If it was that big a deal why just set x to repeat it's input when you held it down, that's better than mashing the thing.

Modifié par BobSmith101, 07 mars 2011 - 11:40 .

[Cless Godhard]

I wonder why OXM did not mention this in their reviews?

[Purple People Eater]

ErebUs890 wrote...

OMG I have to press buttons! Game must be crap!!!

Yeah, lets not to pass this one off as just fans over reacting. I cant stand trolls who **** and complain about minor things either, but this is NOT MINOR. This is basically taking the fundamental gameplay that defines Dragon Age, and devolving it into a mechanic made for simpletons. Console owners will never be able to play on Nightmare mode with any kind of long term success without auto-attack.

Modifié par Purple People Eater, 07 mars 2011 - 11:43 .

[SaltyWound]

Really, really disappointed in Bioware right now. I wasn't going to use AA myself, at least not on my 1st playthrough, but I knew others that did want/need it. Feel particulary bad for people who've left the forums and won't know this until they play the game.

[mesmerizedish]

Dragoonlordz wrote...

It's a lie... Stop saying it isn't when it clearly is. They have stated that auto-attack will be an option available to console gamers in the options menu of DA2, this turned out to not be true which makes it a lie regardless of intentions good or bad or mistakes. One thing was said but the opposite happened aka a lie.

I'm not excusing BioWare's actions or response to this development. I'm not saying, "They didn't lie, it's okay everyone!" As I said before, the argument is purely semantic. Whether it's a lie or not, it's unacceptable.

That said, since you insist on continuing the semantic debate, your definition of a lie is objectively false. Intent is paramount to whether something is a lie or not. If they believed what they said, then it's a mistake. They were wrong, not disingenuous.

Aside from that, we're not talking about whether or not they lied when they said auto-attack was in the game. What we were discussing is if, after realizing that it wasn't and neglecting to inform us of that fact, their decision to withhold that information was a lie. Again, it is not. It is as bad as lying, but it is not lying. You cannot "lie by ommission," to use the idiom. To lie, you need to state a falsehood with the knowledge that it's false. That's a lie. Not stating the truth is just being a dick.

[Marionetten]

Cless Godhard wrote...

I wonder why OXM did not mention this in their reviews?

Because publishers more or less dictate reviews nowadays?