GPU Monitor over 100% #17

Closed
opened 2024-02-10 10:19:18 -05:00 by WilloIzCitron · 3 comments
WilloIzCitron commented 2024-02-10 10:19:18 -05:00 (Migrated from github.com)

i think the gpu usage was over 100% looks unnatural

Reproduce:

  • must have 2 gpus (igpu and egpu)
  • right click on schale folder
  • suffer

Picture:
image

i think the gpu usage was over 100% looks unnatural Reproduce: - ~~must have 2 gpus (igpu and egpu)~~ - right click on schale folder - suffer Picture: ![image](https://github.com/Xenon257R/blue-archive-rainmeter/assets/49786146/3ca3727c-7e2d-4d0b-a817-9d8104e23ecb)
WilloIzCitron commented 2024-02-10 10:36:40 -05:00 (Migrated from github.com)

update:
i think it was a script error

image

update: i think it was a script error ![image](https://github.com/Xenon257R/blue-archive-rainmeter/assets/49786146/58936292-b431-4d2f-b3e7-30fd6d0a2ca8)
Xenon257R commented 2024-02-10 21:04:37 -05:00 (Migrated from github.com)

It definitely looks like an incorrect implementation of the UsageMonitor plugin by me. I do not own a device with multiple GPUs, so this issue went unnoticed. The official UsageMonitor documentation implies a problem with summation vs. average of the resource values, but I will have to rely on you to confirm the below solution works as intended.

Try changing the following value in BlueArchive\template\resources.inc in Line 62 (under a section titled [GPUUsage]):

Index=0 to Index=-1

The new -1 value should fix the overflowing display value by taking the average of all detected GPUs' usage percentage instead of their sum. However, keep in mind that the value might still be different from Task Manager's value according to this thread on the Rainmeter Forums; the difference unfortunately cannot be resolved, but should be small enough to be negligible.

You may want to change the value of Index of the CPU measurement in the same manner as well, located on Line 48 in section [CPUUsage].

Let me know if it works so I know to apply this change in a clean-up patch for the suite.

It definitely looks like an incorrect implementation of the `UsageMonitor` plugin by me. I do not own a device with multiple GPUs, so this issue went unnoticed. The official [UsageMonitor documentation](https://docs.rainmeter.net/manual/plugins/usagemonitor/) implies a problem with summation vs. average of the resource values, but I will have to rely on you to confirm the below solution works as intended. Try changing the following value in `BlueArchive\template\resources.inc` in Line 62 (under a section titled `[GPUUsage]`): `Index=0` to `Index=-1` The new `-1` value should fix the overflowing display value by taking the average of all detected GPUs' usage percentage instead of their sum. However, keep in mind that the value might still be different from Task Manager's value according to [this thread](https://forum.rainmeter.net/viewtopic.php?t=38126) on the *Rainmeter* Forums; the difference unfortunately cannot be resolved, but should be small enough to be negligible. You may want to change the value of `Index` of the CPU measurement in the same manner as well, located on Line 48 in section `[CPUUsage]`. Let me know if it works so I know to apply this change in a clean-up patch for the suite.
WilloIzCitron commented 2024-02-10 22:19:53 -05:00 (Migrated from github.com)

neat! i fixed the bug!
image

neat! i fixed the bug! ![image](https://github.com/Xenon257R/blue-archive-rainmeter/assets/49786146/46de0551-7176-4b17-bfa3-a61abb80f31b)
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Xenon257R/blue-archive-rainmeter#17
No description provided.