21 réponses à ce sujet

[TM13h]

I have a savegame just before the major decision in Awakening and stopped playing because I read about a new patch dealing with Sigrun's Joining. Now, after patching to 1.04, I still cannot complete the quest. When I talk to Varel he will only let me chose to progress the main quest or do some other stuff beforehand but no option to complete Sigrun's joining ritual.

[flagondotcom]

From everything I've seen:

1. Most of the "quest bugs" fixes appear to require starting a new game, or backing up to a point before the bug triggers.

2. The Sigrun-related fix (if there is one) is for her companion quest, not for the Joining. (Note that the companion quest for Sigrun's roguish past that can't be completed if Law and Order is started *might* actually have been functioning as designed in 1.03.

3. The canonical fix for "can't do the last joining" is to either do Justice last or to take any other party NPC early--which breaks immersion, but has been working for quite a while. There's really not much other reason that just before the end of Kal'Sharok there's a door directly to the outside...

[TM13h]

I haven't tried out Sigrun's other quest yet. Just installed the patch to see if the joining now works for her which it doesn't.



Funny thing is I did Justice last but without knowing that you have to backtrack to the Keep before completing that part else the joining cannot be completed. Shortcuts at the end of a "level" are not unusual and I doubt that this was put there just so players can go back and do quests that are not completable later on.

[TM13h]

Well, turns out her other personal quest in Amarthine is also still not available, just like with 1.03. I honestly do not know what BW tried to achieve with 1.04 but apparently it does not work for me.

[Funkjoker]

*sigh*

flagondotcom wrote...

From everything I've seen:
1. Most of the "quest bugs" fixes appear to require starting a new game, or backing up to a point before the bug

[Unrefined-Nemesis]

Start a new game it fixes everything, don't worry Awakening is a 8 hour campaign at most, getting back at where you last stop should take about a 1-3 hours tops.

[Quirken]

TM13h wrote...

Well, turns out her other personal quest in
Amarthine is also still not available, just like with 1.03. I honestly
do not know what BW tried to achieve with 1.04 but apparently it does
not work for me.

Yup.

Jean-Funk Van Damme wrote...

*sigh*

flagondotcom wrote...

From everything I've seen:
1. Most of the "quest bugs" fixes appear to require starting a new game, or backing up to a point before the bug

That's not good enough, Bioware. It should be a matter of finding the flag in the savedata that causes the NPC to not show up, and changing it from TRUE to FALSE.

I'm not gonna replay the whole game just to get back here. That's stupid.

Patch it right. Or release the data for the toolset so WE can do it for you.

Unrefined-Nemesis wrote...

Start a new game it fixes
everything, don't worry Awakening is a 8 hour campaign at most, getting
back at where you last stop should take about a 1-3 hours tops.

I'm 13 hours in, so I don't think "8 hour campaign" is right. Yeah, if you plow through it, it is. I was taking my time, enjoying myself, until I came across this bug, and stopped.

Bioware needs to fix this.

Modifié par Quirken, 20 juillet 2010 - 09:49 .

[Nathan Willis]

Hello Quirken, sorry for the inconvenience but unfortunately the nature of the fix is such that for many personal quest and approval-related issues, indeed a new game will be necessary to see results. Copy-pasted from the FAQ we recently posted in the announcements:



"While we have fixed the party member approval/personal quest issues, it is important to note that players may not experience the results of this fix until starting a new game.



Because of the nature of the bug and the fix implemented, while it is possible that it will still affect party members that are not yet in the player’s group, in general existing game saves may still not see proper approval results."



Apologies for the inconvenience once again. For my part, I'll try and get some permissions so I can sticky the FAQ posted earlier.

[searanox]

Quirken wrote...

That's not good enough, Bioware. It should be a matter of finding the flag in the savedata that causes the NPC to not show up, and changing it from TRUE to FALSE.

I'm not gonna replay the whole game just to get back here. That's stupid.

BioWare have said that they aren't allowed to change certain parts of the game code.  Why?  I'm really not sure, but it's likely for stability reasons or because the amount of testing required after such changes would be too extensive.  My guess is that they are able to make certain fixes to the game engine, but not others, and it's possible that changing save files also isn't viable - especially because it may be quite hard to figure out why that TRUE or FALSE variable is set that way in the first place (if it even is a simple binary variable).

Modifié par searanox, 20 juillet 2010 - 10:07 .

[TM13h]

Nathan Willis wrote...
"While we have fixed the party member approval/personal quest issues, it is important to note that players may not experience the results of this fix until starting a new game.

Because of the nature of the bug and the fix implemented, while it is possible that it will still affect party members that are not yet in the player’s group, in general existing game saves may still not see proper approval results."

That's from Victor's posting which I only read after having the trouble explained above. It might be a good idea to put all of these known issues into the actual patch notes and not hide them away in a locked and soon to be forgotten topic somewhere in these forums; as it is like now, the part about having fixed the personal quests in the patch notes is misleading.

P.S.:
@Unrefined-Nemesis:
I am right at the part where you have to make that major decision, with 25 hours registered game time. How can you, even if you skip all the dialogue, reach that point in 1-3 hours? As it turns out I have to chose between replaying at least a dozen hours for two tiny quests (at least I think they are nothing big) or just carry on w/o solving Sigrun's personal matters. I think I'll do the latter... too much backlog with other games waiting :-).

Modifié par TM13h, 21 juillet 2010 - 09:32 .

[dan107]

Is there a mod or something that fixes this? Considering all the other things that modders have done, this one seems pretty minor.

[TM13h]

To my knowledge there is no such mod, at least not at dragonagenexus, and sadly there does not seem to be an option to fix this with runscript or something like that, like with Velanna's quest that did not trigger for me, too.

[Quirken]

Nathan Willis wrote...

Hello Quirken, sorry for the inconvenience but unfortunately the nature of the fix is such that for many personal quest and approval-related issues, indeed a new game will be necessary to see results. Copy-pasted from the FAQ we recently posted in the announcements:

"While we have fixed the party member approval/personal quest issues, it is important to note that players may not experience the results of this fix until starting a new game.

Because of the nature of the bug and the fix implemented, while it is possible that it will still affect party members that are not yet in the player’s group, in general existing game saves may still not see proper approval results."

Apologies for the inconvenience once again. For my part, I'll try and get some permissions so I can sticky the FAQ posted earlier.

I appreciate the response, and I understand that this is Bioware's current position, but it doesn't address the problem.

When an auto manufacturer screws up, they order a recall to ensure all the old vehicles with problems are off the street. What Bioware has done is fix the problem so that new "cars" are fine, and tell all the people with the broken "cars" they can get a new car if they want to put a lot of effort into it.

I've been programming for about 10 years now. I've worked with game engines in the past (both the Half-Life and source engines). I might not have access to Dragon Age's source code, but I know how to program and it's not hard to imagine what caused the problem in the first place. I've seen very similar bugs (quickly patched by the community, by the way) in Morrowind and Oblivion.

To sum that up: I know this would be easy to fix. Even if it's not simply a binary variable (there could be multiple variables related), Bioware could easily put together a hack-ish fix. Here's a few solutions:

• Force the NPC to spawn. 
• Give us a console command to initiate the dialogue.
• Create a new quest otherwise identical to the old one, with different triggers.
• Give us a console command to reset all quest variables related to the bug. We might have to do a small amount of backtracking, re-recruit Sigrun or something, but at least we wouldn't have to start from scratch

Sure, those aren't elegant solutions. They're kinda sloppy. But any of them would solve the problem.

If Bioware would release the Awakening info for the toolset, people would probably have patched this months ago.

[Time4Tiddy]

It's been reported on the announcement thread for 1.04 that people have started a fresh Awakening and Sigrun's quest NPC is still not spawning if you've done Law & Order/Smuggler's Run. Is there any confirmation if this quest was or was not fixed in the patch? I'd rather just be told it wasn't addressed than wondering. The patch notes say fixed problems with companion approvals and quests, but doesn't specify.

EDIT:  I'd like some resolution to this, as I started my "canon" PC again through Awakening trying to get a final save game to have on hand for DA2.  I didn't get Sigrun's quest the first time through, so I would like to make sure I don't lock myself out again before I get too far.

Modifié par Time4Tiddy, 23 juillet 2010 - 06:06 .

[Eskarne]

Started a new one with 1.04, still bugged here.

[ICek81]

It isnt working even on new game started after update to 1.04.

[Funker Shepard]

ICek81 wrote...

It isnt working even on new game started after update to 1.04.

Yep, same here. New game started under 1.04, quest not firing off. Of course, it wasn't on the changelog either (just as shaperate's blessing etc:) weren't, so not really surprised. Just disappointed.

[FrankGeus]

Hmmm ... here too. Started a new game after patching to 1.04 (which solved the crashes to desktop for me ... so basically I'm happy).



But ... Sigrun's quest npc needed for starting her personal quest is still missing (after I started "Law and Order").



I hoped that this bug was solved due to the release notes: "Fixed a variety of bugs related to party members' approval and personal quests not triggering. ", but indeed it doesn't specifically say that Sigrun's quest was fixed.



Anyways ... if you start a new game ... make sure that you wander through Amarantine with Sigrun before picking up "Law and Order" !

[Lycans4ever]

TM13h wrote...

I have a savegame just before the major decision in Awakening and stopped playing because I read about a new patch dealing with Sigrun's Joining. Now, after patching to 1.04, I still cannot complete the quest. When I talk to Varel he will only let me chose to progress the main quest or do some other stuff beforehand but no option to complete Sigrun's joining ritual.

This is because Blackmarsh is "suposed" to be the final place you have to go and not any other cause of that bug. A possible workaround for this is to recruit Sigrun, proceed through the ruins of Kal'Hirol until the end of the Trade Quarter, take the exit as opposed to the stairs to the lower levels, return to Vigil's Keep and have Sigrun undergo the Joining, before returning to finish Kal'Hirol - Lower Reaches. If you have a save that will allow you to follow those instructions then you are lucky. If not......

[flagondotcom]

Just since this has now been bumped back up near the top, I'll note that there *is* now a mod to fix the issue with Law and Order causing the starter NPC for Sigrun's Roguish Past to never appear.



http://social.biowar...m/project/3129/



*That* fix does not require starting a new game, and was never included in 1.04 although it was implied that it might have been.



The other separate issue, that the last recruited party NPC can only go through the Joining with some immersion-breaking meta-gaming (take them to the Seneschal before they ask) has not been addressed and the only workaround remains meta-gaming to my knowledge.

[coolkyote]

Yep, yet another POORLY tested part of this expansion. Having to start a new game is completely unacceptable. Who the hell does the testing Stevie FRICKING Wonder?!??? Yeah, only 8 hours to re-do from scratch if you don't care about FINISHING it.

[Funkjoker]

^ This quest wasn't fixed in 1.04. So it doesn't matter if you restart your game. However, you can manually "fix" this quest. See the wiki entry.