VerifiedShow Details
Unknown
Works well but launcher is annoying
Everything works well out of the box, but I'd recommend skipping the launcher by adding --skip-launcher to steam's launch options
Works almost perfectly. Totally playable. Has a minor graphical issue with the mouse and launcher being too small (only at 4K).
--skip-launcher --vulcan
Mouse pointer is too small, game is in 4K, pointer looks to be 1080p
Cannot pick up items while holding RIGHT ALT key (to show the items)
The game works flawlessly out of the box using Proton --- no tweaks needed to get started.
WINEDLLOVERRIDES="DWrite.dll=n,b" %command% --skip-launcher --dx11
- Added the '--skip-launcher --dx11' launch options for convenience.
- The in-game mod manager works out of the box with no additional setup.
- I got BG3 Mod Manager working via Bottles
- Add d3dcompiler_47 and dotnetcoredesktop8 as dependencies into the proton prefix.
- Add 'WINEDLLOVERRIDES="DWrite.dll=n,b" %command%' to get the BG3 Script Extender working properly
- Run BG3 Mod Manager through bottle and use as normal
--skip-launcher --vulkan SDL_VIDEODRIVER=x11
Screen would go to all black a few times per minute no matter what options I tried. Fixed with SDL_VIDEODRIVER=x11
Framerate dropped after about an hour of gameplay: rotation of the camera became hyper sensitive and choppy. Adding game launch options resolved the issues.
Works perfectly fine on Arch with Hyprland!
IMPORTANT FOR MODDING: I hosted a game for 4 friends playing on Windows using Party Limit Begone and the Multiplayer Patch that allows you to play with more than 4 people at once. Worked without issue!
Crashes right after first splash screen and before main menu
SLD_VIDEODRIVER=
--skip-launcher --dx11
The tinkering was just to remove the launcher and start the superior dx11 executable
No issues at all
Worked without any issue or tinkering needed, just downloaded and ran
Overall perfect
Limited to 45fps
Textsize can be adjusted
One time textures were not loading
touching the screen leads to the game switching to "pc-mode"
Works out of the box, no thinkering required. I added the skip launcher option, but not necessary if not comfortable or dont want to.
--skip-launcher
Some crackling while playing.
Please go ahead! This is amazing out of the box, you should not have any issues.
Smooth as butter, performs even better on Linux than it does on my Windows install.
I was experiencing tons of random crashes when I tried to play this on Windows, so I decided to try it on my main Bazzite install and somehow it just... works 1000 times better. I've been able to start a new playthrough without any crashes that don't make sense (I've crashed once or twice due to some mod issues) Overall though I completely recommend trying this out on your system.
PROTON_LOG=1 WINEDLLOVERRIDES="xaudio2_7=n,b" DXVK_ASYNC=1 DXVK_HUD=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 gamemoderun mesagit-enable %command% --skip-launcher
Minor yet common artifacts. Black squares flash around the screen regularly during dialogue scenes. Exclusively in the background and never on the characters themselves. Tolerable.
After playing for a few hours the framerate begins to destabilize but never below 30 FPS.
GE-Proton-10-1 and the git mesa drivers solved the weird issues I was having before (process zombification, crashing at various points during launch, dx11 override, audio issues). See about mesa git below.
IMPORTANT: The mesagit-enable statement in the launch options is a CUSTOM SCRIPT I made that allows me to override game launches to force the usage of the git mesa drivers. If the launch options don't work without it for you, then download and extract the git mesa drivers in an /opt/ subfolder (ex: /opt/mesa-git/) and create the script. Here's a simplified version of mine:
#!/bin/bash
# Common mesa-git paths
export LD_LIBRARY_PATH="/opt/mesa-git/lib/x86_64-linux-gnu:$LD_LIBRARY_PATH"
export LIBGL_DRIVERS_PATH="/opt/mesa-git/lib/x86_64-linux-gnu/dri"
export VK_LAYER_PATH="/opt/mesa-git/share/vulkan/explicit_layer.d"
export GALLIUM_HUD="fps,cpu+GPU-load,temp"
VULKAN_DRIVER="radv"
VK_ICD_RADV="/opt/mesa-git/share/vulkan/icd.d/radeon_icd.x86_64.json"
VK_ICD_AMDVLK="/etc/vulkan/icd.d/amd_icd64.json"
exec "$@"
--skip-launcher --dx11
Didn't work with the "gamemoderun %command%" launch option. Crashed just after going through the launcher and the screen going black for a second.
Works fine without the "gamemoderun %command%" launch option.
LD_PRELOAD="" scb -f -W 3440 -H 1440 --hdr-enabled -- %command% --skip-launcher
scb for steam overlay. you can probably update scopebuddy default config and remove some of these flags (docs here https://docs.bazzite.gg/Advanced/scopebuddy/) but I haven't bothered. hdr works great. First few launches were rough and crashed, but haven't had an issue since
On proton 10beta I got quite low fps (20ish). On experimental its close to windows performance
Had to install dependencies and create two scripts that must be run back-to-back to close it after getting it to run well ONCE. Patience.
PROTON_LOG=1 WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command% --skip-launcher
Go to /usr/share/vulkan/icd.d and rename dzn_icd.x86_64.json by adding .ghost or something else.
Reboot, run the game. If you get a working instance without issues or already had one, BACK IT UP.
Had to use bash alias scripts to nuke bg3 or any winservers it uses, and another one to restore the backup. Aliases:
alias nukebg3='pkill -f bg3; pkill -f wine; wineserver -k; pkill -f wineserver; pkill -f Proton'
alias restorebg3='rsync -a --delete ~/.bg3-working-pfx ~/.steam/steam/steamapps/compatdata/1086940/pfx'
This only works IF I run nukebg3 while bg3 is running and using bg3restore after. IF YOU:
- close the game with
nukebg3and then dorestorebg3it will start normally and run
ELSE IF YOU:
don't use
nukebg3to close the game, the next time you try to run it the process zombify regardless of if you usedrestorebg3don't use
restorebg3after nuking the game, it will start but have no sound
IF that doesn't work TRY rebooting Steam before restoring
Game would start up either mute or with partial audio (menu and dialogue only)
Closing the game on fullscreen makes it crash on subsequent boots
Game had lots of weird bugs around getting it to start. Audio issues as mentioned, crashing at different stages before reaching the main menu, and process zombification. See tinker steps above.
This fix is ugly, but it works.
For some reason closing a working instance of the game ruins something inside the ~/.steam/steam/steamapps/compatdata/1086940/pfx folder or its subfolders. I do not yet know what it is. Restoring the pfx folder to a version of it that got the game to work correctly is what makes the "nuke then restore" tech-ritual work. Closing the game does SOMETHING to the wine profile. So I'm trying to find out what.
The game also ignores any --vulkan, --dx11 or --force-//vulkan//dx11// flags in its launch options. I tried getting either renderer to work and after so much tinkering I got a working instance of vulkan with the specified launch options.
Persistent audio and run issues with Proton Experimental, Hotfix, 10.0-1, 9.0-4. 8.0-5 and GE Proton 9-27 and multiple launch options. Help.
PROTON_LOG=1 %command% --skip-launcher --vulkan
After installing it the game runs fine. Any following attempts to run the game either fail/freeze or run but no sound, or only menu and dialogue sound. Using Proton Experimental worked for a bit, if it had no audio I just had to exit and run it again and it'd work as expected. Now though it either: crashes immediately upon running, "starts" and freezes (all process stats stuck forever in N/A), or it runs without any audio or sound. Before it would run with only menu audio and dialogue, now it's not even that much. The only consistent "fix" I have managed is reinstalling, but I don't think anyone wants to reinstall a 100+ GB game before every every session.
Please help.
Had to update Nvidia drivers to Debian Bookworm's latest stable, would not go into the first menu on DX11 otherwise, Vulkan wouldn't start.
WINEDLLOVERRIDES="DWrite.dll=n,b" PROTON_NO_ESYNC=1 %command% --skip-launcher --dx11
Definetely runs slower than it did on Windows on the same hardware
Works great out of the box, the launch options didn't change the experience too much but could useful to you.
gamemoderun %command% --skip-launcher
Change the launch options if you feel like the game is running slower than it should. If not, I wouldn't bother with it.
Runs perfectly using Vulkan
Some artifacts (coloured blotches) in video sequences, but not in game.
Updating nvidia drivers to 550.144-03 caused the game to get stuck at 100% in the initial loading screen before the main menu. Had to revert to the previous version to fix it.
--skip-launcher
Game ran flawlessly from beginning to end. Used Vulkan. Never had a single issue.
Had issues with stuttering but fixed it quickly with launch options, other than that very good performance and no other issues so far
LD_PRELOAD="" %command% --skip-launcher
Stuttering initially after 30-50 min of gameplay, fixed with the launch options.
Works out of the box
I've had several extended gaming sessions in BG3 over the last few weekends with no issues. In the majority of the sessions I am the host running 1 of 2 campaigns we are currently playing through with groups of 3 - 4 people. I've also had a session or so where I joined someone else hosting the game as well. Next test with the latest kernel update for Fedora 42 won't be until likely this weekend some time, but prior to that all the updates for Fedora 42 have worked just fine over the last 3 or 4 weekends. I just use keyboard and mouse for gameplay on BG3, so I can't add anything for controller support.
nvidia-offload env -u SDL_VIDEODRIVER %command% --skip-launcher
I had problems with wayland but the launch options solved it.
PROTON_LOG=1 %command% --skip-launcher --vulkan
Used %command% in launch options, otherwise the game did not run.
Renamed InstallScript.vdf file from /mnt/GamesDrive/SteamLibrary/steamapps/common/Baldurs Gate 3. Otherwise the game would get stuck on "Installing redistributables".
Also, ALT + Click is important in the game (alt shows name of items on the ground and you can click on the text), In Linux Mint (cinnamon) I had to disable preference: "Windows > Behavior > Special key to move and resize windows".
After that it's perfect.
Runs very well even with Youtube in the background
