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
A weaker GPU just means a lower FPS, not crashing. And people ARE using a GTX1060 so, not to be rude, but do a little research before giving advice.
https://www.youtube.com/watch?v=mUYCGw3YB9U
It's almost certainly a software issue with the game and/or some combo with Windows and/or NVidia drivers. MANY people having crashing issues for seemingly different reasons.
Now it's crashing on startup again.
POS.
IF it's saved games being corrupted, that SHOULD be being detected at startup and the problem games tagged as unplayable. I don't think it's that because it crashed with no saved game present as well.
Edit: Might have found a potential fix for my case (didn't get any crashes in multiple tests); I though about trying to install any video mod to see what would happen and read that BG3ModManager required these two versions of .Net Framework:
• .NET Framework 4.7.2 ( https://dotnet.microsoft.com/download/dotnet-framework/net472 )
• .NET 7.0.13 ( https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-desktop-7.0.13-windows-x64-installer )
I had the Net Framework updated beforehand, but after just installing these two (maybe one of them was enough, dunno), I booted the game to see if anything broke without installing any mods, but voila, things seem to work now.
I tried everything I can think of. Is ♥♥♥♥.
It sucks that the game crashes for people, and I have no good advice since it seems to work fine for a long time until it doesn't.
Larian is still patching the game. I would recommend just waiting a few weeks, months and then trying again or returning it if you are able... you'll probably go around in circles trying to fix this yourself and there is plenty of BAD advice.
Solid PC that works fine for your OTHER games? Then it's probably THIS game.
So the game wasn't crashing, it wasn't being found. Hint to Steam/Larian, letting the user know that an executable can't be found would be helpful :).
Fix: There are scripts that allow you to run Windows executables directly on Linux using Proton. Running on that initially got me running bg3 but the wrong save dir.
Some alterations to the script and I had my old save games back.
Reason this triggered is that my game collection is spread across 2 drives, an older HD that has the older and less resource hungry games, and an M.2 drive with the ones that need the speed. Steam got VERY confused WRT BG3 and although it found the Larian launcher that couldn't find the bg3.exe file.
Note that I have other games on the M.2 drive, BG3 is the first to trip this problem.
Unsure if this can also impact Windows users but I wouldn't be surprised.
I'm not quite sure what's going on with your EXE not being found, or exactly what you did to resolve this but "alterations to the script" doesn't seem the way to go even if it's working for now.
I believe BG3 wouldn't launch for me because I had an extra file in the same folder that the EXE was located. I got some weird error (data not found or something?). I think I'd backed up the EXE or something but I forget the details... anyway, the Larian launcher got mad I guess that there was something there that "shouldn't" be there. I've never seen anything like that before.
So... I've got considerable experience in backing up and restoring Steam games and almost NEVER had issues with Steam being confused. It's probably a Larian issue. Here's the way I'd handle your current situation:
1) BACKUP the game in Steam (I assume the backup would be over 100GB)
2) In Steam "browse" to the BG3 install folder (BG3-> properties-> Browse Local Files)
3) UNINSTALL the game
4) DELETE the game folder if it still exists
(I said to browse to it first just so you know you're in the right spot. It should disappear when you delete the game. If it doesn't there may be some file there that shouldn't be there.)
5) BACKUP (COPY) your SAVE folder just in case (but leave cloud backups on. So you shouldn't need it)
6) DELETE your Config/Save/launcher Game "Larian Studios" folder
(see PCGAMINGWIKI link at bottom.. will need to show "hidden Items" in File Manager to see those locations... for example, I'd delete the "Larian Studies" folder here on my system (which includes the "Launcher" folder)->
C:\Users\j_d_b\AppData\Local\Larian Studios
7) RESTORE your backup
8) this MAY sort out any of the odd issues you experienced
9) LAUNCHER-> When I skipped the launcher which was talking about some data error my game launched just fine. Only THEN did I go back and figure out the problem (which isn't the same as yours apparently?).
(Launcher skip, save and config folder locations at PCGAMINGWIKI link below)
https://www.pcgamingwiki.com/wiki/Baldur%27s_Gate_3
Side Note:
The launcher still acts like I don't own the game and offers to let me buy it even though I can start it from the launcher. And it won't link to my two other Larian games.
So in SHORT:
- backup the game
- copy save folder just in case
- uninstall the game
- delete the "Larian Studios" folder
- restore the backup...
UPDATE:
I'm pretty sure the "Larian Studios" folder I said to delete doesn't go away if you uninstall the game but I've not tested it. So maybe change the order. Your saves also should be on the CLOUD, but Larian seems to have weird issues I've not had before.
IF I run with proton from the other drive (Proton experimental which has been the most useful in my experience) the paths are messed up when the Larian launcher is run from it's install dir on the M.2 drive. As a result bg3.exe isn't found.
Appears to be a problem in the setup Steam uses, likely impacts anything across drives that uses a launcher. There's no obvious way to move proton versions across drives and even if there was that probably would just mean that older games on the HD would stop working instead.
I'm happy with my hack - starting the game is much faster ;) but getting it across to Steam that there's a problem in this case, well I'm looking at the D20 dice now and thinking 'this is going to roll a 1' :)
I have opened an issue with Steam but odds of it being fixed look miserable.