Open LukeXuan opened 3 months ago
LukeXuan
commented
3 months ago Something happened with gamescope --mangoapp that is definitely not correct is that unless I explicitly specify the config path, mangoapp will try to read config from /var/run/1000/.... I'm unsure if that's a flatpak problem or gamescope problem. But at least that's something I can fix easily.
flightlessmango
commented
3 months ago mangoapp will try to read config from /var/run/1000/
This was a gamescope issue and has been addressed there
install steam, gamescope, and mangohud using flatpak
Does flatpak mangohud have mangoapp?
LukeXuan
commented
3 months ago Does flatpak mangohud have mangoapp?
yes,
bash-5.2$ ls -la /usr/lib/extensions/vulkan/MangoHud/bin/
total 5564
drwxr-xr-x. 1 nfsnobody nfsnobody 32 Dec 31 1969 .
drwxr-xr-x. 1 nfsnobody nfsnobody 56 Aug 12 07:48 ..
-rwxr-xr-x. 2 nfsnobody nfsnobody 5693376 Dec 31 1969 mangoapp
-rwxr-xr-x. 2 nfsnobody nfsnobody 1705 Dec 31 1969 mangohudToo often the cause lies somewhere in flatpak and if it does it's not a mangohud issue. Could you verify that this is happening outside of flatpak?
LukeXuan
commented
3 months ago running natively with packages shipped from fedora repository it works, like I previously describe,
I also verified that natively (using dnf install gamescope mangohud) they work, mostly. Well, the gamescope in fedora's repo is too old to have the --mangoapp option, but the old bash -c "mangoapp& vkcube" trick still works.
LukeXuan
commented
3 months ago Is there any information I can gather other than MANGOHUD_LOG_LEVEL=debug? At least one thing I observed is that with flatpak, running mangohud eventually leads to somewhere in the vulkan.cpp, and reports my gpu. running with --mangoapp doesn't print that line.
[2024-08-14 02:21:45.361] [MANGOHUD] [debug] [vulkan.cpp:1859] gpu: AMD Radeon RX 7800 XT (RADV NAVI32)Why are you setting ENABLE_GAMESCOPE_WSI=0 ?
LukeXuan
commented
3 months ago It's related to this issue for flatpak's gamescope: https://github.com/flathub/org.freedesktop.Platform.VulkanLayer.gamescope/issues/199
flightlessmango
commented
3 months ago That usually happens when you use mangohud with gamescope, the two layers do not work well together. Make sure you don't have mangohud layer automatically applied and use the gamescope layer
LukeXuan
commented
3 months ago If you are talking about the CreateSwapchain error, no it's independent: running gamescope without mangohud installed still triggers the errors.
leonardohn
commented
4 days ago I'm facing the exactly same issue in NixOS, which also wraps Steam into a namespace. MangoHud works as expected using MANGOHUD=1, but gamescope --mangoapp has no effect, even though it seems to initialize by looking at the logs.
Do not report issue for old MangoHud versions
Describe the bug While
mangohud %command%work without problem,gamescope --mangoapp %command%doesn't display the HUD. I can see in the log thatmangoappis launched though.List relevant hardware/software information
To Reproduce Steps to reproduce the behavior:
mangohud %command%, and observe the hud showing up,gamescope --mangoapp %command%, and it doesn'tExpected behavior mangohud showing up with gamescope
Additional context Here is the log for
mangoapp(the one that's not working), the actually launch options areENABLE_GAMESCOPE_WSI=0 MANGOHUD_CONFIGFILE=/home/luke/config/MangoHud/MangoHud.conf MANGOHUD_LOG_LEVEL=debug PROTON_LOG=on gamescope --mangoapp %command%:and here is the log of
mangohudfor comparison (MANGOHUD_LOG_LEVEL=debug MANGOHUD=1 %command%):I also verified that natively (using
dnf install gamescope mangohud) they work, mostly. Well, thegamescopein fedora's repo is too old to have the--mangoappoption, but the oldbash -c "mangoapp& vkcube"trick still works.