Why would chaining gamemoderun make mangohud work in a game?
Original message was deleted
RI usually have mangohud always on and configured it to not show.
You can create a file in
Then create a MangoHud config file in
With that you don't need to add the command for every game you want to see it
You can create a file in
$HOME/.config/environment.d/99-mangohud.conf with MANGOHUD=1 and reboot.Then create a MangoHud config file in
$HOME/.config/MangoHud/MangoHud.conf and uncomment no_display to make it not show up unless you toggle it in game with Right Shift-F12With that you don't need to add the command for every game you want to see it
RThis is a mangohud config file example:
https://raw.githubusercontent.com/flightlessmango/MangoHud/master/data/MangoHud.conf
https://raw.githubusercontent.com/flightlessmango/MangoHud/master/data/MangoHud.conf
Rprobably not, you would need to see the error that is happening under the hood when steam tries to launch the game
Rbut, you can always try
RAnother way would be running
MANGOHUD=1 %command% in the launch optionsRmaybe it is the mangohud script that is crashing when running under steam
RIt is a basic on/off switch using 1 and 0. Mangohud installs itself as a vulkan layer and tells vulkan to watch that variable, if it is 1 the layer will be activated
Rif you are curious, you can check the mangohud script
cat $(which mangohud)