Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
Or have been playing for a while and just now started failing?
If you already tried everything, go refund or use a third party service like GeForce Now.
Lovely.
Best advice is to hold off on trying to play the game until the next Patch/Hotfix rolls around. If this is your first foray, getting a refund is a perfectly valid way to go if you wish.
Just for reference, I can corroborate the game crash at start on my end, but for me it's doing a bit more than that.
Each time it crashes, it also CTD's another program on my computer. Usually Discord, my web browser, Notepad, Steam, Acrobat, etc. This last crash just now to try to troubleshoot on my end CTD'd Steam alongside BG3.
What you described for your cases might be resolved by this
https://steamcommunity.com/sharedfiles/filedetails/?id=3031161135
Will definitely give it a try, you're a scholar & a saint.
The major point I wanted to make though was the fact that this is (iirc) the second time players are experiencing CTD at launch. First time this happened was during Hotfix 5, and was conveniently the first time I had to put the game down for a while because it was quite strictly unplayable. It was dead space on my device because of it.
So if this is happening again at a larger scale, we have a problem.
To put your mind at ease. OP has this issue on first time playing while the issue you described was people for who it worked suddenly starting to CTD. So it's rather different from what you went through in the past.
Also, this is an incident. It takes at least three incidents to make a trend and when it comes to technical issues where a myriad of things can cause the same kind of incident, you really need some common cause first for a trend.
So don't get worried about this happening to you as well immediately I'd say.
New Patch is potentially more worrisome :-)
Regardless, if troubleshooting isn't helping to isolate the root cause of the issue for me, then the game's getting benched again until the next hotfix. Quite frankly, it's two steps away from that for me at this point. If a full system reset doesn't fix the issue, I'm doneskies for a while.
I cannot confirm, that but I do indeed recall a series of people posting about issues since certain larger patches. In fact wave after wave. The problem I have with the general description is that they do not go into detail what caused the issues.
For example: the first wave was caused by leftover patch files where Larian Studios support have prepared information to resolve it quickly. People who did not use the support steps "kinda had to wait" until patch#4.
After that it was mixed wheras the majority of legit issues were Larian Launcher related issues, hence the recommendation to skip the launcher / launch the game directly from the executable without Steam has helped ever so often.
Those recommendations and workarounds were not as visible as much as I wished to be, as pretty much every time they got swamped and flooded by majority reports which were unmistakenly caused by mods, similar to the recent "wave" where people could not submit quest items there were waves for ~
The Dark Urge and naked men in character creation
invisible party hotbar
stuck in sleep
quest items not spawning
scripted dialogue not ontinuing
effective savegame corruption
For the latter one prominent wave I still remember from early on is the once common "66% issue" ~ games which "stuck" loading at 33%, 66%, 70%, 100% ~ "stuck" because they were more or less "stuck". If you knew what it was causing that it was resolvable and the information I have collected was indeed used to reduce the issue for Act 3. It should not appear at all anymore these days.
Anyroads, getting back to threadstarter and keep things simple: if they did everything as suggested by Larian correctly, and they were never able to start the game yet, refunding is the correct process next.
On a Mac the troubleshooting can cut short to "it either works or it does not". On the one hand because Macs are limited as they are, on the other hand because Mac users do not share much information to begin with to troubleshoot. Seeing OS 14 is being used is in general a sufficient indicator that on that front it is okay. Mayhaps should not share the UUID and serial number so carefreely as they work different on Mac than on Windows.
The automatic refund bot will deny any refund requests past the two hours mark - so go to the Steam Support page -> show receipt -> choose one of the advanced option there to explain your case to the Steam Support. There should be no issue in receiving a refund after a manual check which confirms the story of "5 hours = loading times" as loading time on many Macs are unbelievable horrible. As in: 20 minutes and more.
Giving this a try right now, so far it's showing promise, I got past launch. We'll see if save files load for me or if I get any of the other notable ones like a CTD after lost concentration on Darkness.
UPDATE: It worked. Right up until I tried to load a save file. I was able to launch the game, change my brightness settings, adjust video settings to lessen graphical strain (in case object overflow or graphical artifacts were an issue), then tried to load an autosave on a Media to BG3 run I was doing. CTD.
This was after restarting the device, mind. I'm officially benching this until the next hotfix because there's nothing else I can do.
Keep in mind: in some cases when it turns out to be a savegame issue, the best way to be sure is to share the savegame and have someone else check it. It is not always one's PC at fault. Most of the time it is due to third party apps people forgot about. But there are rare issues as well.
One example is that with the Larian Launcher etc. connected devices can be the cause of issues. Sounds weird, but that is how it works with DirectX.
A crash after casting a spell in Darkness - I am not sure if it is a technical issue or an ingame bug needs checking from the description alone. Hence the mentioning of savegame issues as possible option.
Also, depending on the capacity of one's PC I always recommend these steps, especially for "low end PCs".
https://steamcommunity.com/sharedfiles/filedetails/?id=3065050571
https://steamcommunity.com/sharedfiles/filedetails/?id=3016159305
The first one is more general while the second one was one of the first guide I made for Baldur's Gate 3.
My PC is over eight years old, and I have not much to spend. So I treasure what I got and even with things getting old, not as good as what nowadays standard could be, I always looked for ways to tweak things from early on. Even before Vista's readyboost I used similar software which made me utilised USB sticks as SSDs. Sounds weird, but you get creative if you cannot afford much.
These days it still helps a lot with low capacity PCs to address the virtual RAM and CPU specifically, alongside using the RAM cleaner software mentioned above.
From the little information in your case about CTD when losing concentration on Darkness I recommend therefore:
a) share your savegame and have someone else checked it too - get into such a situation, hit F5 or make a proper savegame in combat, then check if that issue becomes reproducable that way just by toggling off concentration
b) make sure your virtual RAM / pagefile is high enough
c) use the automatic RAM cleaner software as described
d) increase the game'S priority to high
e) exit Steam before launching the game from the executable
f) run the game in windowed mode
That would be the best approach from my point of view. Naturally you do not have to use everything every time. After pinpointing whether such helped with the issue or not you then check what can be done differently e.g. run the game from Steam using skip launcher instead exiting Steam first etc.
And again: even something as banal as connected device issues like gamepass or a defective gamepad can cause unexpected issues.
I once had a case where the PC was absolutely fine. Remote analysis showed nothing. On site checking showed nothing. Want to know what was the issue by the end of the day?
A defective USB hub they use at home for charging their smartphone while at PC.
Which of course the person did not bring along.
But as soon as they plugged everything back at their home the issue reoccured.
Those kind of issues are the worst. Because you can do endless checkings, and without knowing these kind of stuff you might never find it.
Once again, much appreciate the sharing of resources and tools to help with problems like these, they're a big help (even if it's not to me; public access to this will help others, so I commend you for that). I might get to trying these out later, but as of this time of writing I simply cannot be arsed because I've already hit the proverbial f*ck it button.
So the Darkness CTD's been a 2 week long known issue. Me & Ironwu did the tests on that particular little bugger because it was a big part of why House of Grief was such a damn sh*thole for people, and it came up when trying to figure out why that place crashed so often for other users.
I'll be completely honest, I don't know the exact diagnosis of it. Ironwu might, tho. I'll I remember for certain is that whenever a caster loses concentration specifically on the Darkness spell (either by having it broken due to damage/prone or by a player going to the character's control and actively breaking it themselves), it causes a CTD. Fog Cloud, Cloudkill, Insect Plague, Hunger of Hadar, and other cloud-based hazard spells don't cause this issue; only Darkness does.
That's always the funny little thing about tech, innit? It's always the wild sh*t that comes out of left field for people, and it always involves some benign little thing that under normal circumstances wouldn't ever make one stroke out over the issue.
The gaming has been running fine for months.
Gentoo Linux
Linux 6.7.1-gentoo-r1-x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jan 25 13:38:07 EST 2024 x86_64 AMD Ryzen 9 5950X 16-Core Processor AuthenticAMD GNU/Linux
Nvidia Geforce RTX 4080
11-drivers/nvidia-drivers Latest version available: 535.154.05
Crashes with DirectX and Vulkan drivers.
------------------------------------------------
Is there a fix?