Closed Saancreed closed 1 year ago
I believe this change was made because (at least on mesa) the version was incorrect. Also vkcube is probably one of the only places you will be able to observe this, since it's only vulkan 1.0 or something
Ah, okay, good to know. Initially I thought it's some more widespread problem because I've encountered a similar issue in one of the games I recently played but now it seems to be working again without any reverts required. So, whatever I saw back then is probably unrelated or just a one–off incident, but I'll try to pay more attention to this in case it happens again in the nearest future.
And if vulkan_driver
not working on 1.0 instances is a known / wontfix issue, feel free to just close this.
I believe this change was made because (at least on mesa) the version was incorrect. Also vkcube is probably one of the only places you will be able to observe this, since it's only vulkan 1.0 or something
with forza horizon 4 and in gta 5 using proton-ge still does not show the name of the vulkan
Seems to work on my end, re-open if this is still an issue
On the example of
MANGOHUD_CONFIG=vulkan_driver prime-run vkcube
:0.6.6-1:
0.6.7:
git bisect
reveals the following:Reverting that commit restores
vulkan_driver
's functionality on my machine, even on latestmaster
. Maybe we should keep that code path in one form or another as some sort of a fallback ifdriverInfo
turns out to be useless?