Over the weekend, I played Baldur's Gate 3 Early Access via steam. Awesome. The launcher doesn't work, which is a known problem, but running bg3.exe does.
However, with stock Fedora Workstation 33, after the intro when the menu is supposed to load, instead it's a quilt-like pattern of colored squares (and the mouse cursor a big block of the same).
I built and installed amdvlk-vulkan-driver from https://github.com/GPUOpen-Drivers/AMDVLK, though, and now it works flawlessly. Can someone who knows about this explain to me what the situation is? How does this external driver relate to what we have in Fedora?
Graphics card is an AMD Radeon Vega 56, btw.
On Mon, Oct 19, 2020 at 11:02 PM Matthew Miller mattdm@fedoraproject.org wrote:
Over the weekend, I played Baldur's Gate 3 Early Access via steam. Awesome. The launcher doesn't work, which is a known problem, but running bg3.exe does.
However, with stock Fedora Workstation 33, after the intro when the menu is supposed to load, instead it's a quilt-like pattern of colored squares (and the mouse cursor a big block of the same).
I built and installed amdvlk-vulkan-driver from https://github.com/GPUOpen-Drivers/AMDVLK, though, and now it works flawlessly. Can someone who knows about this explain to me what the situation is? How does this external driver relate to what we have in Fedora?
I'm adding in @David Airlie airlied@redhat.com who might know.
Graphics card is an AMD Radeon Vega 56, btw.
On 10/19/20 4:02 PM, Matthew Miller wrote:
I built and installed amdvlk-vulkan-driver from https://github.com/GPUOpen-Drivers/AMDVLK, though, and now it works flawlessly. Can someone who knows about this explain to me what the situation is? How does this external driver relate to what we have in Fedora?
There are four Vulkan driver options for AMD graphics chips at this time.
* Mesa RADV - LLVM (default up to version 20.1) Original Vulkan driver produced by the Mesa team. * Mesa RADV - ACO (default starting in version 20.2) Newest Vulkan driver produced by Valve. Fedora 33 ships with this. Try '/RADV_DEBUG=llvm' to use the older backend to see if it fixes your visual bug./ * AMDVLK Open source driver produced by AMD. * AMDGPU-PRO Closed source driver produced by AMD.
Hope that helps, Michael
On Tue, Oct 20, 2020 at 07:43:48AM -0500, Michael Cronenworth wrote:
There are four Vulkan driver options for AMD graphics chips at this time.
- Mesa RADV - LLVM (default up to version 20.1)
Original Vulkan driver produced by the Mesa team.
- Mesa RADV - ACO (default starting in version 20.2)
Newest Vulkan driver produced by Valve. Fedora 33 ships with this. Try '/RADV_DEBUG=llvm' to use the older backend to see if it fixes your visual bug./
- AMDVLK
Open source driver produced by AMD.
- AMDGPU-PRO
Closed source driver produced by AMD.
Ah, thanks. That clears it up. RADV_DEBUG=llvm, unfortunately, doesn't clear up the problem. Is there any way I can help identify what the problem is with the F33 default in a bug report or something so it can eventually be addressed?
On 10/20/20 4:42 PM, Matthew Miller wrote:
Ah, thanks. That clears it up. RADV_DEBUG=llvm, unfortunately, doesn't clear up the problem. Is there any way I can help identify what the problem is with the F33 default in a bug report or something so it can eventually be addressed?
I haven't tried the game yet, but I've read there is an EXE for Vulkan and one for D3D11. Obvious question: Are you using the Vulkan EXE?
If you are, I would submit a ticket to the mesa tracker against RADV.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/
I've found a recent, and very active, ticket for this game already: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3607
They were unable to even start the game, but the obvious caveat of different hardware may be in play with you if you are able to start it.
On Tue, Oct 20, 2020 at 05:16:55PM -0500, Michael Cronenworth wrote:
I haven't tried the game yet, but I've read there is an EXE for Vulkan and one for D3D11. Obvious question: Are you using the Vulkan EXE?
Yeah, fortunately it's pretty clear -- there is a bg3.exe and a bg3_dx11.exe.
If you are, I would submit a ticket to the mesa tracker against RADV. https://gitlab.freedesktop.org/mesa/mesa/-/issues/ I've found a recent, and very active, ticket for this game already: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3607
Awesome thanks.Oooh -- there's even a Larian engineer on that bug working in their spare time. That is AWESOME.
They were unable to even start the game, but the obvious caveat of different hardware may be in play with you if you are able to start it.
Looks like later down in the bug there are people seeing the same thing, or at least similar -- gets to the menu and then crashes. My crash happens to be visually dramatic rather than a black screen, but seems likely to be the same thing.
On Tue, Oct 20, 2020 at 2:44 PM Michael Cronenworth mike@cchtml.com wrote:
There are four Vulkan driver options for AMD graphics chips at this time.
- Mesa RADV - LLVM (default up to version 20.1) Original Vulkan driver produced by the Mesa team.
- Mesa RADV - ACO (default starting in version 20.2) Newest Vulkan driver produced by Valve. Fedora 33 ships with this. Try
Only the ACO (shader compiler) is produced by Valve, the RADV Vulkan driver is still the same (a community effort).
'/RADV_DEBUG=llvm' to use the older backend to see if it fixes your visual bug./
- AMDVLK Open source driver produced by AMD.
It's very unfortunate that we're in a situation where we have two open-source Vulkan drivers, and the one produced by the hardware vendor is actually not being used in most (any?) distributions. Dave Airlie can surely explain the reasons, I just read that AMDVLK is not great in being a first-class opensource citizen (allowing third-party pull requests, etc).
While both drivers should have a similar level of quality, there are of course bugs in both, as always. I think it would be quite helpful to have AMDVLK packaged as well in Fedora, so that users can install it and switch between AMDVLK and RADV when needed (Vulkan should support having both of them installed, and allow users to pick on of them before starting a program - not sure how, perhaps with an envvar). That would save some troubles to users who experience some bug like you do, and also it would help debugging (an easy check that it's not a hardware issue, for example).
On Wed, Oct 21, 2020 at 04:42:15PM +0200, Kamil Paral wrote:
While both drivers should have a similar level of quality, there are of course bugs in both, as always. I think it would be quite helpful to have AMDVLK packaged as well in Fedora, so that users can install it and switch between AMDVLK and RADV when needed (Vulkan should support having both of them installed, and allow users to pick on of them before starting a program - not sure how, perhaps with an envvar). That would save some troubles to users who experience some bug like you do, and also it would help debugging (an easy check that it's not a hardware issue, for example).
FWIW someone made a COPR. That's what I'm using.
https://copr.fedorainfracloud.org/coprs/tkov/amdvlk/builds/
desktop@lists.fedoraproject.org