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
Currently, the sensors are sorted by Id, in most cases, that works fine.
However, in my particular case (Probably true for other AMD users on Win11)
On my particular system the desired sensor (and with the lowest index at the end) is /gpu-amd/0/load/2
That however raises an issue, if there is a sensor with an Id ending in 10 or higher, as those will be sorted in before the desired sensor with a lower ending number.
(See sensor log snippet below)
Reproduction steps
Probably not too easy to reproduce.
I run a AMD 7900XTX on Win11
Aurora Version:
v185, but according to the sources the issue must still be present in master
Expected Behaviour
GPU-Load selects the D3D Load Sensor
Actual Behaviour
Selects "D3D Timer 0"
More Detailed description
Currently, the sensors are sorted by Id, in most cases, that works fine.
However, in my particular case (Probably true for other AMD users on Win11)
On my particular system the desired sensor (and with the lowest index at the end) is
/gpu-amd/0/load/2
That however raises an issue, if there is a sensor with an Id ending in 10 or higher, as those will be sorted in before the desired sensor with a lower ending number.
(See sensor log snippet below)
Reproduction steps
Probably not too easy to reproduce.
I run a AMD 7900XTX on Win11
Aurora Version:
v185, but according to the sources the issue must still be present in master
Sensor Log Snippet
Expand
Additional Notes:
I tried to update the sorting myself and open up a PR, but cannot get the build to work ¯_(ツ)_/¯
Any help would also be appreciated.
Assumed fix (patch file)
The text was updated successfully, but these errors were encountered: