You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest 2.15.2 update the following filesystem permission was added to the Flatpak ~/.config/MangoHud:ro which should pick up the user's local MangoHud config file, however when running games with MangoHud enabled in Heroic it appears to not read it and use the default settings as if the config file was not present.
The fix/workaround is to instead add the filesystem permission xdg-config/MangoHud:ro, which does make it possible for MangoHud to use the config file.
I'm not sure why ~/.config fails but xdg-config works since they should both resolve to the same path but using the latter one fixes the problem.
Have Heroic 2.15.2 Flatpak installed with all permissions set to default, have an existing MangoHud config file at ~/.config/MangoHud/MangoHud.conf, making sure it has some something changed to differentiate it from the default settings
Run a game with MangoHud enabled in Heroic, note it will use the default settings
Add xdg-config/MangoHud:ro to the Heroic filesystem permissions (using something like Flatseal)
Re-run the same game, note MangoHud is now able to use the config file
Expected behavior
Flatpak filesystem permissions are configured so the config files can be read.
Screenshots
No response
Heroic Version
Latest Stable (Flatpak)
System Information
ArchLinux
Additional information
No response
The text was updated successfully, but these errors were encountered:
Runtime updated to 24.08. So you need to install MangoHud for 24.08
The one that is runtime/org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/24.08
# flatpak install mangohud
Looking for matches…
Similar refs found for ‘mangohud’ in remote ‘flathub’ (system):
1) runtime/org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/24.08
2) runtime/com.valvesoftware.Steam.Utility.MangoHud/x86_64/stable
3) runtime/org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/21.08
4) runtime/org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/22.08
5) runtime/org.freedesktop.Platform.VulkanLayer.MangoHud/x86_64/23.08
6) runtime/com.valvesoftware.Steam.VulkanLayer.MangoHud/x86_64/stable
Which do you want to use (0 to abort)? [0-6]: 1
ID Branch Op Remote Download
1. [✓] org.freedesktop.Platform.VulkanLayer.MangoHud 24.08 i flathub 11.6 MB / 11.9 MB
It really needs some simplification. Like automated check and offer to install proper version for MangoHud, Gamescope etc.
Describe the bug
With the latest 2.15.2 update the following filesystem permission was added to the Flatpak
~/.config/MangoHud:ro
which should pick up the user's local MangoHud config file, however when running games with MangoHud enabled in Heroic it appears to not read it and use the default settings as if the config file was not present.The fix/workaround is to instead add the filesystem permission
xdg-config/MangoHud:ro
, which does make it possible for MangoHud to use the config file.I'm not sure why
~/.config
fails butxdg-config
works since they should both resolve to the same path but using the latter one fixes the problem.Add logs
Steps to reproduce
~/.config/MangoHud/MangoHud.conf
, making sure it has some something changed to differentiate it from the default settingsxdg-config/MangoHud:ro
to the Heroic filesystem permissions (using something like Flatseal)Expected behavior
Flatpak filesystem permissions are configured so the config files can be read.
Screenshots
No response
Heroic Version
Latest Stable (Flatpak)
System Information
ArchLinux
Additional information
No response
The text was updated successfully, but these errors were encountered: