flightlessmango
flightlessmango
> hide_engine_names does not override engine_short_names so if the latter appears in config, the former will not take effect. This has been reworked a bit in e96a0bf5afbc8f01b648a739bfd34379979c23cc Might have accidentally...
cpu power requires intervention documented in readme. Do you have the ability to test latest git mangohud to see if gpu power has already been fixed?
Likely causing a stutter when reading some sysfs nodes. We'd want to figure out which one(s) are causing it
try setting `gpu_power=0`
Does gpu_power=0 change anything?
For old AMDGPUs we touch sysfs nodes. Namely `gpu_busy_percent` `mem_info_vram_total` `mem_info_vram_used` and `mem_info_gtt_used`. Try accessing them each with `time cat gpu_busy_percent` etc and post the result here. They are in...
Nice those look fine. We also poke some hwmon nodes. `/sys/class/drm/card1/device/hwmon/*/temp1_input` `/sys/class/drm/card1/device/hwmon/*/temp2_input` `/sys/class/drm/card1/device/hwmon/*/temp3_input` `/sys/class/drm/card1/device/hwmon/*/freq1_input` `/sys/class/drm/card1/device/hwmon/*/in0_input` `/sys/class/drm/card1/device/hwmon/*/freq2_input`
You want vram to be shown in `gpu_stats` instead of `vram`?
`cpu_temp_sensor` option does not exist Can you provide logs with `MANGOHUD_LOG_LEVEL=debug` set?
Yes this is a bug in mangohud, we need to refine the logic of how we pick hwmon sensors