Larian Studios Forums Active Threads This Week

I'm having the same issue on X-box. I've been doing a crossplay in Honor mode with my mate, which doubly sucks. We saved it on Wednesday and I noticed the depreciated version error this evening.

Just went to the Underdark by way of Zhentarim hideout. Buff up, go down ladder, leap over traps, attack nearby minotaur.

First hit, 95% chance, hit.
Action surge
Second chance, 85%, not sure why, but whatever. Should I do feinting attack to get advantage? Nah, let's just go for it.

Critical miss.

Really? This isn't an outlier. This is the average thing.

Well, time for the awesome power of F9.

Just bring back the cut Minthara pregnancy if you're gonna keep patching the game

If y'all bring back pregnant Minthara I'll pretend none of the nonsense these past 2 months ever happened.

Beautiful example of the buggy doors.

Sneaking up on the Githyanki, Wyll can't cast a surprise eldritch blast because the door opening blocks the way.



But they can still sneak 50 cm further on,to pass across the door opening , and then the spell can hit target.



Please avoid this in your future games, Larian.

Because games like this are pretty fun to play through multiple times, even mainstream players do it so its very common, what would greatly improve the story and gameplay aspect of it is failure. And i mean failing at big story elements.

In BG3 and in classical story telling you can set aim for yourself such as "i try to save the world" or "i will sacrifice the world for my god" or "i will become tyrant" etc and whatever your aim is going to be, achieving that in BG3 and in classical design is easy and game kinda tells you on every choise which one to pick if you want to achieve this or that ending. This is safe design and lacks total ambition and actual design art of story telling and player manipulation. Are you truly setting the bar so low larian ?

In bg3 you did have a moment, my favorite moment in the whole game, where player could fail to save isobel from kidnappers, at that moment many players had chosen "i will be a hero and save these poor people"... then you failed as isobel died and game totaly rubs it into your face, showing how horrible end all those poor people end up facing because of you failed. It was very sad and a surprise for every player who ended up failing at that point. Total masterpiece of story design in a world full of cliche stories where you can predict everything that is going to happen next. That moment should become whole aspect of story telling because of it is a game, even if you make players fail they can re-play, in fact they get burning urge to re-play and correct their failures they had on their first run. There is a game that did this in tiny scale, a very good game, dragon age origins, a lot of players didnt get the endings for certain things that they expected, instead they got sad endings.. that made everyone replay and try to figure out how to get the ending they want, and it was NOT made easy, game didnt guide you to it instead it tried to trick you from reaching your goals, the correct choises were not the obvious choises.

And that is my main idea.. make your storytelling so that it manipulates players to fail. As they try to achieve good endings to their stories, make player think the game guides them towards it but if they follow the "obvious" choises, they end up failing, so it kinda becomes a challenge to find the correct choises, correct path to achieve the kind of ending you want to achieve. And moreover, as you reveal to your player that they have failed, that they have been tricked, rub it into their face so hard they want to smash their keyboard to the wall, make players feel sadness, disappointment and failure, possibly even in black-humorous way. That is anti-clichee and very good story telling technique for a game that people play multiple times.

Whenever you know you can surprise the player, for example when player thinks he has won a battle for something and saved the day.. Then villain returns out of nowhere and rips apart everything and rubs it into player's face as they stare their screens with their mouth open :OOO in shock unable to take action.. that should be the bar you set yourself. Next step from this is that once player finaly finds the secret and correct path, they have to live in excitement and wait and wait until out of nowhere game reveals that even the villain came back and annihilated nearly everyone, you had figured out some secret that finaly saves the day and is revealed on the darkest moment when player thinks he has failed and everything is over. That kind of reveal method maximizes the satisfaction of finally succeeding.

If this idea feels radical or very obviously bad idea.. then remember there is movies that make people feel all kinds of feelings, sadness and sorrow among them yet people still like those movies.. what separates games stories from movie stories is that games can be replayed. So make story harder please.

I don't know it's my my case specifically but I still get mad frame-time fluctuations form 8.6ms to 14.14/15.65ms, maybe it's caused by shader cache being built due to me doing a clean install of BG3 maybe?

Update: Part 3, Chapter 21 is now published. This is the beginning of Part 3 of the Hellraisers story. The adventure continues, but will the Hellraisers survive after being captured by Auntie Ethel, Minerva, and Iggwilv, the Queen of Witches?

BG3.5 - Hellraisers (Fanfiction)
Baldur's Gate 3.5: Hellraisers - an original fanfic story that is a sequel to Baldur's Gate 3 Fanfic: The Afflicted. It picks up immediately after the events of Baldur's Gate 3 as characters from the previous fanfic - Fiovay, Kai, Aelun, Vlyn, and the other members of their party - travel to Avernus. Their quest is to save Karlach but also to hopefully find and rescue Darson, Aelun's father, from the clutches of Demogorgon.

Here is the link to the blog site: https://baldursgate3hellraisers.blogspot.com/2025/10/baldurs-gate-35-hellraisers.html

This is happening to me, and it is a relatively new glitch I hadn't previously encountered. I always quick save and reload to remedy it.

While I can't tell if there are any known fictional characters that inspired Mystic Carrion, that line surely hit home for my tabletop campaign. I have a rather powerful good-aligned (think crypt keeper knight) mummy NPC friendly with the player characters who once complained to a player that even years after being awakened, their bodies still have reflexes left over from being alive, like wanting to draw breath when startled although they too keep their lungs in a pot, developing cravings for food they can't eat, or expecting pain when cut or panic when they can't breathe, but then only feeling numb and dead. The warmth of a living being and feeling a heartbeat are calming to them.

In AD&D, other types of undead are usually tied to the Negative Energy Plane which comes with an innate hate for anything positive or living, although some higher undead can control this urge. Mummies, however, get their regeneration and rotting touch powers from their connection to the Positive Energy Plane which replaces their natural life force. If you're a real mummy nerd, the ba remains with the mummy, while the ka moves on to the Outer Planes and gets replaced.

I don't mean to disrespect anyone who started on newer D&D rules, or who got them working for their group, but it's actually still mind-boggling to me that people have been playing D&D for a quarter of a century with WotC combat rules. The original AD&D (2e) rules were convoluted, confusing, often frustrating and showing signs of age, but they only needed a cleanup (do I have to roll high or low for this?), some fresh concepts (Saving Throws, damage flavours,...) and maybe a little less anti-player bias. But, WotC seems to have confused the often counter-intuitive AD&D rules themselves. Or maybe in some sense, D&D 3e continued only old D&D's straightforward simple but far less granular rules, while AD&D was discontinued. However, seeing how the rest of the rules were treated, I have severe doubts that this was by design.

The 2e-based combat rules I use at the table have combat phases (determined by initiative, number of attacks and speed factor of weapons/spells/actions), combat rounds (which combatant's turn it is - duh, but we're playing in German) and combat turns which renew after every combatant has used up their actions. This means the first one to act would use their first attack, then the next character would use their first attack, or maybe draw the attack to parry for higher AC, retreat or do whatever. Then you'd proceed to second attacks and so on. Dropping combat phases has led to this awful taking of turns with attacks (you hit me thrice, then I hit you thrice) that made everything post-Y2k unplayable for me. In 2e, thieves and (some of) their subclasses can use backstab on any surprised opponent. To use this ability, the thief must be behind the victim and the victim must be unaware that the thief intends to attack them. This usually boils down to one backstab per combat encounter, as you'd expect a comrade dropping to the ground with a knife in the back to be a bit of a giveaway, but this is a limit that can be pushed with magic, clever use of terrain or skill.

Yes I can confirm - it works!
I can walk through busy streets of Baldurs Gate!

Thank you very much

P.S. And as it is in description, displaying tool-tips windows is fixed (compare gear description it used to disappear )

Checked again today and hotfix 36 does not correct crashes on saved games. Frame rates are better but even with using an act 2 save then moving into the lower city (with all previous saves deleted), the game still crashes for any save made after entering the lower city. I’ve done all the recommended steps to troubleshoot (reinstalling the game, deleting all corrupted saves, booting in safe mode, tried both connected to Internet and not, tried saves with crossplay enabled and not enabled) - the loads crash under all circumstances post entrance into the lower city.

Any ETA for a PS5 fix?

The newest hotfix (36) appears to have helped with the frame-rate problems but not the crash on loading saved games on act 3. Both with modded and non-modded games, I still cannot load any game after entering the lower city.

I reinstalled the game, cleared cache and deleted all saves flater than act 2. In both the regular unmodded game and the modded game, the moment you save after entering the lower city, those loads always result in crashes for PS5. This has been consistently happening since hotfix 35.

Larian - please fix this. The game is unplayable at this point for Act 3.

Yep! This is the latest Hotfix for BG3 that should address some of the issues with performance and crashes since the latest update: https://forums.larian.com/ubbthreads.php?ubb=showflat&Number=960877#Post960877

I’d go sword & board tbh. It fits Lae’zel well and makes her way tankier for tactician, which your team kinda needs.

DW can work, but it feels a bit weaker and more gear-dependent. Sword + shield is just solid, consistent, and still hits hard enough.

I just got the dwarf-tiefling mod and it pretty cool. But what I really would like is a fiendish gnome. I would absolutely love to have a gnome running around with some cool horns. I was hoping the modder of the mizora mod would make one for the smaller races but they said it was to difficult due to size differences. So I guess a whole new mod would need to be made like it was for the dwarf-tieflings. But the horns HAVE to be cool. I really don't like any of the tiefling horns but theres some cool horns in the dwarf-tiefling mod. Anyway, I would really really appreciate it if someone could make up a fiendish gnome. Gnomes are my favorite and fiends are cool. But no wings for me please. If you want to add them please make them toggleable. Thank you very much if you make this.

Is there any chance to get Apple Pencil support for the iPad? That would make the game perfect. Asking Larian for that since 2023, but they ignore me. 😅

I'm playing on PS5 with two friends. One is on PS5 and the other is on PC. We have played BG3 before in September 2025 with no issues, but now when we play about every 10-20 minutes I'll get disconnected from the game. We have mods downloaded but don't have them enabled, and the game runs smoothly when we are playing. When me and my PS5 friend play together there are no issues, idk why I keep getting kicked out in the cross-play lobby when we've played together before. Anyone else having this issue or know a solution?

hi
I really can’t wait to play the new divinity but I really will appreciate it if you could include Arabic subtitle for it
And i think you saw Arabic players play it and there a lot more
the game will take a long time to release so I really hope for an Arabic subtitle
Thank you

Thanks for the reply, I appreciate it.

I already tried that. I did a clean uninstall and also checked for leftover files.

I even renamed the AppData folder to force the game to generate a completely new one from scratch, so it should be a clean environment.
Unfortunately, the issue still persists exactly the same.

I played for about 20 hours on PS5, but the game never really clicked for me with the controller.
I’d like to start another play through and wanted to check if there is any chance of PS5 ever getting mouse support before I buy the game on Steam - and most likely a more powerful PC to play it.
Thanks!

Hardware/Software:

MacBook Pro M4 Pro (Mac16,8), 14 cores, 24GB
macOS Tahoe 26.3.1 (25D2128)
BG3 v4.1.1.7151330 (latest as of March 2026)
External 4K monitor, lid closed (clamshell mode)
Xbox controller + PS4 controller
Problem:

Local split-screen crashes every ~5 minutes in the Underdark. Single-player does not crash. Act 1 wilderness in split-screen was stable for hours — the crashes started once we progressed to the Underdark.

What I've tried (none helped):

Visual settings reduced to Medium
Disabled cloud sync
Disabled Game Mode
Stopped all background processes
Verified file integrity
Crash analysis (6 reports, all identical pattern):

All six crashes are EXC_BAD_ACCESS (SIGSEGV) / KERN_INVALID_ADDRESS on Thread 0 (main thread). The faulting address is different every time (wild/garbage pointers), which points to a use-after-free or dangling pointer rather than a consistent null dereference.

Crashing call stack (consistent across all 6):

AGXMetalG16X ComputeContext<...>::setBuffer_impl<AGXBuffer>() + 68
Baldur's Gate 3 rf::RendererCommandBuffer::Submit() + 160
Baldur's Gate 3 ls::GameRenderView::FinishRecording() + 88
Baldur's Gate 3 rf::RenderFrame::FinishRecording() + 144
Baldur's Gate 3 ls::RenderThread::Update() + 4268

I can provide the full crash reports if helpful.