You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The text value of the GPU VRAM consumption is stuck at 0. 5GB.
The visual representation (ring graph or bar graph) is correct -- the percentage usage matches the value from HWiNFO.
But the text value is always showing 0.5 GB, independently of the actual usage.
Expected behavior
Text value of VRAM shows the correct amount.
Screenshots
Notice how the text is showing 0.5 GB even though the ring graph is correctly showing ~50% usage (which should be ~ 2 GB)
The ring graph correctly updates in real time and matches the value shown by HWiNFO.
But the text value is always stuck at 0.5 GB regardless.
Also not sure if it's related, but even though I'm selecting the GPU Memory sensor, when I click on the drop down again it shows the checkmark in the wrong sensor.
This checkmark bug doesn't happen in the other sensors, only in this one -- so maybe it's related.
Desktop (please complete the following information):
OS: Windows 11 24H2
Version 1.1.0
The text was updated successfully, but these errors were encountered:
Describe the bug
The text value of the GPU VRAM consumption is stuck at 0. 5GB.
The visual representation (ring graph or bar graph) is correct -- the percentage usage matches the value from HWiNFO.
But the text value is always showing 0.5 GB, independently of the actual usage.
Expected behavior
Text value of VRAM shows the correct amount.
Screenshots
Notice how the text is showing 0.5 GB even though the ring graph is correctly showing ~50% usage (which should be ~ 2 GB)
The ring graph correctly updates in real time and matches the value shown by HWiNFO.
But the text value is always stuck at 0.5 GB regardless.
Also not sure if it's related, but even though I'm selecting the GPU Memory sensor, when I click on the drop down again it shows the checkmark in the wrong sensor.
This checkmark bug doesn't happen in the other sensors, only in this one -- so maybe it's related.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: