Skip to content

Baldur's Gate 3 (1086940) #4243

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
cwebster2 opened this issue Oct 6, 2020 · 535 comments
Open
2 tasks done

Baldur's Gate 3 (1086940) #4243

cwebster2 opened this issue Oct 6, 2020 · 535 comments
Labels
Game compatibility - Unofficial Games not expected to work without issues .NET Uses the .NET framework

Comments

@cwebster2
Copy link

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 kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Oct 6, 2020
@kisak-valve kisak-valve changed the title Baldurs Gate 3 - 1086940 - Does not start Baldurs Gate 3 (1086940) Oct 6, 2020
@kisak-valve kisak-valve added the .NET Uses the .NET framework label Oct 6, 2020
@kisak-valve
Copy link
Member

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
Copy link
Author

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
Copy link

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

@olav-valle
Copy link

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
Copy link

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
Copy link

przmkg commented Oct 6, 2020

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
Copy link

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

@olav-valle
Copy link

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

@przmkg
Copy link

przmkg commented Oct 6, 2020

@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
Copy link

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

1086940_20201006233021_1

Vulkan_Log.zip

@kisak-valve
Copy link
Member

kisak-valve commented Oct 6, 2020

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.

@kisak-valve kisak-valve added AMD RADV Possible driver issues with RADV Mesa drivers Possibly involves an issue with a Mesa video driver labels Oct 6, 2020
@alosarjos
Copy link

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
Copy link
Contributor

GloriousEggroll commented Oct 6, 2020

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
Copy link

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
Copy link

ldust667 commented Oct 7, 2020

@MrCraigen what OS are you on?

@trickyholley
Copy link

@GloriousEggroll Your patch worked like a charm; thanks!

@1beb
Copy link

1beb commented Oct 7, 2020

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

image

@cwebster2
Copy link
Author

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
Copy link
Author

Game works great!

@SET001
Copy link

SET001 commented Oct 7, 2020

@1beb this gives me the error

Unknown arg dotnet48

@MrCraigen
Copy link

@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
Copy link

SET001 commented Oct 7, 2020

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

@ZarathustraDK
Copy link

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
Copy link

Traxmaxx commented Oct 7, 2020

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

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

@ArcanePhysics
Copy link

@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

@switch-blade-stuff
Copy link

@huutaiii not sure what could be the cause of that but as a workaround you could try re-mapping the mouse buttons externally

@huutaiii
Copy link

huutaiii commented Jul 19, 2024 via email

@switch-blade-stuff
Copy link

I suppose I can have the mouse re-mapped only while playing, it seems tedious however.

You could enable the mapping when you start the game by editing the command option in steam, but it is indeed more work than it should be.

@gonneman
Copy link

gonneman commented Jul 21, 2024

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 :)

The game has been working perfectly with DX11 for 3 weeks and now it suddenly doesn't any more.
I'm not sure what changed and I don't think the were as an update for the graphics drivers. Would you mind having a look at the logs again @saghm?

Edit: Sorry, I should add what exactly is going wrong (and I attached the wrong logs previously). I can start the BG3 launcher without any problems. Then when I click start with either DX11 or Vulkan I get a black screen and the game hangs. I can't exit it with killing the process. I've tried this with Proton Experimental. Older versions of Proton seem to struggle to even start the launcher.

Here is the log for DX11, which was working perfectly until a few days ago.
BG3_DX11_new.log
It looks to me like it is trying to use the open source mesa drivers and then complaining that the proprietary drivers are being used. Is there a way to make it use the proprietary drivers?

@Celti
Copy link

Celti commented Jul 23, 2024

Although now it is more confusing as to why it doesn't work via the native package

@switch-blade-stuff Do you have SDL_VIDEODRIVER=wayland set in your environment? I just ran into the “Failed to collect displays” error and unsetting that resolved that issue. Using the Flatpak would fail to pick that variable up from your environment, also resolving it.

@switch-blade-stuff
Copy link

Although now it is more confusing as to why it doesn't work via the native package

@switch-blade-stuff Do you have SDL_VIDEODRIVER=wayland set in your environment? I just ran into the “Failed to collect displays” error and unsetting that resolved that issue. Using the Flatpak would fail to pick that variable up from your environment, also resolving it.

I do have that one set. Wouldn't un-setting it cause issues with native wayland stuff and SDL though?

@Celti
Copy link

Celti commented Jul 23, 2024

I do have that one set. Wouldn't un-setting it cause issues with native wayland stuff and SDL though?

I rather meant unsetting it within Steam; e.g., SDL_VIDEODRIVER='' %command%. As for the game itself, it's running within XWayland, so it's looking at the X11 environment and not the Wayland one, which is where the problem comes from — you've told it to use Wayland, and it can't.

@ImDevinC
Copy link

ImDevinC commented Jul 27, 2024

I am using Steam Flatpak (although have test non-flatpak) and can't get past the loading screen sticking at 67%. I've also tried both DX and Vulkan with no success. I'm attaching a log, where I can clearly see something crashing at the end, but I don't know what it is. Perhaps someone has an idea what's happening?
I've tried a lot of troubleshooting steps so far as well with no change:

  • Since I have dual GPU, I've tried forcing just the nvidia one
  • Tried both vulkan and DX
  • Tried multiple different versions of Proton (GE, 9, experimental, hotfix)
  • Tried removing the game entirely and reinstalling
  • Tried both Flatpak and non-flatpak

Apparently I can't attach a log, so here's the pastebin: https://pastebin.ai/g40tfbamiy

neofetch 
                   -`                    devin@bean 
                  .o+`                   ---------- 
                 `ooo/                   OS: Arch Linux x86_64 
                `+oooo:                  Host: OMEN Transcend Gaming Laptop 14-fb0xxx 
               `+oooooo:                 Kernel: 6.10.0-arch1-2 
               -+oooooo+:                Uptime: 3 days, 7 hours, 18 mins 
             `/:-:++oooo+:               Packages: 905 (pacman), 27 (flatpak) 
            `/++++/+++++++:              Shell: zsh 5.9 
           `/++++++++++++++:             Resolution: 2880x1800 
          `/+++ooooooooooooo/`           DE: Xfce 4.18 
         ./ooosssso++osssssso+`          WM: Xfwm4 
        .oossssso-````/ossssss+`         WM Theme: catppuccin-frappe-dark 
       -osssssso.      :ssssssso.        Theme: catppuccin-frappe-dark [GTK2/3] 
      :osssssss/        osssso+++.       Icons: Tela-circle-dark [GTK2/3] 
     /ossssssss/        +ssssooo/-       Terminal: tmux 
   `/ossssso+/:-        -:/+osssso+-     CPU: Intel Ultra 9 185H (22) @ 4.800GHz
  `+sso+:-`                 `.-/+oso:    GPU: Intel Arc Graphics] 
 `++:.                           `-/+/   GPU: NVIDIA GeForce RTX 4070 Max-Q / Mobile 
 .`                                 `/   Memory: 5169MiB / 31666MiB

@saghm
Copy link

saghm commented Jul 28, 2024

Here is the log for DX11, which was working perfectly until a few days ago. BG3_DX11_new.log It looks to me like it is trying to use the open source mesa drivers and then complaining that the proprietary drivers are being used. Is there a way to make it use the proprietary drivers?

You can set the env var VK_ICD_FILENAMES to specify which driver to load. (I think there's a newer env var that's supposed to supersede it, but last time I tried using it I couldn't get it working). Setting it to the absolute paths of the ICD files separated by : will override which driver is used. On Arch Linux, they're located in /usr/share/vulkan/icd.d, but I'm not sure if that will be the same on other distros.

If you want to verify that you're specifying it correctly before you paste it into the launch options, you can run vulkaninfo with it set to verify that the correct driver is found. As an example, here's the output of it on my desktop specifying the open source drivers and the proprietary drivers respectively:

→ VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json vulkaninfo | grep driverID
        driverID        = DRIVER_ID_MESA_RADV
        driverID                                             = DRIVER_ID_MESA_RADV
        driverID        = DRIVER_ID_MESA_RADV
        driverID                                             = DRIVER_ID_MESA_RAD
→ VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd32.json:/usr/share/vulkan/icd.d/amd_pro_icd64.json vulkaninfo | grep driverID
        driverID        = DRIVER_ID_AMD_PROPRIETARY
        driverID                                             = DRIVER_ID_AMD_PROPRIETARY
        driverID        = DRIVER_ID_AMD_PROPRIETARY
        driverID                                             = DRIVER_ID_AMD_PROPRIETARY

Using the paths above as examples, the game can be forced to run with the proprietary driver by setting the launch parameters to VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/amd_pro_icd32.json:/usr/share/vulkan/icd.d/amd_pro_icd64.json %command%.

@gonneman
Copy link

I can find *.json files in two locations.

  1. /etc/vulkan/icd.d/nvidia_icd.json
  2. /usr/share/vulkan/icd.d/ which contains intel_hasvk_icd.i686.json intel_hasvk_icd.x86_64.json intel_icd.i686.json intel_icd.x86_64.json
    I'm guessing the formers is what I want.

Regarding setting the environment variable, I think I might be misunderstanding you there. If I run
export VK_ICD_FILENAMES=/etc/vulkan/icd.d/nvidia_icd.json
and then
vulkaninfo
I get this output
vk.log
As far as I can see it does not contain a line with "VK_ICD_FILENAMES" in it. Did I misunderstand your suggestion?

If I try and launch BG3 with VK_ICD_FILENAMES=/etc/vulkan/icd.d/nvidia_icd.json %command% then nothing happens. The game is listed as running in Steam but no launcher window ever appears.

@saghm
Copy link

saghm commented Jul 29, 2024

As far as I can see it does not contain a line with "VK_ICD_FILENAMES" in it. Did I misunderstand your suggestion?

I think you did. The example I did was grepping the output of vulkaninfo for driverID after setting VK_ICD_FILENAMES before running it; it won't appear in the log output itself. Grepping your attached log shows that the driverID is in fact being set:

→ grep driverID vk.log
        driverID                                             = DRIVER_ID_NVIDIA_PROPRIETARY

If I try and launch BG3 with VK_ICD_FILENAMES=/etc/vulkan/icd.d/nvidia_icd.json %command% then nothing happens. The game is listed as running in Steam but no launcher window ever appears.

Can you attach the game's logs (both with the flatpak version of Steam and the native Version)?

@gonneman
Copy link

gonneman commented Aug 1, 2024

I see. For completeness here are the outputs of vulkaninfo before and after setting VK_ICD_FILENAMES to /etc/vulkan/icd.d/nvidia_icd.json.
vkinfo_pre_export.log
vkinfo_post_export.log

I don't have enough disk space to install BG3 in both Flatpak and native Steam. Is it possible to have both use the same games directory? Here is the output of launching BG3 with PROTON_LOG=1 VK_ICD_FILENAMES=/etc/vulkan/icd.d/nvidia_icd.json %command% (with "trace" and "fixeme" lines removed).
BG3.log

@ptkato
Copy link

ptkato commented Aug 29, 2024

I got some silent crashes to desktop that happen only when I open a UI element that has a character preview like the inventory or trade screen, for examples. While it's not consistent it happens often enough that it's a nuisance.

steam-1086940.tar.gz

It seems that using the DirectX 11 executable, as opposed to the Vulkan one, made the game much more stable.

@Aperture32GLaDOS
Copy link

It seems like the toolkit doesn't play well with proton. You can get basic functionality with only wine and dotnet471, but with proton you get stuck at "starting services". I checked the logs, and found this error beneath some mscoree traces: 03d4:err:sync:RtlpWaitForCriticalSection section 00006FFFFFFB0360 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 03d4, blocked by 024c, retrying (60 sec)

@cschalle
Copy link

cschalle commented Sep 7, 2024

Game stopped working for me with patch 7. Using NVIDIA driver on Fedora Workstation.
The launcher runs fine, but if I pick Vulkan it says 'failed to create Vulkan device' and then Larian crash submission dialog appears. If I choose DX11 the screen just blinks black and then the Larian crash dialog appears.

Tried uninstalling and reinstalling too, but still same error.

Others games still work fine on the system like Total War:Wharhammer3 (windows version) and Elite Dangerous.

@jdsmall25
Copy link

I'm not able to run the BG3 Toolkit either. I followed the larian documentation to get setup and had a similar experience to aperture32glados. When I launch the toolkit, I set the data directory and it eventually freezes at "Starting Services..." the logs generated by the toolkit have a number of errors. I installed the dotnetdesktop6 package via proton tricks but that didn't seem to have an impact. This seems like it should work, its acting like missing a dependency?

@spannerman79
Copy link

I haven't had the chance to check, but looking over at https://steamdb.info/depot/1086941/ it has DotNetCore/windowsdesktop-runtime-6.0.11-win-x64.exe while winetricks (and in turn protontricks) actually uses a version higher windowsdesktop-runtime-6.0.19-win-x86.exe ( see https://github.com/Winetricks/winetricks/blob/master/src/winetricks#L10236-L10257 )

Could that make the difference? Was the update between those two versions of dotnet enough to break BG3?

@jdsmall25
Copy link

I was able to successfully install the .NET version that's packaged with the game and sadly I could see no discernible difference in behavior.

When running the app with PROTON_LOG=1 at the point of the crash it keeps trying to parse the config from several of the DLLs in the root folder and failing, resulting in repeating the segment below. Seems like its related to .NET as however these dlls are compiled mscoree can't read them properly?

307004.984:0124:0128:trace:mscoree:CLRMetaHost_GetVersionFromFile L"Z:$HOME\\.steam\\debian-installation\\steamapps\\common\\Baldurs Gate 3 Toolkit\\EoCPlugin.dll" 000000000041C510 000000000041C4E0
307004.991:0124:0128:trace:mscoree:CLRRuntimeInfo_QueryInterface 00006FFFFDCE67C0 {bd39d1d2-ba2f-486a-89b0-b4b0cb466891} 000000000041C9D8
307004.991:0124:0128:trace:seh:RtlAddGrowableFunctionTable 0000000022998838, 0000000022AD66F0, 0, 2, a3a55c0, a3a568b
307004.991:0124:0128:trace:seh:RtlGrowFunctionTable 000000001A95EA70, 1
307004.996:0124:0128:trace:seh:RtlGrowFunctionTable 000000001A95EA20, 3
307004.996:0124:0128:trace:seh:RtlGrowFunctionTable 000000001A95EA20, 4
307004.996:0124:0128:trace:mscoree:ReallyFixupVTable 0000000006C45A90,00000001010B0000,L"Z:$HOME\\.steam\\debian-installation\\steamapps\\common\\Baldurs Gate 3 Toolkit\\EoCPlugin.dll"
307004.996:0124:0128:trace:mscoree:CreateConfigStream (L"Z:$HOME\\.steam\\debian-installation\\steamapps\\common\\Baldurs Gate 3 Toolkit\\EoCPlugin.dll.config", 000000000041C458)
307004.996:0124:0128:warn:mscoree:get_runtime_info failed to parse config file L"Z:$HOME\\.steam\\debian-installation\\steamapps\\common\\Baldurs Gate 3 Toolkit\\EoCPlugin.dll.config", hr=80070002

Full log attached - I replaced my home dir with $HOME
steam-2934770.log

@jdsmall25
Copy link

I was able to get the editor to launch following the instructions on a different thread.

Basic steps that worked for me

  1. export WINEPREFIX=path to prefix
  2. Winetricks remove_mono
  3. Winetricks dotnet48
  4. wine reg add "HKCU\SOFTWARE\Microsoft\Avalon.Graphics" /v DisableHWAcceleration /t REG_DWORD /d 1 /f

Afterwards, the editor launches and is fairly responsive however the in game editor doesn't display. You can hear the editor loading the level sections as it plays the "loading" audio you'd hear in game.

I've done limited testing so far but the interesting part is that the asset preview seem to work fine and the AllSpark preview also works fine. So 3d rendering does work just not the main in game editor.

@mx-moth
Copy link

mx-moth commented Dec 5, 2024

BG3 wasn't working on my new laptop using any version of proton 8.0, proton 9.0, proton experimental, or proton GE. I did a bit of digging and came across this thread which seemed to be a similar issue and included a fix. The thread references a bug in wine which is fixed in wine 9.9. No version of proton includes wine 9.9. I added the patch from the thread as a patch to Proton-GE, compiled a new version, and everything worked flawlessly.

The issue suggested in the linked bug reports is that wine doesn't understand something about my CPU, and fails to report some critical information when the BG3 engine queries for it. This leads to the game stalling on the initial loading screen. A segfault is reported in the BG3 logs.

Applying this fix also made Divinity 2 Original Sin run on this machine, which makes sense as they are the same game engine.

System Information:

  • GPU: GeForce RTX 4050 Max-Q / Mobile
  • CPU: Intel Core Ultra 7 155H
  • Kernel version: 6.12.1
  • Link to full system information report: Gist
  • Proton version: Proton 9.0 (Stable), Proton Experimental, Proton GE

@foresto
Copy link

foresto commented Dec 5, 2024

@mx-moth That's interesting. I wonder if that GetLogicalProcessorInformation() patch would also stop the game from crashing when run with restricted CPU core affinity using something like taskset f bg3.exe.

Are you by any chance able to test this?

@mx-moth
Copy link

mx-moth commented Dec 6, 2024

@foresto I updated the launch parameters to include taskset f like so:

__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only taskset f %command% --skip-launcher --vulkan

and it showed a black screen when launching and never got any further. Before applying this patch I would variously get either a black unresponsive screen with the gauntlet mouse cursor, or the intro videos would play without sound and then the loading screen would never get past 95%. I don't think this patch makes taskset work unfortunately.

@foresto
Copy link

foresto commented Dec 6, 2024

Thanks for testing it. Just to be sure the f argument was valid, does your CPU have at least 4 cores?

@mx-moth
Copy link

mx-moth commented Dec 6, 2024

@foresto Yep, 16 cores, 2 threads per core. I successfully ran prime-run taskset f glxgears and saw the expected spinning gears running on my GPU. taskset -p $( pgrep glxgears ) reported the expected affinity mask for the process. My lscpu is attached:

lscpu output
Architecture:                         x86_64
CPU op-mode(s):                       32-bit, 64-bit
Address sizes:                        46 bits physical, 48 bits virtual
Byte Order:                           Little Endian
CPU(s):                               22
On-line CPU(s) list:                  0-21
Vendor ID:                            GenuineIntel
Model name:                           Intel(R) Core(TM) Ultra 7 155H
CPU family:                           6
Model:                                170
Thread(s) per core:                   2
Core(s) per socket:                   16
Socket(s):                            1
Stepping:                             4
CPU(s) scaling MHz:                   13%
CPU max MHz:                          4800.0000
CPU min MHz:                          400.0000
BogoMIPS:                             5992.00
Flags:                                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb intel_ppin ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdseed adx smap clflushopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect user_shstk avx_vnni dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req hfi vnmi umip pku ospke waitpkg gfni vaes vpclmulqdq rdpid bus_lock_detect movdiri movdir64b fsrm md_clear serialize arch_lbr ibt flush_l1d arch_capabilities
Virtualization:                       VT-x
NUMA node(s):                         1
NUMA node0 CPU(s):                    0-21
Vulnerability Gather data sampling:   Not affected
Vulnerability Itlb multihit:          Not affected
Vulnerability L1tf:                   Not affected
Vulnerability Mds:                    Not affected
Vulnerability Meltdown:               Not affected
Vulnerability Mmio stale data:        Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed:               Not affected
Vulnerability Spec rstack overflow:   Not affected
Vulnerability Spec store bypass:      Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:             Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:             Mitigation; Enhanced / Automatic IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS Not affected; BHI BHI_DIS_S
Vulnerability Srbds:                  Not affected
Vulnerability Tsx async abort:        Not affected

@OADINC
Copy link

OADINC commented Dec 31, 2024

Hi, I'm not sure if I should make a new issue for this but,
surround sound doesn't work for BG3. My speakers/receiver are in dolby digital/AC3 mode but I only hear stereo sound (If I play a video file with surround sound then it works just fine).
I saw a steam community thread that said to add a launch command. But this didn't work for me. Does any one have a suggestion?

@kisak-valve
Copy link
Member

Baulders Gate 3 will not launch

Issue transferred from #8387.
@Weber462 posted on 2025-01-11T04:06:33:

Compatibility Report

Baulder Gate 3
1086940

Computer Information:
Manufacturer: Giga Computing
Model: MZ73-LM0-000
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD EPYC 9534 64-Core Processor
CPU Family: 0x19
CPU Model: 0x11
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 3718 MHz
0 logical processors
128 physical processors
Hyper-threading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Supported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Supported
AVX512VNNI: Supported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System Version:
Freedesktop SDK 24.08 (Flatpak runtime) (64 bit)
Kernel Name: Linux
Kernel Version: 6.8.0-51-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12101011
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_0.20241024.105847
Client Information:
Version: 1733265492
Browser GPU Acceleration Status: Disabled
Browser Canvas: Unavailable
Browser Canvas out-of-process rasterization: Disabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Disabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Disabled
Browser Rasterization: Disabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Disabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Unavailable
Browser WebGL2: Unavailable
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 550.120
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x10de
DeviceID: 0x2782
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 2
Primary Display Resolution: 2560 x 1440
Desktop Resolution: 4480 x 1440
Primary Display Size: 23.98" x 13.98" (27.72" diag), 60.9cm x 35.5cm (70.4cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 12282 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Nvidia GPU a5 HDMI/DP
Memory:
RAM: 131072 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 1875626 MB
Largest Free Hard Disk Block: 1503206 MB
Storage:
Number of SSDs: 1
SSD sizes: 2000G
Number of HDDs: 0
Number of removable drives: 0

I confirm:

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

Forgive my ignorance if this is the incorrect place to post this. I cannot get Baulders Gate 3 (or divinity 2) to start. I have tried proton 9, experimental, hot fix.

Output with Proton Experimental
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_0.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_1.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_2.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_3.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_4.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_5.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_6.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_7.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_8.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_9.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine2_10.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_0.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_0.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_1.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_1.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_2.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_2.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_3.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_3.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_4.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_4.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_5.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_5.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_6.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_6.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\xactengine3_7.dll'
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
regsvr32: Successfully registered DLL 'C:\windows\\system32\\XAudio2_7.dll'
Fossilize INFO: Setting autogroup scheduling.
chdir "/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Baldurs Gate 3/bin"
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
Game Recording - would start recording game 1086940, but recording for this game is disabled
Adding process 3307 for gameID 1086940
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 3308 for gameID 1086940
WARNING: discarding _NET_WM_PID 5656 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 24724 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 26602 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5656 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 24724 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 26602 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
Adding process 3309 for gameID 1086940
Adding process 3396 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3397 for gameID 1086940
fsync: up and running.
Adding process 3398 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3399 for gameID 1086940
Adding process 3402 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3405 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3408 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3418 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3431 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3437 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3450 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Setting breakpad minidump AppID = 1086940
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561197972021254 [API loaded no]
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 3467 for gameID 1086940
pid 3400 != 3399, skipping destruction (fork without exec?)
Game Recording - game stopped [gameid=1086940]
Removing process 3467 for gameID 1086940
Removing process 3450 for gameID 1086940
Removing process 3437 for gameID 1086940
Removing process 3431 for gameID 1086940
Removing process 3418 for gameID 1086940
Removing process 3408 for gameID 1086940
Removing process 3405 for gameID 1086940
Removing process 3402 for gameID 1086940
Removing process 3399 for gameID 1086940
Removing process 3398 for gameID 1086940
Removing process 3397 for gameID 1086940
Removing process 3396 for gameID 1086940
Removing process 3309 for gameID 1086940
Removing process 3308 for gameID 1086940
Removing process 3307 for gameID 1086940
Output with proton 9.0-4
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Fossilize INFO: Setting autogroup scheduling.
chdir "/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Baldurs Gate 3/bin"
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Game Recording - would start recording game 1086940, but recording for this game is disabled
Adding process 7178 for gameID 1086940
ERROR: ld.so: object '/home/weber/.var/app/com.valvesoftware.Steam/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
Adding process 7179 for gameID 1086940
Adding process 7180 for gameID 1086940
WARNING: discarding _NET_WM_PID 5656 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 24724 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 26602 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 32874 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5656 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 24724 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 26602 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 32874 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5656 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 24724 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 5 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 26602 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 6340 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
WARNING: discarding _NET_WM_PID 32874 as invalid for X11 window - use specialized XCB_X11_TO_PID function!
Adding process 7267 for gameID 1086940
Adding process 7268 for gameID 1086940
Adding process 7269 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
fsync: up and running.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7270 for gameID 1086940
Adding process 7273 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7276 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7279 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7288 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7301 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7307 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7320 for gameID 1086940
wine: using kernel write watches, use_kernel_writewatch 1.
Setting breakpad minidump AppID = 1086940
Steam_SetMinidumpSteamID:  Caching Steam ID:  76561197972021254 [API loaded no]
wine: using kernel write watches, use_kernel_writewatch 1.
Adding process 7337 for gameID 1086940
pid 7271 != 7270, skipping destruction (fork without exec?)
Game Recording - game stopped [gameid=1086940]
Removing process 7337 for gameID 1086940
Removing process 7320 for gameID 1086940
Removing process 7307 for gameID 1086940
Removing process 7301 for gameID 1086940
Removing process 7288 for gameID 1086940
Removing process 7279 for gameID 1086940
Removing process 7276 for gameID 1086940
Removing process 7273 for gameID 1086940
Removing process 7270 for gameID 1086940
Removing process 7269 for gameID 1086940
Removing process 7268 for gameID 1086940
Removing process 7267 for gameID 1086940
Removing process 7180 for gameID 1086940
Removing process 7179 for gameID 1086940
Removing process 7178 for gameID 1086940

I am very new to linux. Other games to launch fine. (ex counterstrike, civ, stellaris).

Thank you in advance for the support and your patience.

-weber

@rickybrent
Copy link

I believe @Weber462's issue is caused by wine bug #56653 -- I ran into the an issue with the same symptoms on a newer laptop and using latest version of GE-Proton9-21 fixed it for me.

@Weber462
Copy link

@rickybrent Thank your for comment! Per your recommendation, I did try both GE-Proton 9-21 and 9-20 with no luck unfortunately. I would be open to any other recommendations.

@NathanTouchton
Copy link

I can repost this elsewhere if this is not the appropriate place, but I was instructed by Steam support to get help from the Proton GitHub page for assistance with this, and I saw this thread is already opened, albeit for a slightly different issue.

I haven't played this game in a long time, but when I played it earlier in 2024, it worked perfectly on this same computer with my same Arch Linux install. Now when I open it, it freezes every few seconds, which makes the game essentially unplayable. When it freezes, it does it for a full minute or two every time. The opening credits and main menu are the worst part. If I can get into the game, it doesn't freeze as often, but it still happens for a couple minutes each time it freezes. This is the only game having the issue. My hardware is fully capable of playing the game, and I've tried too much troubleshooting to list it all here (and I don't fully remember all the steps I've taken these last few months). I have tried multiple different versions of Proton, verifying the game files, reinstalling the game, deleting the compatdata folder for this game and relaunching, using many different launch options related to Proton/DXVK/Wine, resetting the settings, changing my display settings for KDE as well as various options in the game itself, using both DirectX and Vulkan, and probably other steps I cannot remember now. My drivers and everything are up to date, and this issue has persisted across multiple driver and kernel updates, so that does not seem to be the issue. I've also tried multiple different versions of Proton, and it happens with every one I've tried except for the ones that are so old the game doesn't work at all. The issue also happens with Proton GE (which I normally use by default anyway). I've tried looking through the Proton logs and searching the internet for any possible errors, but nothing is helping. I have also removed ClamAV to make sure it wasn't somehow preventing the game from accessing files it needs or something, but that didn't help. There's no other steps I can find from any source to troubleshoot this further, and ProtonDB and other sites pretty much say this game should be working (as it was for me until recently). The first time I noticed it not working was near the end of last year. I am at a complete loss as to what could be causing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Game compatibility - Unofficial Games not expected to work without issues .NET Uses the .NET framework
Projects
None yet
Development

No branches or pull requests