-
Locked SOLVED [RESOLVED] Unable to progress with "A Brewing Storm" after waking up | POST HERE
47 Likes/1386 Replies/59875 Views
Hello all!
Following my previous update, I would like to share the patch notes for TU 1.2.1 with you all. This update will deployed 27 April, 2021 at 1 PM CEST / 8 AM ET.
If you are still encountering issues with "A Brewing Storm" following TU 1.2.1, please don't hesitate to update this thread so we can take a closer look. Please include a video that shows the following:- You have TU 1.2.1. installed. You can view this information in the opening game menu in the bottom right-hand corner.
- You are still unable to start the fight with Dag
We can then pass this along to the development team for further investigation.
@EpicAar - Thank you for sharing your feedback with us regarding the Dev Blog. I'm afraid we would be unable to speculate on the development process, or on what caused this issue to happen in-game. If we have any more information to share regarding future developer posts, we'll be sure to let you all know within the forums. Rest assured that the development team intends to fix all instances of this issue with TU 1.2.1. If the issue persists for players following the update, we will escalate this for further investigation.
Thanks all
Official ResponseThey/Them | If my answer helped you, give it a thumbs-up! | ubisoft.com/help | @UbisoftSupport | Currently Playing: Borderlands (PS5)
6 Replies
-
@ubi-borealis Let's hope it fixes the bug... otherwise, with all due respect, this will be Ubisoft's biggest failure... bigger than CD Projekt with CyberPunk 2077.
-
@ubi-borealis Thanks for the update, just to confirm, the patch will allow players to carry on from previous save files?
-
-
-
-
-
-
-
Hello, after waking up in A Brewing Storm no cutscene will be triggered and I'm basically stuck.
It appears this bug has been there for MONTHS, and it's a game-breaking bug, since I can't progress with the main story.
Is it any workaround/fix for this, or will I be unable to complete the game? This is frankly unacceptable.
Please let me know. -
Hello there!
@gg_Gatsby - We haven't been told that a new save file will be required, as this would have been shared in the patch notes. You should be able to continue from your current save file, based on the information that has been made available.
@h1ck0k - "A Brewing Storm" is due to be fixed today following the deployment of TU 1.2.1. This update will deployed 27 April, 2021 at 1 PM CEST / 8 AM ET.
Thanks! Official ResponseThey/Them | If my answer helped you, give it a thumbs-up! | ubisoft.com/help | @UbisoftSupport | Currently Playing: Borderlands (PS5)
1 Reply
-
-
@oracleoftruth
I don't, it should hopefully be here soon though. (Playing on PC in Canada)
Edit: Mine just started downloading -
-
@ubi-borealis It looks like nothing has changed.
Anyway I just uninstalled the game and I'm reinstalling it now. I'll keep you posted. -
Well this is strange. The save I had retained is gone - I'm back to 'A Bloody Welcome' in Cent (where you meet Fulke after she had killed the Abbot).
Hoofbeats glitch is fixed, thank goodness! Gunnar still threatening me though lol. I'll play through and see what happens... -
Thanks for your prompt updates, @h1ck0k & @FrustratedGamer!
If you're still unable to proceed with "A Brewing Storm," please don't hesitate to update us in this thread so we can investigate. Please include a video as well, as this will be useful for the development team.
Thanks!
Official ResponseThey/Them | If my answer helped you, give it a thumbs-up! | ubisoft.com/help | @UbisoftSupport | Currently Playing: Borderlands (PS5)
1 Reply
-
Downloaded the update and the cut scene triggered immediately. Will let you know how it plays out in the hour. I am at work so had to pause it until after this meeting.
-
It's fixed.
I restarted a month ago and successfully avoided the bug. I've still got the original save. Just loaded it after the update, finished the Cent arc and headed back to Ravensthorpe to trigger 'A Brewing Storm' ... Cut scene and duel loaded fine - no apparent glitches. All prior attempts from this save point before the latest update resulted in the bug.
Hopefully everyone else has the same outcome!
(I'm just glad to have the hoofbeat sounds back!)
Well, that's that then.
last edited by