The Gallium3D Heads-Up Display (HUD) not available under Vulkan.
I want monitoring GPU information for DXVK and native vulkan games.
I have an experimental branch but it still requires a bunch of work, and I wouldn't recommend you to use it currently. Anyway, this is on our todolist for a long time.
(In reply to Samuel Pitoiset from comment #1)
> I have an experimental branch but it still requires a bunch of work, and I
> wouldn't recommend you to use it currently. Anyway, this is on our todolist
> for a long time.
Is your branch usable as is? Looks like it's missing radv_hud.c which makes it non buildable.
Lionel has written an overlay for vulkan, see https://gitlab.freedesktop.org/mesa/mesa/merge_requests/139
It has landed, so you can use it on Mesa master, and it will be in the 19.1 release (it might be in the 19.0 release already, not sure and I can't check from my phone).
Build it by setting `-D vulkan-overlay-layer=true`, and see src/vulkan/overlay-layer/README for instructions on how to use it:
[mikhail@localhost mesa]$ git branch -r --contains 20c370c6
origin/HEAD -> origin/master
looks like it merged only in master
The Vulkan overlay still doesn't allow to monitor GPU load/temperature, etc (as requested). We need a new extension for that.
(In reply to Samuel Pitoiset from comment #5)
> The Vulkan overlay still doesn't allow to monitor GPU load/temperature, etc
> (as requested). We need a new extension for that.
There is still an MR that brings new data (like pipeline statistics & timestamps) : https://gitlab.freedesktop.org/mesa/mesa/merge_requests/353
A delta(timestamps) / amount_of_time_per_frame would give a rough estimate of GPU utilization by the app.
For temperature we'll need another extension indeed.
Yeah, and the plan is to expose more driver queries in the future, like what the GALLIUM_HUD actually does.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/852.