🧪 v2.2.0-beta.1 — Intel CPU Barchart Test Feedback

[TroyMetrics]

👻 TroyMetrics Beta Builds — Testing Requested (Intel)

This thread is for v2.2.0-beta.1 testing, focused on Intel CPU compatibility for the new Dynamic CPU Barchart system.

✅ What New v2.2 (Beta 1)

• New Dynamic CPU Barchart system
  • Bars now represent MAX(T0, T1) per physical core (best for gaming bottleneck visibility).
  • Uses HWiNFO sensors to ensure correct physical-core ordering.
  • Intel hybrid CPUs should display P-cores first, then E-cores (when HWiNFO exposes P-core / E-core sensors).
• FrameGen auto-detection removed (was inconsistent - did not work in certain games)
  • Replaced with a user toggle so you can force the frametime graph mode per game.

🧠 FrameTime Mode Toggle (new)

• Set FrameTime Mode
  • Set FrameTime Mode = 0 or N/A Game-side (Render) Frametime — Uses RTSS built-in Frametime or <FT> source.
    Best for normal gameplay/benchmarking when Frame Generation is OFF, since it reflects the game’s true render pacing and responds quickly to hitches and spikes.
  • Set FrameTime Mode = 1 Display/output-side Frametime — Uses PresentMon msBetweenDisplayChange.
    Recommended when using Frame Generation, because it tracks the pacing of frames as they reach the display output. This avoids the jagged/“fat” frametime graph behavior that can appear when viewing render-side frametime while FG is active.

This lets users manually switch to display/output metrics when using Frame Generation (or anytime they prefer) to avoid jagged or “fat” frametime graph behavior.

Note: Display/output frametime may appear delayed (Approximately 3 seconds) due to PresentMon behavior.

⚠️ Important

HWiNFO is required for accurate Intel (P/E) core ordering in the new barchart system.
If HWiNFO isn’t running, the overlay can’t reliably map hybrid core groups.

---

🧪 What I need Intel users to verify

I’m mainly trying to confirm that the HWiNFO sensor references + logic are working on Intel systems (i.e., the bars actually show real activity and don’t go blank / N/A). I don’t currently have an Intel system available, so this pre-release is mainly to confirm that the Intel HWiNFO sensors resolve correctly (i.e., the CPU barchart shows real activity and isn’t blank/zero due to missing/incorrect sensor names).

Please check for:

• Missing bars / blank module
• Bars not moving under load
• Incorrect total bar count for your CPU

---

📝 How to post your results (quick template)

Simply just reply to this thread, please include:

• CPU model: (ex: i7-14700K / i9-13900K / i5-13600K)
• HWiNFO running? (Yes/No)
• Screenshot (optional but awesome): you can paste images directly into Discussions
• Anything weird you noticed: (missing bars, flicker, N/A, etc.)

Thanks for helping test this 👻🔥

[VimesUK]

Firstly, even with shared memory access within HWiNFO64 enabled, the conditions for the memory speed and average CPU load do not work, the conditions have to be removed.

see 2.13 with all working and the conditions for the 3 variables noted removed.

Then on to the 2.20 beta 1....

again without the conditions removed for the three variables they will not display.

I run an Intel 265K on a Gigabyte Z890 motherboard. Core Count override was set to 20.

[chrisp008007-cell]

Modelo de CPU: Intel Core Ultra 9 275HX
¿ HWiNFO está en ejecución? Sí
Captura de pantalla

Tengo HWiNFO en ejecución con la opción activada de la memoria compartida y aun así el Overlay indica el mensaje de que no está encendido....

Con los Overlays que tienes subidos de noviembre si que lo muestra correctamente.... No entiendo que en esta versión no