Continuing to be the go-to for people needing a good HUD while gaming, MangoHud has a new release up. Giving you the ability to get a real-time readout on GPU/CPU use, FPS, frame timings, RAM/VRAM use, what graphics API is used and even a little benchmarking.
Not seen it? It looks something like this:
With the latest release out now, here's some highlights:
- Fixed a memory leak in Source Engine 1 games (CSGO, TF2 etc)
- You can use mangohud --dlsym as an alternative to MANGOHUD_DLSYM=1
- MangoHud now comes with a man page man mangohud
- Added support for KDE neon in build script
- output_file is now replaced by output_folder, the files are automatically named after the programs executable
- By pressing Shift_L+F3 you will automatically upload the latest log file to Flightlessmango.com and open up said benchmark. To upload all logs for this session, the default keybind is Control_L=F3. Both of these require that you set the permit_upload param to 1 and output_folder
- Added supported for more glyph ranges
Some of the configuration parameters you can set have been added to as well, like being able to show the Wine/Proton version used if you're playing games through either compatibility layer. Full releases notes can be seen here. You can also use GOverlay if you need a simple UI to configure it.
Here's a fresh video of MangoHud in action showing the logging capabilities:
Direct Link
Game featured - Ziggurat. If you love repeatable first-person shooters, Ziggurat is a huge amount of fun to blast through. Buy Ziggurat from: Humble Store, GOG and Steam.
Grab MangoHud from their GitHub.
Quoteshow the Wine/Proton version used if you're playing games through either compatibility layerBeen waiting for this one!
Quoting: dpanterQuoteshow the Wine/Proton version used if you're playing games through either compatibility layerBeen waiting for this one!
Examples:
Last edited by mrdeathjr on 17 August 2020 at 6:25 pm UTC
Quoting: UsualAny way to show only the RAM the game is using instead of overall?mangohud and system monitor show different ram usage. if this would be correct you could remember the ram usage before you start the game and do the math
Quoting: scaineI wonder if this will ever get deb/ppa support. I'm just not a fan of "locally" (i.e. non-managed) installed software. Such a cool project too.
maybe you should switch to manjaro. mangohud and a lot of other software is in AUR
https://wiki.manjaro.org/index.php/Arch_User_Repository
Last edited by mylka on 18 August 2020 at 1:05 am UTC
Quoting: dpanterQuoting: scaineI wonder if this will ever get deb/ppa support.WIP, track the request here
Sounds like a hell of a journey! Although a lot of it about the licensing for Debian. Interesting that they're making Oibaf the dependency model for their deb/ppa work. I wonder if it's compatible with Kisak, or I have to switch PPAs when they have a build out?!
Thanks for the link regardless.
Quoting: dpanterQuoteshow the Wine/Proton version used if you're playing games through either compatibility layerBeen waiting for this one!
My pleasure!
Quoting: scaineI wonder if this will ever get deb/ppa support. I'm just not a fan of "locally" (i.e. non-managed) installed software. Such a cool project too.My dirty hack for deb package:
In source dir (from git or tarball) after installing all required dependencies (UPDATED):
meson build/meson64 --libdir lib/mangohud/lib --prefix /usr -Dappend_libdir_mangohud=false -Dld_libdir_prefix=true
CC="gcc -m32" CXX="g++ -m32" PKG_CONFIG_PATH="/usr/lib32/pkgconfig:/usr/lib/i386-linux-gnu/pkgconfig:/usr/lib/pkgconfig:" LLVM_CONFIG="/usr/bin/llvm-config32" meson build/meson32 --libdir lib/mangohud/lib32 --prefix /usr -Dappend_libdir_mangohud=false -Dld_libdir_prefix=true
DESTDIR="$PWD/build/release" ninja -C build/meson32 install
DESTDIR="$PWD/build/release" ninja -C build/meson64 install
cd build/release
ln -sv lib usr/lib/mangohud/lib64
ln -sv lib usr/lib/mangohud/x86_64
ln -sv lib usr/lib/mangohud/x86_64-linux-gnu
ln -sv . usr/lib/mangohud/lib/x86_64
ln -sv . usr/lib/mangohud/lib/x86_64-linux-gnu
ln -sv lib32 usr/lib/mangohud/i686
ln -sv lib32 usr/lib/mangohud/i386-linux-gnu
ln -sv ../lib32 usr/lib/mangohud/lib/i386-linux-gnu
ln -sv lib32 usr/lib/mangohud/i686-linux-gnu
ln -sv ../lib32 usr/lib/mangohud/lib/i686-linux-gnu
tar cvzf ../../../MangoHud-0.5.1-bin.tar.gz . --owner=0 --group=0
cd ../../..
./tar2deb.sh MangoHud-0.5.1-bin.tar.gz mangohud 0.5.1-1
Last step execute shell script tar2deb.sh with such content:
#!/bin/bash
set -x
# $1 - tar.gz file
# $2 - package name
# $3 - version
# $4 - section
# $5 - architecture
control=$(mktemp -dt)
data=$(mktemp -dt)
tarfile="$1"
pkgname=$2
pkgver=$3
section=${4:-misc}
arch=${5:-amd64}
cat "$tarfile" | (cd $data; tar xvzf -)
size=$(du -s $data | cut -f1)
cat > $control/control <<EOF
Package: $pkgname
Section: $section
Priority: optional
Architecture: $arch
Version: $pkgver
Installed-Size: $size
Maintainer: $USER
Description: Deb-package made from $tarfile
This package is made by tar2deb by $USER at
$(date) from $tarfile
EOF
(cd $data; find -type f | xargs md5sum ) > $control/md5sums
(cd $control; tar cvzf control.tar.gz * --owner=0 --group=0)
cp $tarfile $control/data.tar.gz
echo 2.0 > $control/debian-binary
ar -cr ${pkgname}_${pkgver}_${arch}.deb $control/{debian-binary,control.tar.gz,data.tar.gz}
rm -rf $control
rm -rf $data
Last edited by pmadzik on 21 August 2020 at 3:37 pm UTC
See more from me