flightlessmango

No this is not solved (at least not intentionally), I got confused by the unrelated comments. However it would be useful if you could test with dev branch and see...

I haven't been able to run this game at all yet so it makes things a little harder. Steam log might be useful. What GPU are you using?

So far I don't have a reason to believe there is a mangohud bug here, we're just showing what the kernel driver is telling us. I would need to see...

It comes from the `/sys/class/drm/card0/device/gpu_metrics` binary, specifically `indep_throttle_status` You would need to compare the bits hit with this [Throttle map](https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/amd/pm/swsmu/smu11/navi10_ppt.c#L240)

>throttle_status_flags: PPT0, PPT2, PPT3, SPL, TDC_CVIP Not sure what SPL and TDC_CVIP is, but I think PPT0-3 are power bits. So according to this mangohud should show power throttling (assuming...

both mangohud and the script is reporting the same thing, so I'm gonna assume they are correct. How do you verify that you're not power throttling?

> It also reports power and thermal throttling at all times on my system. Which is not the case, especially the thermal throttling doesn't make sense when my card is...

I don't know of anyway to query obs for recording status, or anything for that matter

I'm seeing the core dump with or without mangohud, however mangohud works just fine in this game on my system. Might be worth testing latest master

Since steam is starting the game it will be unaware of the `mangohud` from the terminal, you would need to add `mangohud %command%` to the launch options