#Mangohud + BAR on Linux
1 messages · Page 1 of 1 (latest)
Set a reminder in 2 days from now (<t:1725253011:f>)
View reminders with the reminders command
Yes but I can't easily look it up right now
The Bar client showed all kinds of of system information 2-3 year's ago... we could even see our's and other Player's OS/CPU/GPU and the usage from our devices. It was so dumb to remove all this nice features... this was 5 steps backwards 🤯 P.S: Im playing BAR on Linux too, for what reason are you want to use Mangohud? Just for the Overlay or FPS Lock?
It was so dumb to remove all this nice features
Privacy concerns from some people.
Yeah, i know... i asked teifon at this time... its still dumb. A simple on/off switch at the BAR Settings would be enough for this, but instead it was disabled with Force OFF for everyone. It was so nice to see this overview without additional Thirdparty program's. Im not even use a smartphone or Windows anymore, but disable this feature in relation's about Privacy was a joke. This feature's never revealed anything that was really private... and our community wasn't asked either, it was removed without feedback (eat or die).
It was removed after a bunch of people spoken about this being a concern
From people who using Win10/Win11 with hardcore invasive telemetry today? 😄
¯_(ツ)_/¯
Stranger from the internet seeing my PC specs: 😡
Microsoft seeing everything I do on my PC: 🥰
Exactly, the good old Double high standards 🤣
fps lock for keeping the system cooler
Someone on the Nobara discord managed to do it with mangohud --dlsym ./bar.appimage, but I couldn't replicate it. Do you happen to be able to get it to show up?
FPS lock is something i want to archive too... but i have no experience around Mangohud... Do you play the appimage version of bar? Because im using Flatpak and i don't think this will work with flatpak this way
I've tried both and couldn't replicate
mangohud --dlsym ./Beyond-All-Reason-1.2988.0.AppImage worked for me on fedora kde
hmmmmmm idk why its not working for me then
just curios, are you on wayland or x11?
oh also, what version of mangohud do you have, and do you mind sharing your config?
Reminder for @neat oriole
this thread
Hmmmmmmm that's my setup too
Ok! I have an update. It turns out that the program AppImageLauncher, which launches my appimages, for whatever reason was blocking the mangohud. Uninstalling AppImageLauncher and running the appimage normally fixed it 🎉
I wonder that you using AppImage at all, the last time i try BAR as AppImage version it has a good amount of Sounds Filtered out. specially the low frequenz stuff no longer shows output. While with the Flatpak where i never had a problem around this sound stuff.
I couldn't tell a difference between flatpak and appimage apart from appimage having actually louder sounds
the appimage+mangohud FPS lock is keeping my PC nice and chilly btw, so it's doing exactly what I was hoping! 🎉
You can hear the broken audio filter, when it comes to Geothermal Sources... in Flatpak the peak sound is only there when you really close with the camera to a geo spott, while in the AppImage version its always present. Flatpak sound are miles better... but if you use a cheap onboard soundcard instead a good dedicated soundcard, you may don't care around soundquality
It's not Appimage vs Flatpak. It's libraries in your base system vs in Flatpak.
Everything bar ships in Appimage and Flatpak is exactly the same
You having some issue with Appimage doesn't mean that it's issue with Appimage and everyone else will have the same issue
It only means that your system libraries are buggy
And the ones in flatpak are not buggy for you
sound OpenAL library used by engine is not statically linked, but it's dynamically linked to what is present in the system.
I reported this problem long time ago, i think it was in this Topic: https://discord.com/channels/549281623154229250/1209551304058470481 but i remember a discussion with damgam and teifon, where i pointed them, again to this filter problem and @west shadow was showing a link with Open AL that there was this bug still not fixed. But i can't find the discussion 😦