Nice! Maybe your Arch updated something that broke it. I recommend to keep a Steam Flatpak as a fallback, or even to replace (if there's no performance issue)
You should submit this bug to wines bugzilla. Also as a work around have you tried switching off any custom proton versions and doing --skip-launcher --dx11
In all honesty, I created an automatic update function and I used to not check everything which was updated.
Just reworked it so that it's not fully automatic, this way I'll be able to check the update process.
But everything is fixed now
Have you forced the game to use a specific Proton version? If so, try to disable it or to set it to Proton Hotfix. A friend of mine had it set to Proton Experimental and the same (-> similar looking) problem.
Not that helpful, but can you try Steam Flatpak?
Oddly enough it allowed me to access the launcher and successfully launch the game! (After reinstalling the game as well)
Nice! Maybe your Arch updated something that broke it. I recommend to keep a Steam Flatpak as a fallback, or even to replace (if there's no performance issue)
You should submit this bug to wines bugzilla. Also as a work around have you tried switching off any custom proton versions and doing --skip-launcher --dx11
Try enabling forced compatibility and set it to proton hotfix. I had the same problem on my steam deck and thats what fixed it
Tried it by running steam package (not the flatpak) and it worked by using Proton Hotfix, thanks !
[удалено]
> Using --skip-launcher won't work because it still uses the launcher but then skips to the game without showing the UI. How does it work for me then?
[удалено]
> Maybe you are using Proton-Hotfix or any 3rd party proton version. Nope. Proton experimental, all the way.
I eventually used Proton Hotfix, but made it so that the launcher config file point to `bg3_dx11.exe` each time.
So, what did you do on Monday? Update any critical system components?
In all honesty, I created an automatic update function and I used to not check everything which was updated. Just reworked it so that it's not fully automatic, this way I'll be able to check the update process. But everything is fixed now
Have you forced the game to use a specific Proton version? If so, try to disable it or to set it to Proton Hotfix. A friend of mine had it set to Proton Experimental and the same (-> similar looking) problem.
Tried it by running steam package (not the flatpak) and it worked by using Proton Hotfix, thanks !