Run through Bottles (flatpak) on Fedora Silverblue, AMD GPU, lutris-GE-Proton8-26

edit edit:

  • 6.8.8-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC
  • Radeon RX 6700 XT
  • amd-gpu-firmware-20240410-1.fc39.noarch
  • amd-ucode-firmware-20240410-1.fc39.noarch
  • xorg-x11-drv-amdgpu-23.0.0-2.fc39.x86_64

Neither bg3.exe nor bg3_dx11.exe launch the game for me, so I use the LariLauncher.exe.

  • with DirectX11 the game starts but there are bad textures, including on the very first rendered screen.
  • with Vulkan I get this error and the game crashes still at this loading screen.

The launcher complains about data mismatch but Heroic Launcher which I use to download my gog files apparently thinks it is fine. Although, the “Verify and Repair” button takes only couple of seconds.

Any ideas please?

  • mox
    link
    fedilink
    English
    97 months ago

    I suggest avoiding the Vulkan build. It has been crashy in most BG3 releases, including the current one, I think.

    For the dx11 build, you might get more help if you post your kernel and amdgpu firmware versions, GPU model, and screen shots showing the bad textures.

    It’s also worth browsing the Proton comments to see if anyone else has encountered the same problems.

    • @thlcnOP
      link
      English
      1
      edit-2
      7 months ago

      I will rather skip the Vulkan version then, thank you. I will update the post with version information but how do I learn the amdgpu firmware versions please?

      • Para_lyzed
        link
        English
        3
        edit-2
        7 months ago

        Since you’re using Fedora Atomic, I’ll give you instructions for rpm-ostree:

        Run rpm-ostree status and find the deployment with the dot to the left of it. Example output:

        State: idle
        Deployments:
        ● fedora:fedora/40/x86_64/kinoite
                          Version: 40.20240509.0 (2024-05-09T00:47:51Z)
                       BaseCommit: 2f8263a33190c4e1320233aebbdc8f337b0a6abcba371d4870ae43fba33aea62
                     GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
                  LayeredPackages: akmod-nvidia akmods asusctl asusctl-rog-gui libratbag-ratbagd mullvad-vpn rpmdevtools
                                   supergfxctl virt-manager xorg-x11-drv-nvidia
                    LocalPackages: rpmfusion-free-release-40-1.noarch rpmfusion-nonfree-release-40-1.noarch
        
          fedora:fedora/40/x86_64/kinoite
                          Version: 40.20240507.0 (2024-05-07T00:44:22Z)
                       BaseCommit: c7fb680111ecf1736e473cf6f9169f69e5f2ec6b50814f7017bd6f9f3c1bdaf2
                     GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
                  LayeredPackages: akmod-nvidia akmods asusctl asusctl-rog-gui libratbag-ratbagd mullvad-vpn rpmdevtools
                                   supergfxctl virt-manager xorg-x11-drv-nvidia
                    LocalPackages: rpmfusion-free-release-40-1.noarch rpmfusion-nonfree-release-40-1.noarch
        

        First one has a dot next to it, which means it’s the active version. Copy the value after “BaseCommit:” (in my case it is 2f8263a33190c4e1320233aebbdc8f337b0a6abcba371d4870ae43fba33aea62)

        Run rpm-ostree db list <paste commit hash here> | grep amd. Example output (my command was rpm-ostree db list 2f8263a33190c4e1320233aebbdc8f337b0a6abcba371d4870ae43fba33aea62 | grep amd):

        amd-gpu-firmware-20240410-1.fc40.noarch
        amd-ucode-firmware-20240410-1.fc40.noarch
        

        In my case, running the most recent update on Fedora Atomic KDE, it looks like I’m running version 20240410-1 of amd-gpu-firmware. Yours may vary depending on what update you’re on.

        • @thlcnOP
          link
          English
          17 months ago

          nice write up, thank you!

      • mox
        link
        fedilink
        English
        1
        edit-2
        7 months ago

        how do I learn the amdgpu firmware versions please?

        I don’t know Fedora, but I expect there’s a dnf command that would tell you what package owns the files in /lib/firmware/amdgpu . The version of that package would probably correspond to the upstream firmware version.

        • Para_lyzed
          link
          English
          37 months ago

          Since they’re running Fedora Atomic, the commands are through rpm-ostree, as dnf is disabled. I’ve provided the relevant instructions.

  • kid2908
    link
    fedilink
    English
    67 months ago

    Have the same issue after an system update on arch a few day ago. Today update had it fixed.

    Seem like an issue with glibc.

    • @thlcnOP
      link
      English
      07 months ago

      That would require the Steam runtime. I will try some other runners in version 7 first, I expect they should have the same patches applied:

  • @[email protected]
    link
    fedilink
    English
    67 months ago

    I ran it (bg3.exe) through the latest vanilla proton (9.0.1 I think?) earlier today and it had no issues. I used the experimental version for character creation and it had some fucked up textures (color banding mostly), but after switching it ran perfectly in the stable version. I’m running thru steam on a nvidia gpu, so hopefully on amd you’ll be fine if you try that.

    • @thlcnOP
      link
      English
      47 months ago

      lutris-GE-Proton8-26

      is the latest version available within Bottles, I will look into newer versions!

      • @dot0
        link
        English
        27 months ago

        GloriousEggroll, the person who makes ProtonGE, also makes an entire Fedora-based distro called Nobara. it has a lot of gaming-focused changes and comes with a utility which lets you install all sorts of different versions of Proton - both vanilla and GE modded.

        obviously switching distros is a big deal but like worst case scenario you could give that a try?

  • Rodneyck
    link
    fedilink
    English
    4
    edit-2
    7 months ago

    It is not only BG3, it also happens in Skyrim SE, Fallout 4, nothing but Vulkan errors. I turn off Vulkan in Lutris and they run.

    Some say the kernel is the issue, but I have tried a few different ones and same issue. I am at a loss. I am running Arch, AMD GPU.

    • @aksdb
      link
      English
      27 months ago

      Do you maybe use amdvlk instead of mesa?

  • @dodos
    link
    English
    47 months ago

    Been a long time since I played and I’m on Nvidia, but if I recall correctly vulkan never worked for me on Linux. Give dx a try.

    • @thlcnOP
      link
      English
      1
      edit-2
      7 months ago

      Long time for me too :) but the game ran here almost perfectly sometime after its release, at high or even maximum settings at that.

      (I don’t remember the version I used, though)

  • Gamers_Mate
    link
    fedilink
    17 months ago

    I haven’t tried Baldur’s gate but to get the lord of the rings bfme2 to run I set the runner to wine-ge-8-26-x86_64 and it started working in Lutris.

    I also tested bottles before I moved to Lutris and there should be runner settings for graphics to be translated to Vulkan from directx.
    I am using Linux Mint though which is debian based so idk if you have to do things different for wine in fedora.

    • @thlcnOP
      link
      English
      17 months ago

      there should be runner settings

      Oh yes, there are! They are all nicely organized, with short description using the Gnome UI language. I prefer Bottles so much to the other launchers but I could get some games to run in the past only using Lutris with its install script database…

  • @thlcnOP
    link
    English
    17 months ago

    The game used to work some half year ago. After the massive update I deleted the files and redownloaded the whole game anew