Closed leinardi closed 7 months ago
I'm wondering why it's looking in /usr/local
, how did you install?
Does the mangohud folder and library exist in /usr/local/lib
?
I installed it as it's stated in the README:
meson build
ninja -C build install
I've installed the same way 0.6.9-1 and 0.7.0-rc1.
This is the output of whereis mangohud
:
$ whereis mangohud
mangohud: /usr/local/lib/x86_64-linux-gnu/mangohud /usr/local/bin/mangohud
If it is useful, I could try to use git bisect to find the exact commit that caused the regression. I'm also available to do some remote debugging if needed.
Yeah I think a bisect would be very useful
Can you also show output of
tree /usr/local/lib/x86_64-linux-gnu/mangohud
Can you also show output of
tree /usr/local/lib/x86_64-linux-gnu/mangohud
Sure, here you go:
$ tree /usr/local/lib/x86_64-linux-gnu/mangohud
/usr/local/lib/x86_64-linux-gnu/mangohud
├── libMangoHud_dlsym.so
└── libMangoHud.so
1 directory, 2 files
I'll post the result of the git bisect asap.
That's probably from 0.6.9, can you show tree with rc1?
Bisect done (first bad commit 5754ca13ee2cdf19a76b4fc79dd914a58d6371f5):
$ git bisect good
5754ca13ee2cdf19a76b4fc79dd914a58d6371f5 is the first bad commit
commit 5754ca13ee2cdf19a76b4fc79dd914a58d6371f5
Author: FlightlessMango <flightlessmangoyt@gmail.com>
Date: Sat May 20 08:27:13 2023 +0200
vulkan manifest: set cpu_family in layer name
src/mangohud.json.in | 2 +-
src/meson.build | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
That's probably from 0.6.9, can you show tree with rc1?
$ tree /usr/local/lib/x86_64-linux-gnu/mangohud
/usr/local/lib/x86_64-linux-gnu/mangohud
├── libMangoHud_dlsym.so
├── libMangoHud_opengl.so
└── libMangoHud.so
1 directory, 3 files
Okay that's interesting What version is vulkan-loader?
It's the version 1.3.239.0-1
: https://packages.ubuntu.com/lunar/libvulkan1
Btw, I found a way to reproduce the issue without involving Steam:
$ mangohud vkcube
[2023-09-13 17:49:21.592] [MANGOHUD] [error] [overlay_params.cpp:815] Unknown option 'gpu_voltage (only works on AMD GPUs)'
Unable to repro with a fresh 23.04 in a docker container, work like normal
I have a 7900 XTX and unfortunately stock ubuntu doesn't support it, so you have to use LLVM 15+, Mesa 22.3+ and updated linux-firmware.
Is there any other test that I can do? Like I said, I'm also available to do a remote debug session via TeamViewer or some other desktop sharing tool.
FWIW vkcube and mpv --vo=gpu-next --gpu-context=waylandvk
work fine with mangohud 0.7.0-rc1 for me on NixOS using that same GPU. My vulkan-loader is at version 1.3.261.
Regarding ubuntu: I have had a ton of compatibility problems with the vulkan-sdk ppa. Most of the relevant things are in mainline ubuntu repos for a long time already so I'd generally recommend just installing the components you need manually from there. And kisak or oibaf ppa for mesa.
Regarding ubuntu: I have had a ton of compatibility problems with the vulkan-sdk ppa. Most of the relevant things are in mainline ubuntu repos for a long time already so I'd generally recommend just installing the components you need manually from there. And kisak or oibaf ppa for mesa.
Yep, that's exactly what I'm doing (I'm using kisak ppa and installed the linux-firmware manually.
In less than a month Ubuntu 23.10 will be released, hopefully that will fix the issue but, in case it doesn't, I hope this regression will be investigated more.
@leinardi can you repro with glxgears
?
Can you paste the output of VK_LOADER_DEBUG=all mangohud vkcube
as well?
can you repro with
glxgears
?
glxgears
works fine:
Can you paste the output of
VK_LOADER_DEBUG=all mangohud vkcube
as well?
sure, here you go: debug.txt
/usr/share/vulkan/implicit_layer.d/MangoHud.json
Should not be exist, probably not causing issues but it's not helping
Not sure, probably a leftover of a previous version? I'm using this software since long time.
Anyway, I moved it away but it still doesn't work: debug.txt
Please let me know if I can help with some other test.
@leinardi can you DM me on discord?
@flightlessmango I tried but we are not friends yet, I sent a request:
@leinardi I've added you
Had the same issue, lost 2 hours trying to figure out what was the problem, removing the mango hud call fixed it (Deus Ex would not start)
@Deus-nsf was this with mangohud rc1? What are your specs and OS?
I must admit, I didn't double check the version exactly, but I keep all my packages up to date, and it was working fine before, and removing the mango hud call immediatly fixed the issue.
I have a Ryzen 5800X 3D, a GTX 1080 Ti with Proprietary Drivers, 32 GB of RAM, all that running on a Debian 12 distro. Before that MangoHUD worked beautifully, no issues whatsoever :) Hope that helps!
@Deus-nsf Debian 12 (bookworm) is using an older version of MangoHud: https://packages.debian.org/bookworm/mipsel/mangohud
WORKAROUND
After a remote debug session with @flightlessmango we found out that the issue happens only if you manually run meson build && ninja -C build install
: if you install it via ./build.sh build install
it works fine :+1:
As requested, I'll leave the issue open for now.
Well at least I know how the find out if Mango hud is working or not
If the game is starting mangohud is not working If the game is not opening then mangohud works
I believe this issue has been resolved since a while back.
https://github.com/flightlessmango/MangoHud/issues/1119#issuecomment-2037822440 That's something that should be done in the Church
Describe the bug After upgrading from 0.6.9-1 to 0.7.0-rc1 many Steam games do not start anymore. The steam UI show the game as running but no window is shown and there are several errors related to MangoHud in console:
List relevant hardware/software information
To Reproduce Steps to reproduce the behavior:
Expected behavior The game starts and MangoHud is visible
Additional context Downgrading to 0.6.9-1 fixes the issue. MangoHud.conf
EDIT These are the steam console logs of the working 0.6.9-1:
EDIT 2
As workaround, install MangoHud via the build.sh script: