CPU utilization shader will not fully light up at 99% CPU

[stdedos]

With layer set as:

Then, even 99.98% CPU will not light up F12
CPU% measurement is done using ProcessHacker (https://github.com/processhacker/processhacker/)

I used to have Maximum Value: 100 before I set it to 95 (when this picture was taken)

Expected behavior:

If gradient is done by # of keys, then CPU >$((MaxCPU - MaxCPU/keys))% would light up F12 (i.e. 92.307% in my Max CPU 100% case)
If gradient is done by "actual keyboard distance", then CPU >$((MaxCPU - MaxCPU/dst_unit))% (idk how/if you "somehow" measure that)

Actual behavior:

Only CPU 100% would trigger that (and could be not the case, I tried 99,5% and barely got it).

How often does this problem occur?

This problem occurs... (Fill in here) Constantly

Please describe the steps to reproduce this issue:

The issue can be reproduced by doing following steps:

What is the version of Aurora you are experiencing this issue with?

My version is... 0.6.4b-b604

Does the previous version of Aurora have this issue?

The previous version, (Fill in the version here), did/did not have this issue. Haven't tried / I guess yes

Please include any logs, screenshots, or files that are related to this issue:

[Mikowmer]

Try removing ESC from the affected keys.

EDIT: Or try to set it up like this (i.e. the default):
https://imgur.com/irtEqo2

[Wibble199]

I don't think the problem is with the logic, as it works fine for other variables, so perhaps the program is reading the CPU usage incorrectly for some reason.

Try typing a value directly into the "Current Value" box, such as '100' and validating whether all the keys light up fully and correctly. I would be surprised if this doesn't happen. If it works as expected when testing raw values, the problem will be with reading the CPU usage values for some reason, but we'll try figure it out once you've tried this.

[stdedos]

Try removing ESC from the affected keys.

EDIT: Or try to set it up like this (i.e. the default):
imgur.com/irtEqo2

Doesn't work. CPU @ 99.98% and still F12 is unlit

---

I don't think the problem is with the logic, as it works fine for other variables, so perhaps the program is reading the CPU usage incorrectly for some reason.

My guess would be so. However, it is hard to test it e.g. with RAM utilization (because near-or-100% RAM is probably BSOD).

Try typing a value directly into the "Current Value" box, such as '100' and validating whether all the keys light up fully and correctly. I would be surprised if this doesn't happen. If it works as expected when testing raw values, the problem will be with reading the CPU usage values for some reason, but we'll try figure it out once you've tried this.

I already said on the issue description that I had it

Maximum Value at 100

before I debugged it and "arbitrarily" decided that max 95% is as good as 100%. There is no "automatic" value to set for max percentage (as e.g. there is for maximum RAM).

I can upload the json profile when I've set it on 100% if it's hard to believe that I used to have it as 100 😩

[diogotr7]

This might be caused by either a reading issue, or a bug with the cpu usage smoothing. please try with the new implementation for performance counters in the dev builds.

[stdedos]

and still seeing the issue. It doesn't happen for clear-cut cases (like 99.98%) but it's still annoying.

However, Aurora is an annoyance to use because #1002, #1028 (comment), #1028 (comment), #1897, and

(every single time I open it, and I haven't even touched Overwatch)

and therefore I am not really looking forward in using it at this moment

[diogotr7]

That pop-up can be fixed if you delete the overwatch profile files manually.

I'll give the other issues a look.

[stdedos]

That pop-up can be fixed if you delete the overwatch profile files manually.

Something-something RazerChromaProfile vs WrapperProfile, a lot of things I didn't try to diff, and some RGB differences. If they are useful to you, here they are: overwatch-.zip

I was hoping it would be solvable, as both (?) were Aurora's stuff

I'll give the other issues a look.

Looking forward to it. Let me know if/when you'd like the cores (10 files / 3,78 GB (4.066.579.146 byte)). Maybe you'll be lucky and I'll get a new one 😉