From Larian Forums:

Hello everyone,

We’ve got a new hotfix for you today, addressing several bugs, visual issues and blockers.

Have you ever had a romance so intense, that everything melts away? Well, sometimes that isn’t intentional. We’ve fixed an issue where Gale’s romance scene was playing in what looked like some kind of black void. Consider the ambience restored.

We are aware of an issue with kissing animations for Astarion, and are currently working on a fix. We expect this to be released in a future update. Thank you for all your reports and messages, and thank you for playing Baldur’s Gate 3! If you have any bugs to report, please reach out to our support team.


FIXES
You can now use soaps encountered in savegames before Patch 4.
Fixed the game sometimes freezing indefinitely after a reaction to a spell that hits you with multiple projectiles.
Fixed a crash after using a reaction that causes an attack against a dead creature.
Fixed an issue causing you to get stuck in certain dialogues unable to continue.
Fixed a blocker that could occur when trying to Long Rest.
Dominated followers will now follow the party as expected after loading a savegame.
Fixed Gale's romance scene playing in what looks like a black void.
Fixed a Dark Urge flashback accidentally teleporting you to the Lower City.
The Cursed Skulls in Jannath's Estate are now vulnerable to Force and Radiant damage.
Fixed an issue that prevented certain characters from executing their behaviours.
Fixed citizens and refugees in Baldur's Gate sometimes jittering about the place or not using their proper animations.
Fixed some visual artefacts appearing at camp in relation to Dark Urge and Karlach dialogues. This also solved the bloodstain under suddenly becoming larger after loading a savegame.
Wyll and Minthara should now properly kiss a second time without the need to retrigger the dialogue.
Fixed an issue where a companion's camp night dialogue could be replaced by a different dialogue that couldn't trigger during a previous night.

Thank you for the reliable update notes of yours, dbartenstein!

Hey! Just a heads-up. Don't freak out.

The downloadable Hotfix #11 for GoG will be slightly mis-labeled IF I am reading this correctly, if they correct it before they release it then you can ignore my post.

So Steam/Larian Hotfix #11 (v4.1.1.3956130) will be the same as GoG release as v4.1.1.3956130 Patch Patch4_Hotfix3

Yes, thats right, they labeled it "3" instead of "2" so yeah.

Have a nice weekend everyone!

I have a question that has probably been asked before. Where do you look to see what version number the game is currently at?

Makes sense. Not a mislabel on Steam, though. When you launch the game, in the main menu bottom right.

And whenever you make a savegame/load a savegame it shows which version the savegame is made with.

No patch offline installer available yet, it looks like.

GOG is still due a fixed version of v4.1.1.3767641 Patch Patch3_Hotfix3 to v4.1.1.3882084 that doesn't require 1 TB of free space to apply anyway, is this still being figured out/worked on or what?

Hotfix 11 Breaks linux compatibility for a lot of folks regardless of distro or platform (GOG, Steam), so do NOT install this patch unless you enjoy trying workarounds.

Patch offline installer available now.

After Galaxy installed this patch, the game wouldn't launch from Galaxy anymore, because the launcher got broken.
It says "Unhandled exception. System.IO.FileNotFoundException: Could not load file or assembly 'CefSharp.Core.Runtime, Version=117.2.40.0, Culture=neutral, PublicKeyToken=40c4b6fc221f4138'. File not found."

Tried checking file integrity, it didn't help.

In such cases it helps to get rid of the launcher and have it verified/reinstalled via Galaxy.

Delete the Launcher folders in local AppData and the game's folder.

So that explains why theres suddenly a Hotfix #12 on GoG.

The chaos gets ever worse.

Why do some people correctly say "Patch 4 Hotfix 2", as it should be, and others have this stupid habit of calling it "Hotfix 11" ?

The Patches are actually more important than the Hotfixes. As the words say, really.

Really a Hotfix should be an emergency measure, when a security issue has been found. Not the name of a regular patch. Which is what hotfixes for BG3 really are.

The naming convention from Larian/Steam is Patch #1,2,3... and so forth, and hotfixes are 1,2,3....9,10,11 and so forth.. next would be 12,13,14 and so on.

GoG decided their own naming convention, so Patch#1, hotfix 1,2,3. When the patch number changes they restart the hotfix numbering, so Patch#2, hotfix 1,2,3. Patch#3, hotfix 1,2,3.

SO... Larian/Steam Patch4, hotfix 11 EQUALs GoG Patch4, hotfix3. BUT this time they skipped/mislabled, because the last hotfix was actually Patch4,hotfix1 so hotfix11 should have been hotfix2, but for some reason its called hotfix3.

Chaos and confusion.

Honestly, I don't think GoG will redo that patch. I guess you could wait, but once it disappears from the list of downloads, it's not coming back.

The largest c: drive I have on my PCs is 500 GB. So, I could only test, trying to run that patch to a certain point. I just ended up uninstalling and reinstalling the game.

That patch had ridiculous system requirements to run and I have never in my life come across a patch that crazy.

Sucks for people with limited/capped internet, but the better option is to download the game again. I've read the install time for that patch was between 30 mins - 2 hrs to install for some people. (I'm guessing depending on PC specs?).

Ah! Ok. I now understand what you were trying to say.

I do agree the Larian naming convention can lead to confusion BUT this will only affect us GoG owners of the game.
Since on the other platforms the patches/hotfixes are automatically installed in the correct order.

The way GoG is naming the patches/hotfixes is the better way for us because we have the option of downloading the patches.

Anyhow, I get what you were trying to say. thumbs up.