Closed RedSnt closed 1 month ago
Addendum, something I didn't think of before now: I tried downgrading to 51.13 and that made MangoHud start up correctly again, so seemingly it is a bug (or feature I'm overlooking?) introduced in 51.14. It's also present in 51.15.
Had the same issue. fix is to install Mangohud 24.08 specifically.
flatpak install mangohud
# now choose the 24.08 version from the list, for me it was the top option
Had the same issue. fix is to install Mangohud 24.08 specifically.
flatpak install mangohud # now choose the 24.08 version from the list, for me it was the top option
Thanks, glad to hear I'm not imagining or have misconfigured something. I think I'll stick with a downgraded Bottles version for now, it's not like 51.14 and 51.15 changed a lot for my use case, and it's only really Fallout New Vegas that needs MangoHud's frame limiter feature.
Had the same issue. fix is to install Mangohud 24.08 specifically.
flatpak install mangohud # now choose the 24.08 version from the list, for me it was the top option
Thanks, glad to hear I'm not imagining or have misconfigured something. I think I'll stick with a downgraded Bottles version for now, it's not like 51.14 and 51.15 changed a lot for my use case, and it's only really Fallout New Vegas that needs MangoHud's frame limiter feature.
Just found out the version dependencies also span to gamescope and vkBasalt (and vkBasalt does not have a 24.08 version available in flathub). So downgrading Bottles is the only option if you depend on vkBasalt. NOTE: you can actually view dependencies when hovering your mouse over the greyed out switch option in a Bottles bottle.
We have updated the Runtime to a new version, so, due to the way Flatpak works, you need to install all those components with the same version pointed by SjoerdV.
For those not being updated yet, you need to downgrade or wait for the respective developers to upgrade their projects on Flathub. Sadly there is nothing we can do here.
That's good to know, thanks @mirkobrombin - I also figured out that there doesn't seem to be any conflicts having both v23.08 and v24.08 of org.freedesktop.Platform.VulkanLayer.MangoHud
installed.
Describe the bug
After updating from 51.13 to 51.14, MangoHud no longer works ingame for me. It used to work, and it still works for other flatpak games (like prism launcher -> minecraft).
To Reproduce
Make sure
org.freedesktop.Platform.VulkanLayer.MangoHud
is installed in flatpak, then make sureMANGOHUD=1
environment variable is set in flatseal for Bottles or all applications as in my case. Less important step is setting up so that Mangohud.conf is visible for flatpaks by exposingxdf-config/MangoHud:ro
under filesystem/other files.Now run Bottles and try running anything 3D like a game where MangoHud would normally initialize. In my case both Civilization 4 and Fallout New Vegas fail, no mangohud running.
Package
Flatpak from Flathub
Distribution
MX Linux 23.4 (Debian Bookworm-based)
Debugging Information
Troubleshooting Logs
Additional context
I'm reporting the bug here instead at flightlessmango/MangoHud because MangoHud still works in Flatpak as it used to, but stopped working for just Bottles, and it broke from the recent upgrade to 51.14, and I'm not sure what changed, because flatseal still says the same environments are set and same files exposed.
It certainly would be nice if someone else can verify this or if I've made a mistake somehow.