Baldur's Gate 3 (1086940)

[cwebster2]

Compatibility Report

• Name of the game with compatibility issues: Baldurs Gate 3
• Steam AppID of the game: 1086940

System Information

• GPU: GTX 1080Ti
• Driver/LLVM version: 455.23.04
• Kernel version: 5.8.0
• Link to full system information report: Gist
• Proton version: 5.0.9

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Game does not start. fails to run steamapps/common/Baldurs Gate 3/Launcher/LariLauncher.exe

Reproduction

Install game, click Play.

steam-1086940.log

[kisak-valve]

Hello @cwebster2, looks like there's several rough edges in the log, but wine: Call from 0x7b00fc3e to unimplemented function mscoree.dll.GetTokenForVTableEntry, aborting stands out more than the rest.

[cwebster2]

Hello @cwebster2, looks like there's several rough edges in the log, but wine: Call from 0x7b00fc3e to unimplemented function mscoree.dll.GetTokenForVTableEntry, aborting stands out more than the rest.

Hi @kisak-valve, I agree in that assessment of the log. If there is anything i can test, i am happy to do so.

[AnhVanGiang]

I got the same issues, heres the log:
steam-1086940.log

[olav-valle]

Chiming in here to say that the GOG version of this game also crashes if you try to start it with the LariLauncher.exe, but seemingly works very well if you start the bg3.exe instead (not past the character creator yet). This is using wine-tkg 5.17 that I compiled for use with Tony Hawk's Pro Skater 1+2, and includes some additional patches if I remember correctly. I'll see if I can remember what those were, in case they can help.

[AnhVanGiang]

Chiming in here to say that the GOG version of this game also crashes if you try to start it with the LariLauncher.exe, but seemingly works very well if you start the bg3.exe instead (not past the character creator yet). This is using wine-tkg 5.17 that I compiled for use with Tony Hawk's Pro Skater 1+2, and includes some additional patches if I remember correctly. I'll see if I can remember what those were, in case they can help.

You are correct, i tried running bg3.exe with ordinary wine and it runs perfectly well.

[przmkg]

Managed to make it work (Proton 5.0.9) with a similar solution to what's required for Divinity 2:

Run the following from your Baldur's Gate 3 main directory.

mv Launcher Launcherbak
ln -s bin Launcher
ln -s ./bin/bg3_dx11.exe ./bin/LariLauncher.exe
cp ./Launcherbak/*.dll ./bin

Little explanation:

I had to basically trick Steam into thinking it's running the launcher but it's actually the executable.
On top of that, I had to copy all the dll files from the Launcher directory into bin.
The vulkan version crashed on start for me so I use the dx11 one here.

Edit: It crashes after character creation
Edit 2: I switched to amdvlk and it works now with the Vulkan version. It no longer crashes after character creation

[Leopard1907]

@przmkg Your driver version/compiler ( if there are multiple options exist) and gpu?

[olav-valle]

@przmkg
I have no issues running the vulkan version in wine. Might be an issue with your vulkan version?

[przmkg]

@Leopard1907 I have a 5700xt with Mesa 20.1.8 (llvm 10 I think).
I have only tried with the ACO shader compiler, maybe that's the issue.

[alosarjos]

Tried the Vulkan version on Arch Linux (5700XT + Mesa 20.2). Just got a black screen, the Dx11 version runs fine. Here are the logs for the Vulkan version (Needed to compress it like ZIP)

I also could run the Vulkan version with the AMDVLK drivers

Vulkan_Log.zip

[kisak-valve]

Hello @alosarjos, fixme:vulkan:wine_vkCreateDevice Support for allocation callbacks not implemented yet looks like a line of interest from the log. This is followed by a bunch of access violations (c0000005). The circumstantial evidence previously mentioned devalues this observation.

[alosarjos]

Hello @alosarjos, fixme:vulkan:wine_vkCreateDevice Support for allocation callbacks not implemented yet looks like a line of interest from the log. This is followed by a bunch of access violations (c0000005).

I have opened an issue on the Mesa GitLab: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3607 in case you can provide more info or logs on what they may need.

[GloriousEggroll]

It needs vcrun2015 or 17 or 19 on newer versions of wine

DX11 crashes after char creation on nvidia, AMDVLK, and RADV
Vulkan works on Nvidia and on AMD with AMDVLK
Vulkan crashes with RADV
Saves work fine.
You only need dotnet48 for the launcher, which takes way too long to install and sometimes fails. If you skip the launcher and launch the game directly, it works fine.

Here's a protonfix that works with my latest ge release on vulkan, as noted for AMD you currently need AMDVLK:

1086940.py

""" Game fix for Baldur's Gate 3
"""
#pylint: disable=C0103

from protonfixes import util

def main():
    """ Run script extender if it exists.
    """
    # Fixes the startup process.
    util.protontricks('vcrun2019_ge')
    util.protontricks('d3dcompiler_47')
    util.replace_command('LariLauncher.exe', '../bin/bg3.exe')

Drop it in to Proton-5.9-GE-7-ST/protonfixes/gamefixes/

[MrCraigen]

I used protontricks to install dotnet48 with Proton 5.0-9.
The launcher started, Vulkan render works great with Nvidia card and i was able to create a character. Also played for an hour. No crashes and save / load works.

[ldust667]

@MrCraigen what OS are you on?

[patrickholley]

@GloriousEggroll Your patch worked like a charm; thanks!

[1beb]

Just wanted to add to @MrCraigen comment, with some more explicit instructions:

sudo python3 -m pip install protontricks
protontricks -i baldur # get the (ID) that's in round brackets
protontricks ID dotnet48 # I had to run it twice because something got stuck or it appeared to stop updating
# It will open an agree/continue dialogue window

[cwebster2]

I tested my installing dotnet48 into the game's wineprefix with protontricks and while the launcher appears to have some grapghical glitches, the game does launch and seems to be working fine. havent made it past character creation, and will update once i have some time in game

[cwebster2]

Game works great!

[SET001]

@1beb this gives me the error

Unknown arg dotnet48

[MrCraigen]

@MrCraigen what OS are you on?

Im using Manjaro KDE, I installed the protontricks through the AUR

@1beb this gives me the error

Unknown arg dotnet48

What version of winetricks are you using with prontricks? I'm using winetricks 20200412.
You can try run protontricks --gui, choose Baldurs Gate 3 on the list and then dontnet48 from there

[SET001]

after updating winetricks I was able to install dotnet48 and then everything runs just fine ))
Thanx!

[ZarathustraDK]

Proton installs a bunch of dependencies when the game is first launched through Proton for the first time, so for people using Lutris or Wine you'll need get those dependencies also. I don't know exactly what those dependencies are, but most likely they're the cause of your misery.

For Proton (with dependencies installed) the game will refuse to start without tinkering (as in Play-button turns into "Loading" for a few seconds, then back to "Play").
This is fixed by linking the executable as described in another post above. Alternatively, copy the bg3.exe from the Bin-folder to the Launcher-folder, then, in the launcher-folder, rename LariLauncher.exe to something else, and after that rename the copied bg3.exe to LariLauncher.exe. Game should work then, at least it does for me on an Nvidia-card.

[Traxmaxx]

I did the mentioned steps but it's still crashing. Tried AMDVLK and RADV.

• GPU: RX 580
• Driver/LLVM version: Mesa 20.1.5, LLVM 10.0.1
• Kernel Version: 5.4.0-7642-generic
• Link to full system information report: https://gist.github.com/Traxmaxx/ce57cf1009e3b93e13476a536abcef52
• Proton version: Proton-5.9-GE-7-ST

Log: https://gist.github.com/Traxmaxx/826dcfed9d438d69a2438ea08ea4ecc5

[ArcanePhysics]

@Traxmaxx
I seem to have the same issue on
OS: Pop!_OS 20.04 LTS
KERNEL: 5.4.0-7642-generic
CPU: Intel Core i5-6500 @ 3.20GHz
GPU: AMD Radeon RX 470
GPU DRIVER: 4.6 Mesa 20.0.8
RAM: 16 GB
Get Same errors with AMDVLK

[GnomeBeans]

Replying to #4243 (comment)

you mean dotnetdesktop6 in winetricks or was that a typo? No wonder you would see a help command list.

[TacticalLaptopBag]

Replying to #4243 (comment)

I was seeing multiple guides with protontricks dotnetdesktop6, is that winetricks only? That would make much more sense if that's the case lol

[Kaukov]

Replying to #4243 (comment)

As mentioned above by me, I experienced the same issue. Turns out the game has issues when you have .NET SDK installed on the system. If you uninstall it, it will launch without any issues. There was a time when a certain version 6.something of .NET SDK worked fine, but the recent versions of 6.X and 8.X started producing the error again, so the only solution is to uninstall .NET SDK.
Update: having only .NET SDK 6.0.X installed or selected as the system .NET SDK, the game launches fine. But having .NET SDK 8.0, 7.0, or any other version different than 6.0 will break BG3

[Venefilyn]

No success on my end, tried the sed replace, protontricks, different Proton versions including experimental and GE.

No clue what to look for here. This is with
PROTON_LOG=1 eval $( echo "%command%" | sed "s/Launcher\/LariLauncher.exe'.*/bin\/bg3.exe'/" )

Also tried
PROTON_LOG=1 eval $( echo "%command%" | sed "s/Launcher\/LariLauncher.exe'.*/bin\/bg3_dx11.exe'/" )

Running Mesa 24.0.6

steam-1086940.log

[gonneman]

I would also really appreciate some help. I've tried some other Steam games (Monster Train and Doom) which work fine, but BG3 just crashes when I try to launch it.

I am running openSUSE Leap 15.6 on a Dell Precision 7550
GPU: Quadro T2000/PCIe/SSE2
CPU: 12 × Intel® Core™ i7-10850H CPU @ 2.70GHz
Graphics Platform: X11
Kernel Version: 6.4.0-150600.21-default (64-bit)
steam-1086940.log
steam_sys_rep.txt
steam_runtime_sysinf.txt

Does anyone have any advice? When I click play the launcher starts without problems. When I then try to start with DX the game crashes instantly. When I try to start with Vulkan it hangs at a black screen.

[wwmm]

Replying to #4243 (comment)

Is there any change if you use proton experimental instead of GE-Proton?

[gonneman]

Unfortunately not. I get exactly the same behaviour from proton 8, 9, experimental and GE.
Is there a way to get more informative error messages? Or any other information I could provide.

[saghm]

Based on the ICDs listed in your steam_runtime_sysinf.txt, it looks like you have an "nvidia optimus" setup where there's both an integrated GPU on the processor and a discrete nvidia card for the higher performance stuff. I don't have any experience with opensuse personally, but from a quick google it seems like the nvidia drivers are only available via a third-party repo.

I think following the steps here might be necessary if you haven't done them yet.

[gonneman]

Well spotted. Yes, I have the latest Nvidia drivers (550.90.07) installed.
I've used the suse version of nvidia optimus (called prime-select) to lock things onto the discrete nvidia card only.
Since I can run the Steam games "Doom" and "Monster Train" (no particular reason for those choices apart from them being quite different from each other and in my library) without any issues. I'm taking this as fairly solid evidence that my nvidia drivers are properly installed and configured.

[saghm]

Interesting, thanks for the additional info! I noticed under the "vulkan" -> "icds" section of the runtime info that the nvidia file is in a different place than I would expect (/etc/vulkan/icd.d/nvidia_icd.json rather than in /usr/share/vulkan/icd.d; on Arch all of mine are always under /usr/share), and I figured it was worth double checking. BG3 does have settings in-game for selecting the GPU, so I wouldn't be totally shocked if it was using the integrated one by mistake due to some combination of how it attempts to detect the default GPU and proton maybe passing the info through in a way that differs slightly from how the info appears on Windows natively.

I think you can rule out whether the issue is the wrong GPU being used by overriding the list of available Vulkan loaders to only include the nvidia one by doing the following:

1. Right-click the game entry in the list on the left side of the Steam window
2. Select "Properties..."
3. In the "General tab", add the following to the box under "LAUNCH OPTIONS":
   VK_ICD_FILENAMES=/etc/vulkan/icd.d/nvidia_icd.json %command%

My hope is that running the Vulkan version of the game like this will at least get further than the blank screen you're seeing currently. If it doesn't, at least we'll be able to rule out the issue being the game trying to run on the integrated GPU.

[gonneman]

I added that launch option and sadly still get the same result: An instant crash when launching with DX and a hung black screen when launching with Vulkan. So I guess this is evidence for the nvidia implementation of Vulkan being used?

[saghm]

Yeah, sounds like the issue isn't that it's trying to use the integrated GPU.

I took a closer look at the log you provided from trying to launch the game; it looks like it's from trying to launch the DX11 version of the game (from the presence of info: Game: bg3_dx11.exe a couple of times but not info: Game: bg3.exe. Assuming this was from one of the attempts you made launching with DX11, if you could provide one from launching with Vulkan as well as a log file from launching one of the other two Steam games you mentioned working fine (just booting the game to the main menu or something should be fine), I could take a look and see if there's something obvious that's different about them to try to narrow down what could be going wrong.

If this log was from an attempt to launch with Vulkan, I'd be interested in seeing a log file from an attempt to launch with DX11! The fact that you're getting different behavior with DX11 and Vulkan means that something different is happening, but I have no idea what it could be if the DX11 version is getting launched when you try to use Vulkan as well.

[gonneman]

Certainly. Here are the log files you requested.
The other games:
monster_train.log
doom.log

BG3 DX11
bg3_DX11.log

The Vulkan log file is 45MB and so I can't upload it. Here is a Google Drive link to it instead.
https://drive.google.com/file/d/1twBWwijoACfOKsMkTE-aoP4oLtE9K3FT/view?usp=sharing

[saghm]

Comparing monster_train.log to the vulkan BG3 one, a couple of things stick out:

• Monster Train is using Proton Experimental, whereas BG3 is using Proton Ge 9.6. I think you mentioned earlier that you had tried using experimental as well, but if you could try it again and make sure to try to launch the vulkan version of the game and send the log on Google Drive again we can potentially eliminate some of the other differences that are superficial
• BG3 seems to be using DXVK-NVAPI, whereas monster_train.log doesn't mention nvapi at all. I'm not sure if this is just due to the different proton versions though
• The BG3 vulkan log contains the line NvAPI_DRS_FindApplicationByName (Z:\home\gonneman\.local\share\Steam\steamapps\common\Baldurs Gate 3\bin\bg3.exe): Executable not found. I'd be surprised if this file actually didn't exist at all for you since it should come with the game installation itself via steam, but worth double checking since it would definitely cause issues if you don't :)

In case it's helpful to know, I've mostly been stripping out trace and fixme: level logs to make it easier to look at the less granular error messages. If you're comfortable using the CLI, you can do this yourself with grep -v trace: | grep -v fixme: or something similar to keep the file size small enough to upload; the log files you provided end up only being around 700 lines or so after that.

[gonneman]

OK here are Monster Train using Proton GE
monster_train_GE.log
and BG3 using DX11 and Proton Experimental
BG3_exp.log

I trimmed the log files using grep, as you recommended. That was very helpful advice and much appreciated, thank you.
I also check \home\gonneman.local\share\Steam\steamapps\common\Baldurs Gate 3\bin\bg3.exe. The file is definitely there.

[saghm]

Looks like BG3 is still using NVAPI with Proton Experimental, and Monster Train isn't. I haven't used Nvidia cards recently, but from some googling it seems like recent Proton versions proactively try to use some workarounds to get NVAPI working when it normally wouldn't be possible to enable, so I wonder if maybe something is going on with that. If you change the launch options for BG3 to PROTON_DISABLE_NVAPI=1 %command% and run with vulkan, does it get any further?

[gonneman]

With NVAPI disabled the crash is now instant on vulkan as opposed to a black screen that just hangs. Here are the logs. Once with Proton Experimental and once with GE.
BG3_exp_nvapi1.log
BG3_GE_nvapi1.log

[saghm]

Oh, I only just realized that you're running the launcher specifically from Steam rather than the game itself; I always prefer to skip the launcher and have --skip-launcher after %command% in my launch options. Is the launcher starting up and running fine, and then the crash happening after trying to launch the game from it, or is the launcher itself not starting up at all?

[gonneman]

The launcher starts without any issues and I can selecte DX11 or Vulkan for starting the game. The crashes do not until I try to actually start the game from the launcher.

[switch-blade-stuff]

Have been having a slightly different issue where the Vulkan option fails with a "failed to collect displays" error, while the DX11 option does start the game process and audio can be heard, but no graphical window is opening.

I am using Arch Linux with SwayWM. Weirdly enough, it does work on my laptop, which also runs Arch+Sway.
My desktop has a AMD Radeon RX 7900 XTX discrete GPU and an AMD Ryzen 7 5700G CPU with an integrated Vega APU.
The laptop only has Intel Iris Xe integrated graphics.

I have tried re-installing the game with a different Proton version (experimental, 9.0, 8.0), as well as setting DRI_PRIME=1, with no effect. swaymsg -t get_tree only shows the launcher XWayland window if started without --skip-launcher, and no other BG3-related windows otherwise.

[saghm]

I am using Arch Linux with SwayWM. Weirdly enough, it does work on my laptop, which also runs Arch+Sway.
My desktop has a AMD Radeon RX 7900 XTX discrete GPU and an AMD Ryzen 7 5700G CPU with an integrated Vega APU.
The laptop only has Intel Iris Xe integrated graphics.

My desktop and laptop both have AMD GPUs and CPUS, and my previous desktop had an AMD GPU and an Intel processor (but no integrated GPU). It's starting to sound like there might be something about dual integrated/discrete offloaded GPUs might be a common pattern with some of the issues (and honestly the one time in the past when I had a laptop with this setup I always found it pretty frustrating for stuff like this). I also run Arch but I've been using Plasma 6, so I'm not sure how much of the configuration would be specific to the desktop being used (since I know that with Wayland, the compositor ends up handling quite a lot compared to desktop environments in the past with X11).

I'm not sure whether you've been trying other launch options or not, but here's what I've been running with lately with pretty good performance (consistently high framerate with close to max graphics settings on 1440p displays, although I do occasionally get a crash or two on the laptop, usually if I try to hit tab to open the group inventory UI quickly after a bunch of other inputs):

VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json:/usr/share/vulkan/icd.d/radeon_icd.i686.json STAGING_WRITECOPY=1 STAGING_SHARED_MEMORY=1  WINEDLLOVERRIDES="DWrite.dll=n,b" PROTON_NO_ESYNC=1 %command%  --skip-launcher

You'll need to tweak the ICD filenames (or remove the env var entirely if you're confident the right driver and GPU is getting used) if you're using AMDVLK, but if you're using the open source drivers in mesa the paths will be the same for you since we're both on Arch (not sure how other distros package things).

If that doesn't fix things, you might want to try comparing the logs on your laptop and desktop to see where they differ. I'd also be interested to see how similar your failing config with the dual GPU setup is to the ones @gonneman has shared; maybe there's a common pattern where dual GPU setups are somehow getting mixed up when the info is passed through Proton to BG3 that's independent of the GPU vendor.

[switch-blade-stuff]

@saghm Unfortunately your solution did not work for me. I have also tried disabling the iGPU completely through UEFI settings and using the AMDGPU PRO Vulkan drivers with no success, which makes me think it is caused by something unrelated to multi-GPU. I will try to test it on a fresh Arch + Sway install and compare the logs then.

[saghm]

Just to make sure, did you verify that only the discrete GPU was detected by proton when running with the integrated GPU disabled? This is also something you might have to verify in the logs, but if something is wrong with how the info about dual GPUs is being presented to the game when running with proton, it's not something that necessarily would be fixed by changing the bios setting. Setting VK_ICD_FILENAMES to only the discrete GPU should already be enough to ensure that it's the only one the game is using when running the Vulkan version, so if the integrated GPU is mistakenly trying to be used by the game in that case, there's no reason it couldn't also happen even when it's not enabled at all.

This isn't to say that there couldn't be something else causing the issues you're having of course, but at least from the info shared by the other user above about other games working but not BG3, it seems plausible that there's something incorrect in how the GPU settings are being detected by BG3, and dual GPU setups are notoriously finicky even when they're being used natively rather than via a compatibility layer pretending to be a different operating system.

[switch-blade-stuff]

Just to make sure, did you verify that only the discrete GPU was detected by proton when running with the integrated GPU disabled?

No, I have only verified that only one GPU is being detected via lspci. What do I need to do to verify that through proton?

Setting VK_ICD_FILENAMES to only the discrete GPU should already be enough to ensure that it's the only one

To my understanding, since the iGPU is a Radeon Vega integrated into the 5700G, it would use the same driver as the 7900XTX dGPU, no?

[gonneman]

@saghm Do you have any other ideas as to what I could try to get BG3 running?

[saghm]

Unfortunately, the only other thing I can think of is that it seems like some people have had issues with Steam installed via flatpak instead of a native package, but otherwise I'm pretty much out of ideas.

[syrrurg]

I have a very similar black screen hanging problem with an Optimus MSI gaming laptop.
TLDR: It works only on Ubuntu 24.04. Main goal is to run on Fedora.

Basic laptop spec.:

• CPU: Intel Core Ultra 9 185H
• iGPU (GPU1): Intel Meteor Lake-P [Intel Arc Graphics]
• dGPU (GPU0): NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile]

So I think the most important information is that it works on Ubuntu perfectly fine with different combinations of:

• Ubuntu / Kubuntu 24.04
• GNOME / KDE
• Wayland / X11
• DX11 / Vulkan
• default Ubuntu NVIDIA driver (535) / .run installer of 555 beta
• different versions of Proton, but mainly the Experimental version

But in other distros it's not working, the game window just showing a black screen with a mouse cursor (BG3 game style cursor, not the default OS style).

I tried many combinations, based on a lot of recommendation what I can found on the Internet:

• OpenSUSE Tumbleweed / Fedora / Nobara / EndevaourOS / Garuda (latest, updated versions)
• GNOME / KDE
• Wayland / X11
• DX11 / Vulkan
• default or officially recommended NVIDIA drivers by the distribution (mainly 550.x), but also tried the .run 555 beta and even .run 535 (same version as in Ubuntu)
• different versions of Proton, but mainly the Experimental version
• different Steam game command line parameters
• with or without Larian launcher
• tinkering with NVIDIA related OS settings (e.g. PRIME offload, disabling Intel Arc)
• (I also tried to start with a clear pfx folder and reinstalled the game a few times.)

Steam was always the distro provided package (or in the case of Ubuntu, the .deb package from the Steam website) and not Flatpak.

Game is using the NVIDIA card, based on the output of 'nvidia-smi' or 'nvtop'.

In-game graphic settings looks irrelevant, I tried to load with different graphicSettings.lfx files, like:

• full screen or windowed mode
• low graphics without v-sync and DLSS/DLAA etc., or everything on max

Right now I'm on:

• Operating System: Fedora Linux 40
• KDE Plasma Version: 6.1.0
• KDE Frameworks Version: 6.3.0
• Qt Version: 6.7.1
• Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit)
• Graphics Platform: Wayland

Here are the latest logs:

• steam-1086940_dx11.log
• steam-1086940_vulkan.log

"Not-So-Fun" fact: It's working with Ubuntu 24.04, OpenSUSE Tumbleweed and Fedora also, on an older Optimus MSI laptop, which has an NVIDIA RTX 3080 Max-Q / Mobile dGPU and an Intel Core i7-11800H CPU (Intel UHD Graphics iGPU)

---

Update: I recently realized something, before I posted the comment above. I don't remember that I tried this already or not, but right now:

• With the "eval $( echo "%command%" | sed "s/Launcher/LariLauncher.exe'.*/bin/bg3.exe'/" )" launch option and Proton 7, I can see the logos and the loading screen, but it stucks at 95%.
  steam-1086940_vulkan-evalsed-proton7.log

[gonneman]

Unfortunately, the only other thing I can think of is that it seems like some people have had issues with Steam installed via flatpak instead of a native package, but otherwise I'm pretty much out of ideas.

That did it! I installed Steam via Flatpak and now BG3 works flawlessly (on ultra settings with DX11 to boot!). I'm feeling a little silly now for not trying this before posting here...
Thanks for taking the time to help. I really appreciate it.

[saghm]

ow for not trying this before posting here...

Honestly, I feel like I should have thought of asking that earlier before asking you to try so many other things, but I'm thrilled that it's working for you now :)

[switch-blade-stuff]

Flatpack version does seem to work fine, I do feel quite stupid for not trying that earlier lol. Although now it is more confusing as to why it doesn't work via the native package