3 réponses à ce sujet

[Alius_Neo]

In my DA:Awakenings game I had fully upgraded Vigils Keep, saved Amaranthine and Nathaniel was the one to lead the fight at the Keep. But for some reason because I left Nathaniel at the Keep DA2 wont register the Find Nathaniel guest, which loads on my brothers ame bcz he had Nathaniel with him when he went for the Mother. In my game Fools Gold was activated in A2 instead.

[myaari]

I've been thinking about this, since I'm in the same shoes. Like you, I left Nathaniel behind at the keep, along with Anders (who survived) and Justice (who got his head cut off). And like you, I can't get Nathaniel to appear in DA2. What occurred to me is that when you save Amaranthine, even if Vigil's Keep is fully upgraded, the Codex in Awakening states that each character left behind to defend the Vigil dies - and you don't find out until the epilogue that they are actually alive.

Now, of course, Awakening is so glitchy that it makes DA2 look well-scrubbed, but I always gave it the benefit of the doubt in this instance and assumed that the reports of your characters' deaths were intentional, and you were supposed to believe that they had died until the epilogue dramatically reveals otherwise. Now I'm thinking it's a bug - despite what happens in the epilogue, saving Amaranthine permanently sets the flags of the Vigil's Keep defenders, whoever they may be and however upgraded the Keep itself may be, to "Dead," and that's what carries over into DA2 (note also that Awakening has no post-epilogue save). If keeping Nathaniel in your party in the endgame of Awakening *does* unlock his quest in DA2, as apparently it did for your brother, then that adds further credence to the notion that, no matter what happens in the Awakening's epilogue, anybody left behind to defend the Keep is flagged "Dead."

If this is the case, given that the source of the bug is Awakening itself which was never really patched and at this point never will be, I wonder if we can ever expect to see a fix for this in DA2. I guess all anyone can really do is replay Awakening and make sure any DA2-relevant characters are in your party if you choose to save Amaranthine rather than the Keep. Kind of sucks, though, that whoever gets left behind will be dead through all future DA games.

[JunMadine]

You know I like Dragon Age but the Mass Effect team is MUCH better at dealing with bugs and glitches. Why? I am not sure they are the same company. Perhaps they could learn from ME guys. 

 To be fair I am really frustrated with this bug and awakening.  But I will retract the above comment for now until I see the patch that is on the way.

Modifié par JunMadine, 26 mars 2011 - 11:19 .

[myaari]

JunMadine wrote...

You know I like Dragon Age but the Mass Effect team is MUCH better at dealing with bugs and glitches. Why? I am not sure they are the same company. Perhaps they could learn from ME guys.

ME1 could be a bit glitchy...I think a lot of the relative smoothness of save imports into ME2 (though it wasn't perfect) could be chalked up not to differences in skill level between the dev teams, but rather differences in the complexity of the process and in the sheer number of plot flags being transfered.

ME1 was a 35-hour-or-so game if you did absolutely everything, whereas DAO was about twice that - with the addition of a 20+-hour expansion and several other plot-relevant DLCs. DA has more plot quests and sidequests, more characters, and more variables. ME1 saves were transfered only once, directly into ME2 - and many of the plot details that transfered from ME1 only wound up resulting in an e-mail on the Normandy in ME2, which can't be the world's hardest coding job. Also, a lot of people are using saves in DA2 that were transfered three times prior (into Awakening, Golems and Witch Hunt) before being transfered into DA2. It seems inevitable (if frustrating!) that as you compound both the number of plot variables and save transfers between DLCs and games, more and more import glitches arise. Unfortunately, that also makes them harder to fix, no doubt - especially since it's highly unlikely anyone will go back to DAO, Awakening and the other DLCs and fix bugs that may be causing import problems in DA2 that aren't DA2's "fault," so to speak.

We should all probably try to be sympathetic to the fact that BioWare is doing something both innovative and inherently complicated with this save import feature - although that doesn't mean nobody should point out that there's plenty of room for improvement. It does seem in a way that, whether because of time constraints, insufficient testing or the mere complexity of the process, the DA2 team may have bit off a bitten more than it could chew with the imports - but I suppose one should reserve final judgment until these issues see a patch (if indeed they do - there's plenty of reason to expect that many non-game breaking issues, which would include imports, will never be fixed). It does make me worry a bit about Mass Effect 3, though...