Larian Banner: Baldur's Gate Patch 9
Previous Thread
Next Thread
Print Thread
Joined: Dec 2025
J
stranger
OP Offline
stranger
J
Joined: Dec 2025
Hi everyone,
I’m encountering a bug I never had before Patch 8 while saving Counselor Florrick at Waukeen’s Rest in Act 1.

I can break the doors without any issue, and Florrick starts running toward the exit normally. She heads to the same main entrance we came in through. However, once we reach the entrance, the cutscene never triggers. Instead of saying something like “Some fresh air, at least…”, she just stands there behind her guards.

When I try to talk to her, she keeps saying:

“We can talk when you’ll get me out of here.”

The game still considers her as if she’s trapped inside the building.

If I fast travel and come back, the game acts as if I never saved her and she’s burned to death. Long resting does the same thing. (Going to camp and coming back without resting works, but doesn’t fix the issue.)

Extra details:

I have Wyll in my party

I used Wyll to break the first door

No mods installed

⚠️ Additional odd behavior:
If I try talking to Wyll while Florrick is stuck in this state, he behaves as if the rescue cutscene already happened and as if we already spoke to Florrick(he is giving detail that you learn durring this cutscene) even though the cutscene never triggered and Florrick herself still thinks she’s trapped.

Things I’ve tried so far:

Reloading a save from before approaching the inn and doing the whole sequence again → same issue

Blocking the guards so they wouldn’t interfere with pathfinding (thinking they might block her trigger point) → same issue

Exiting through the left side building (where you rescue the trapped man) instead of the main entrance → she exits fine, but still says she’s not saved and no cutscene triggering.

Exiting through the right side building (by moving the huge barrel aside and jumping first floor where you get a cutscene to break the door) instead of the main entrance → she exits fine, but still says she’s not saved and no cutscene triggering.

Trying all of the above with different party compositions (full party, solo, only Wyll) → same result every time

No matter what I do, I cannot trigger the “Florrick is saved” cutscene.

I couldn’t find anyone online with this exact issue. Most posts about bugs in this sequence are pre patch 8 and mention her being stuck upstairs not moving, but that’s not the case here.

Has anyone else encountered this bug since Patch 8, or found a workaround?

Joined: Apr 2022
Location: Germany
old hand
Offline
old hand
Joined: Apr 2022
Location: Germany
I actually had the same problem once, but an older reload helped. You may also need to verify the game files first and then reload a save game where you hadn't entered Waukeen's Rest at all. Annoying, I know.

Joined: Dec 2025
J
stranger
OP Offline
stranger
J
Joined: Dec 2025
ok that reassuring to know that i am not the only one haha !! i already tried a save before approaching the in ... i will tried with an even older one (if i can find one ) after checking the file on steam thank you

Joined: Oct 2020
old hand
Online Content
old hand
Joined: Oct 2020
I remember a weird thing with Florrick's cutscene. Not exactly the same as what you describe, but similar. Maybe this could lead to a solution.

I sent Karlach in the burning house alone. There's no need to send the entire team inthere. Karlach is fire resistant and strong enough to break down the door. So Florrick is freed, runs toward the exit, I follow behind with Karlach, and then before momma K can exit, the cutscene starts. But it doesn't really finish because my selection is still on Karlach who is still inside. Going back to Karlach and leading her out then continued the cutscene normally.

If this happens, check if all party members are outside or if maybe some are still inside the house.

There was a similar problem in the barn in Rivington, when you're inside and the guard wants to take you to Nestor. You can't get to Nestor and remain stuck unless all the characters are in the right place.

It's a bug, but there was a way out by switching between the party members and trying to regroup.


Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.5