Posts made by Hydro666
@ubi-spud Yeah that is not ideal since I have progressed down other quest lines since encountering this bug and I would lose a lot of progress by doing that.
Could we get an ETA on when the fix will be rolled out? This way I can decide whether it makes more sense to wait for the fix or just bite the bullet and revert to a very old save if need be.
@Ubi-Spud, for what it's worth I have an idea as to what the root cause is:
When selecting a person to accuse for the first time from the dialog tree, the selection color of the text will transition from white to grey, indicating that you already explored that option. My theory is that the person Soma accuses of being a traitor is the most recent person whose dialog tree option transitioned from white to grey as @jebabiah also suggests.
When I was first choosing people to accuse, I first selected Galinn (since it seemed like it was obviously him) so then when Soma asked me to confirm, I said that I needed to think about it more (since I thought that maybe the true traitor would have painted Galinn's boat yellow to throw me off). So I then picked Lif, and then Brina just to see what the dialog would sound like, but then I decided that it must have been Galinn.
Brina was the last choice I picked before all the other options were greyed out, and now she is the only one being consistently killed (since every other characters dialog option is also greyed out).
Also @Ubi-Woofer is there any way we could get this issue tracked in the megathread as well: https://discussions.ubisoft.com/topic/81608/reported-issue-megathreads-please-check-here-if-a-thread-exists-for-your-issue
Followup, I have tried the following steps to remedy this issue but Briana is still killed even after selecting Galinn:
- Fast Traveling away and back and talking to Soma.
- Fast Traveling to Norway and back and talking to Soma.
- Quitting to desktop and reloading and talking to Soma.
Of all of these attempts, Soma still kills Brina after selecting Galinn as the one I would like to accuse. @Ubi-Spud are there any other steps I should be doing to try to remedy this issue?