From what I've been reading there is NO auto-attack option in Console DA2?
#426
Posté 08 mars 2011 - 10:40
#427
Posté 08 mars 2011 - 10:41
sassperella wrote...
It took a year for them to fix the save corruption bug on the xbox 360 on origins. That lost people hundreds of hours of gametime and was a game breaker. Do you honestly think this will be patched any time soon?
Yes, because this is fairly minor alteration to a script. A few lines of code that tell your character "Hit that dude". Besides, which: the feature's already been implemented. They just need Sony and MS to give them the go ahead to replace a single file.
In any case, the issue with save corruption was much more complicated because it was down to built-in limitations with the merchants, and NONE of that is accessible via dascript. The "merchant_core" script is actually empty. Doesn't do a thing. That was all handled at a much lower level by the engine itself, and they also had to deal with not breaking all the non-corrupted saves with any fix. And then there's the fact that literally every shop you've ever visited in the game's entire inventory is recorded in every single save file. IOW, not trivial.
Not that I think it should have taken as long as it eventually did, but then again, I don't know how complex and/or brittle that part of the engine code was.
Modifié par didymos1120, 08 mars 2011 - 10:43 .
#428
Posté 08 mars 2011 - 10:50
OMG MY STORY IS RUINED!!!
Yeah thats it...I hope
#429
Posté 08 mars 2011 - 11:01
So there was a mistake with both?
#430
Posté 08 mars 2011 - 11:03
I think there was a small debate about that Dorian and I agree. They made the atmosphere, the core or background or ambiance, the baseline of what Dragon Age was. The foundation. It seems they took that and modified it too much where the atmosphere, the ambiance and game play changed too much. Especially going for the frenzy combat to get more sales. I side with you and the group that disagreed with their choices. I'm sure since they are talking franchise there will be more coming. A better goal would have been to make the changes gradually over a couple more releases instead of all in one. Alienates one large group of avid supporters/customers but bought the game from trust and reputation. That, of course, has fallen considerably as these two (so far) blunders have arisen.Dorian the Monk of Sune wrote...
DA Trap Star wrote...
why would they think that no auto attack was a better option, I'm sure they have game testers. I'm sure most of them have thumb injuries from the constant button pressing to attack.
My thumb just hurts from the thought of that Ogre fight in the demo...
The same reason they are surprised peoplequit without achievements like achievements are a big deal. They are out of touch. Its true that a lot people dont like single player stat based combat and thats how DA:O started but wake up Bioware its still single player stat based combat. They should be focusing on the strategic elements that can exisist. You cant make an action RPG out of it.
I have faith though that they will fix their mistakes and most importantly learn from them so future releases in the franchise will repair the damage this one has done.
#431
Posté 08 mars 2011 - 11:04
#432
Posté 08 mars 2011 - 11:09
Bongani wrote...
Wouldn't the Xbox and PS3 versions have differing mastering processes / different game files?
So there was a mistake with both?
Yes both were sent to master, both apparently didn't make it onto their respective master.
#433
Posté 08 mars 2011 - 11:50
Mousers wrote...
Almost looks like they are using the same import code that was broken for Awakenings and WH.. to save time, and it was the wrong code, not the fixed code. And simple code if they are using a database structure. Extract, import, test. 15 min done. Also since it is basic and simple it is also easy to miss a type-o. Hint to coders... read it backwards to double check and test, test, test. Coders just aren't suppose to release code that is sloppy or inefficient. So to my list above I guess we can also add Human Resources. If they have a file naming convention, a file revision log and procedures they enforce they won't be putting out of date code into a new product. First time with Awakenings a mistake, second time with WH incompetance, third time with DA2 unemployment line.
Don't get me wrong though with my posts, I'm not slamming BW, they just seem to have internal procedural issues. And I'm not excusing them for their mistakes, they should know better because they have shown us in the past that they can.
The problem is, some of the import flags they use are buggy (mage boon, well, all boons except the dalish boon and one of the dwarven ones, for instance do not get set if Alistair grants it in DAO, and is not the only one), and others are most likely inappropriate (romance active instead of in love or still in love for instance, which messed up epilogues in Awakening). At the very least, the import process HAS to have bugs -- and bugs that are from Origins.
It makes sense that both console versions don't have the autoattack IF the wrong file was sent to be mastered. My main problem with the situation is that BW didn't tell people until it was too late to cancel their order and in fact, avoided telling people in an interview. They most likely wouldn't have lost many sales over this, especially if they assured people they were working on a patch.
Modifié par ejoslin, 08 mars 2011 - 12:26 .
#434
Posté 08 mars 2011 - 11:53
#435
Posté 08 mars 2011 - 11:53
Mousers wrote...
BobSmith you made a very good point I hadn't thought of. If they did as Chris said, sent the AA code to master that means it was final for release, which means it should be in the manual. But then, since it was a late addition they could say the code went to master but the manuals were already printed so didn't make it there. But if that is the case they could add 1 sheet loose insert stating... because of popular demand we added AAso yeah, it should be there. I'll be sure to check mine when I get it in the mail.
I just read over the PSM3 review and there is no mention of autoattack. But if it's not in the manual, then are definately lying about how long they were aware of it.
#436
Posté 08 mars 2011 - 11:56
I've tried to keep Fable 3 out of my mind through the buildup to the release. But playing the game it's getting pretty difficult to keep the similarities out of my head. And they're not favorable.
I trust BW, I've been with them for a while. I enjoyed ME2 (though only 3 will determine whether we're looking at a Empire Strikes Back shift or the first steps on a declining slope), and I'm restraining my hurt at Kotor 3 being a MMO. But they really need to get their act together. The weird thing is I've known them always seeing the forest despite the trees - DA:O was an amazing game despite some issues I think a lot of people might see obvious answers to (like the fact that if you didn't keep up with your Codex every time it updated you'd probably never really know what was added). But in both this game and ME:2 they've taken the opposite approach - listening too much to individual critiques of the game at the expense of the overall product. The clips in ME:2 are a great example: they certainly answered some of the issues people had with the first game, but at a pretty egregious violation of world lore and basic logic (not to mention the fact that it wasn't even implemented that well).
Having said that, I still trust BW. I just hope that this is the wake-up call that they needed, and that this community response actually gets back to the people in power.....and that they don't draw the conclusion that AA needs to be included on every subsequent game they make.
#437
Posté 08 mars 2011 - 11:57
#438
Posté 08 mars 2011 - 11:58
I feel guilty that I misled my friend and essentially shilled for Bioware in furthering the false claims about the auto-attack feature. I will be picking up my Signature Edition in a few short hours, but I won't be opening it unfortunately. Until Bioware re-assures me that this issue will be resolved in a timely manner, it will remain in its un-opened box, ready to be returned. I will apologize to my friend and suggest he do the same.
#439
Posté 08 mars 2011 - 12:03
Bongani wrote...
Wouldn't the Xbox and PS3 versions have differing mastering processes / different game files?
So there was a mistake with both?
The fix in question is probably in a header script. That's how DAO implemented it. They then recompile all the other scripts including it, and stuff 'em all into an ERF (I assume they're still using the format anyway), and that would be the actual file that got left out. But since that's all scripting stuff, compiled into a bytecode format created by Bioware, it's platform agnostic. There aren't any actual executables involved that have to conform to a specific ABI. It's just data the game engine reads and interprets. So no, almost certainly not different game files in this case.
#440
Posté 08 mars 2011 - 12:08
FulfilledDeer wrote...
(though only 3 will determine whether we're looking at a Empire Strikes Back shift or the first steps on a declining slope)
OK, wait: are you saying tESB was somehow the herald of the lesser Ewok-ridden RotJ and the very much lesser-than-that prequels, or that you actually think the SW films got better after tESB? I iz confused.
#441
Posté 08 mars 2011 - 12:14
If anyone wants to know, I have been taking my medicine with a little alcoholic. And when I mean little, I mean a lot. HAHA! HEHE! HOHO!!!
#442
Posté 08 mars 2011 - 12:15
#443
Posté 08 mars 2011 - 12:16
Rawgrim wrote...
They were aware of it all along. One of the developers said flat out tha auto attack was in the game, and we shouldn`t worry about it. This was 2 months ago. They have also avoided questions about auto attack since then.
Conspiracy mongering. The explanation given is rather straighforward: they said it was in the game 'cause it was supposed to be. Someone screwed up, and the requisite file got left off the discs. And they didn't keep talking about because, well, what the hell else was there to say other than "We're putting it in"? Should they have had daily press conferences to say "Yep. Still in. See ya tomorrow guys!" ? Do they continually answer any of the other bajillion continually-asked questions? No. They don't. Your evidence isn't.
Modifié par didymos1120, 08 mars 2011 - 12:17 .
#444
Posté 08 mars 2011 - 12:20
Rawgrim wrote...
They were aware of it all along. One of the developers said flat out tha auto attack was in the game, and we shouldn`t worry about it. This was 2 months ago. They have also avoided questions about auto attack since then.
Very suspicsious they only replied once it was too late for people to cancel without the hassle of having to send stuff back.
#445
Posté 08 mars 2011 - 12:20
I can't get my hands on my pre-ordered Signature Edition for another two-and-a-half hours, and the excitement I had about playing on release day has already disappeared since I won't be opening it because I don't want to ruin what I expected would be my favorite game of the year. I sincerely hope the auto-attack bug is patched immediately.
#446
Posté 08 mars 2011 - 01:29
#447
Posté 08 mars 2011 - 01:33
lawrence_sp wrote...
Well this is very disappointing, not only is the auto attack is missing, but from other topics it looks like there are a lot of bugs and glitches in the game...
There will always be bugs and glitches. This is quite different , both in how it effects the game and how we were misled about it.
#448
Posté 08 mars 2011 - 01:45
#449
Posté 08 mars 2011 - 01:51
#450
Posté 08 mars 2011 - 01:54
Modifié par Dragoonlordz, 08 mars 2011 - 01:56 .





Retour en haut




