Ryzen 5600x can't reach 4600 MHz on all 6 cores at the same time on the stock cooler with the default settings. The max frequency on a single core is pointless for modern games that use more than 4 cores. Msi Afterburner implies that it's reaching 4600 Mhz on all cores. Hwinfo says this is wrong. Like I said I don't understand why unwinder thinks that the average all core frequency is not good.

because its average clocks are black magic.

Mineria:

Average really doesn't tell anything.... think average FPS for a second and tell me how useful it is.

Well, averaging is actually really frequently used for FPS counter, that's what you're seeing in 99.9% of in-game FPS counters and external counters like RTSS, Steam or anything else. All of them are displaying FPS counter calculated by averaging frametimes with sliding window during the last second. Even the metric name (frames per second) hints that there should be some form of frames averaging and it is not an instantaneous inverted value based on a single frame time.

bluedevil:

Msi Afterburner implies that it's reaching 4600 Mhz on all cores.

No need to link your wrong understanding to what MSI AB really implies. It implies that at least one core is reaching such clock, nothing more, nothing else, and it was documented and declared so since day one. If you misunderstood that - it is not my porblem. If you don't see that core clock averaging is not reflecting anything realistic - it is not my problem too. As a rough example, two 1000MHz /100MHz clocked cores giving you average "clock" of 550MHz and 550MHz / 550MHz cores giving you the same average "clock" are by far not equal neither from performance nor from power consumption point of view. Let's stop on that. If you beleive that clock averaging is needed- nothing prevents you from creating your own plugin displaying averaged value for you. I won't be displaying what I see physically wrong. Period. I'd _really_ like to avoid continuing wasting work time on this discussion please.

Unwinder:

Chris created those "incredibly impractical and confusing skins" for you, he is exacrtly the same Guru3D community member as you are. You have all chances to do something useful too, show everyone how to create proper skins yourself and share results of your work with community. But something is telling me that it won't happen.

It's called criticism. Just because something remains optional doesn't mean it deserves a free pass. These newer skins are horrible and unworthy of anyone with an eye for functionality or an engineering background. I hope at least the old skins won't ever be removed! I also hope the download size of AB won't one day reach Nvidia driver size of levels due to thousands of modern skins packaged with it. Peace.

It is not called criticism. People with true engineering background have drastically different understanding of criticims and do not declare that something is "unworthy of anyone" when it doesn't match with their personal preferences.

I never implied you Unwinder should be hold responslible for the link placements, ever! Thank you. It is not the first time that the links are confusing, mixing beta and final, o numbers. At least it works. And regarding skins, just use all what you like. Big corpos are unable to find the "perfect" looks of their software, so enthusiast created content will also be debateble, but always appreciated!

Maulet:

I never implied you Unwinder should be hold responslible for the link placements, ever! Thank you.

Well, you adressed this question personally to me so I replied. Download page contents is beyond of my control.

Unwinder, your MSI Afterburner is head and shoulders above the rest of the field and has been since it’s first release in 2010. Don’t know how you maintain so well with all the nitpicking prima donnas around, my hat goes off to you. Well played, Mate.

Unwinder:

Well, averaging is actually really frequently used for FPS counter, that's what you're seeing in 99.9% of in-game FPS counters and external counters like RTSS, Steam or anything else. All of them are displaying FPS counter calculated by averaging frametimes with sliding window during the last second. Even the metric name (frames per second) hints that there should be some form of frames averaging and it is not an instantaneous inverted value based on a single frame time.

True, I wasn't quite clear in what exactly I meant with average fps. I meant in the lines of average fps as in average over several minutes/hours, like you can see after running some benchmarks or notice in some GPU/Game reviews, which is different from talking about average fps as with an instant fps counter showing stable fps with no or very few of the 1 and 0.1% framedrops.. I think that aligns more to how useful it is seeing an estimate of average frequency over several cores instead of either the highest or all cores.