search

flightlessmango / MangoHud

A Vulkan and OpenGL overlay for monitoring FPS, temperatures, CPU/GPU load and more. Discord: https://discordapp.com/invite/Gj5YmBb
MIT License
6.28k stars 272 forks source link

Thinks that I'm constantly thermal throttling / power limited #1243

Open LivacoNew opened 6 months ago

LivacoNew commented 6 months ago

Describe the bug Recently MangoHUD has been incorrectly displaying that I'm constantly thermal throttling. On top of this, it at times displays that I'm power limited even though from what I can tell my CPU/GPU are completely fine.

List relevant hardware/software information

To Reproduce Steps to reproduce the behavior:

  1. Play anything with MangoHUD enabled.

Expected behavior MangoHUD displays if I'm throttled or power limited correctly.

Screenshots VKCube is not enough to throttle this system in the slightest. Btop on the bottom left confirms my CPU is at a perfectly fine temp. image

Additional context N/A

flightlessmango commented 6 months ago

Unrelated to this issue, it looks like you have two instances of mangohud installed. It appears to be rendering twice

LivacoNew commented 6 months ago

I think I just took the screenshot right as it was updating - I only have the one from the official arch repo and that's it

flightlessmango commented 6 months ago

We are correctly interpreting the information the driver gives us. This had to be corrected before upstream https://github.com/flightlessmango/MangoHud/issues/748#issuecomment-1653315797 Since this GPU is not in NAVI22/23/24 batch, it's likely it needs to be fixed upstream as well

GStar718 commented 5 months ago

does this still work?

flightlessmango commented 5 months ago

does this still work?

I don't know what you mean exactly

LivacoNew commented 5 months ago

does this still work?

I'm still getting this issue if that's what you meant.

LivacoNew commented 5 months ago

^ Seems the guy who reported the issue mentioned above has reported this to their Gitlab with other people also having the issue confirming it's a amdgpu's problem.