01What Interactive Hud is
A hardware monitor that doesn't stop at the present moment: it sees, records, remembers and watches.
Interactive Hud shows the state of your computer on top of your game — temperatures, clocks, power, FPS — and, at the same time, keeps the machine's history: every game session, every hour of the day, every driver that changed, every time a fan stopped.
There are four layers, and it helps to see the difference right away:
| Layer | What it is | Where it lives |
|---|---|---|
| See | The gauges floating over your game | The HUD |
| Record | Every game session, on its own, with a grade at the end | Sessions and the report |
| Remember | 7 days, 90 days, months, the whole build | Timeline · Logbook · Memory · Health |
| Watch | Cooling and temperatures, without being asked | The Sentinel |
A normal monitor answers “what is it right now?”. This one also answers “when did this get hot?”, “how much did last night cost me in electricity?” and “what changed in the machine since it got slower?”.
What you need
| Requirement | Detail |
|---|---|
| System | Windows 10 or 11, 64-bit |
| .NET | Nothing to install — it ships inside the package |
| Administrator | Yes, and the app asks for it by itself. Without it there are no temperatures, clocks or FPS |
| Sensor driver | Included; the app installs it by itself if it's missing |
| Internet connection | To install (the installer fetches the app), to activate the license and to check for updates. Once activated it works 90 days offline; after that, if the app starts with a connection it renews the license by itself, without asking for your key — offline, the activation window opens with your key already filled in |
02Installing and first launch
One installer, one permission prompt, one key. After that the app works on its own.
- Run the installer
InteractiveHud-Setup.exe— the small file you download at https://interactivehud.com/download. It fetches the app, confirms the file comes from ValenorEye and only then installs it. It installs into your user profile and does not ask for administrator at this stage. The first time, Windows may show “Windows protected your PC”: click More info, check that the Publisher field shows VALENOREYE, LDA, and click Run anyway. - Open Interactive Hud — it opens by itself at the end of the installation. Windows asks for administrator permission (the blue UAC box). Accept — that's what unlocks temperatures, clocks and FPS. The publisher shows as VALENOREYE, LDA, because the app is signed. What asks for this permission is the Interactive Hud launcher (
InteractiveHud-Lancador.exe): the first time, it puts a copy of the app in %ProgramFiles%\ValenorEye\Interactive Hud\, where only an administrator can write, checks each of its roughly 280 files against the catalog signed by ValenorEye, and that copy is the one that runs — so the first launch may take a little longer. (Since version 1.1.41.) - Paste your key into the «LICENSE ACTIVATION» window. It looks like
ITHUD-XXXXX-XXXXX-XXXXX-XXXXX. The window also shows This PC's ID and the Motherboard ID — that's what ties the key to this machine. If you replace the motherboard, the license moves to the new one by itself if it had been on the old one for at least 90 days; it never moves back by itself to a board it has left. If you replace the board before those 90 days, reinstall Windows or change PCs, write to us at info@interactivehud.com and we'll free your license. (The motherboard, since version 1.1.38.) - Follow the guide — 12 short steps (8 about the Panel, 4 about the HUD) that open by themselves whatever they're explaining. You can say «Not now».
The app does not close. It keeps showing processor usage, memory, network and ping — but temperatures, clocks, power and FPS stay at “N/A”, and a permanent yellow notice at the top of the menu says what was lost. To get them back: close and reopen the app, accepting the prompt.
The app has no trial and no free mode. Without an activated key, closing the activation window quits the app. Whoever has the app bought it.
Updates
The app checks for a new version at startup, 30 minutes later and then every 6 hours — at most one successful check per day. When there's a new version, «⬇ Install update» appears with the version number — in the menu of the tray icon next to the clock, in the gauge menu and, since version 1.1.47, at the top of the Panel. It never installs itself: it tells you, and waits for you.
When you install, a small window shows the step it's on — checking, downloading (with the percentage), preparing, installing — and at the end the app restarts by itself. While it's checking or downloading, closing the window cancels, and you stay on the version you had; after that the window won't close, because interrupting the installation halfway would break it. When your computer already has the previous version stored, it downloads only what changed — usually under 1 MB, instead of the ~85 MB of the full package. (Since version 1.1.43.)
The update catalog is signed with our key, and the signature is verified on your computer before anything is downloaded. If verification fails, the update is refused — there's no “continue anyway”. When only what changed is downloaded, the package assembled on your computer is checked against that same signed catalog before it's installed; if it doesn't match, the full package is downloaded.
03The Panel — the front door
It's what opens when you start. It greets you, sums up the state of the machine and takes you everywhere else.
How to open it
Left-click the icon next to the clock. (Or right-click the icon → «Panel».) By default it opens by itself with Windows.
The Panel opens compact: just the face. Hover over it and the buttons and footer appear. You drag it by the design itself, and the bottom-right corner changes the scale — it grows as far as the screen allows (at most 4×) and shrinks until the Panel is about 420 px wide — handy on a small secondary screen. Double-clicking that corner restores the natural scale.
What it shows
- Status chip — «All good», «Attention» or «Critical».
- Four quick gauges — processor, graphics, memory, and how long the PC has gone without a restart. The count keeps running through sleep and, with Fast Startup on, a «Shut down» doesn't reset it — a «Restart» does.
- Your day — hours watched today, energy measured and the graphics peak.
- What changed since your last session — what changed in the machine (programs, drivers, Windows updates). Clicking opens the Logbook.
- Recent log — the latest events.
- Command hub — six buttons: the Timeline, Memory, Health, the Monthly recap, «Compare sessions (A/B)…» and «Record session (manual)», which turns into «Stop & save session» while recording. Settings aren't here: they're in the footer, next to «Sensors».
The warning bands at the top
When there's something to sort out, a band appears at the top of the Panel. The four that exist:
| Band | What it means |
|---|---|
| Windows Fast Startup (Power Options) | It's on: «Shut down» saves the Windows kernel to disk instead of closing it, and the PC can go weeks without a clean boot — what always does the full cycle is «Restart» (and that's what brings back the graphics power reading when it's missing). The app opens the right Windows page — it doesn't change anything by itself |
| I don't start with Windows | The app isn't starting with the system, so it loses hours of history |
| Is a pump connected here? | The Sentinel saw a suspicious fan header and asks you, to know whether it should watch it |
| Is a pump still connected here? — or, if it's a processor fan, Is a fan still connected here? | A CPU fan or a pump that spun in a previous session has been at 0 RPM since the app started. Either it stopped, or nothing is connected there anymore — the app can't tell which, so it asks you. «No, I don't» silences it until it spins again |
Classic · Sentinel · Command Cockpit · Living Headline · Command Center · Aura. They aren't different colors — it's the same information laid out six ways. You switch in Settings → Appearance → Panel theme. See section 5.
04The HUD — the gauges
Each number is its own little window that you drag wherever you like, on any monitor.
Out of the box, the HUD starts hidden. On a fresh install you only see the Panel. If you thought the overlay doesn't work, this is why. To show it: the «Show HUD» button in the Panel footer, or Ctrl+Alt+Z, or the icon next to the clock → Shortcuts.
The first time, eight cards appear in the «Holograma» style, in a 4×2 grid centered on the screen: processor, graphics, memory and fans on top; disks, FPS, network and power below.
Everything is done with right-click
There's no mandatory settings window. Right-click any gauge to open the menu with everything: style, transparency, merging, profiles, shortcuts, sessions, the Timeline, Memory, alerts, diagnostics and settings. The rest depends on the gauge: «Shape» and «Metric» only appear on single-metric gauges (Bar, Arc, Ring…; Chip Pro has the metric but not the shape). Cards have neither — a component card has «Card style» and, on some, «Card metrics», with ready-made sets — so you won't find them on the eight default cards. And five card styles have no «Theme / Color» (see section 5).
Gestures
| To | Do |
|---|---|
| Move one | Drag with the left button from any point |
| Move all | Ctrl+Alt + drag one of them — they all go, keeping their relative positions |
| Resize | Grab the bottom-right corner. It keeps the proportions (a circle stays a circle) |
| Snap | Drop it near another one: it jumps into place, aligned, touching, and takes the neighbor's size |
| Delete | Hover over it and click the ✕ in the top-right corner |
| Add | Right-click → «Add gauge» → pick the group and the metric |
1. The ✕ only works while it's visible (mouse over it). Clicking there without hover drags the window instead of deleting — on purpose, so you don't delete by accident.
2. The bottom-right corner always resizes, even when the arrow isn't visible. If you grab the gauge by that corner, it stretches.
3. The ✕ on the last gauge closes the app, without asking. You can't be left with zero gauges.
Merging gauges
Put two or more cards of the same style and similar size side by side and the «Merge gauges» item turns gold in the menu. When you merge, they disappear and one large panel is born with the information of all of them — in a row, in a column or in a grid.
- The merged panel has its own menu (right-click it): Style (19 looks, switched live), Split gauges, Full screen, transparency and animation pace.
- The tolerance is generous: up to 12 px difference in size, 28 px misalignment and 48 px of space between them.
Only component cards merge. A gauge in Bar, Arc, Ring, Dial, Chip Pro, Ticker or Monitor never lights up «Merge gauges», even with two identical ones side by side. And a gauge inside a merge stays hidden: to reach it, split the merge first — a merge isn't deleted with a ✕, it's undone with «Split gauges».
Two special gauges
Monitor
A table inside the HUD with the columns Now · Min · Avg · Max, grouped by hardware, with up to 22 rows of your choice. Right-click → «Monitor rows» to choose what goes in; «Reset statistics» starts the count over.
The statistics live only in memory: closing the app loses them. And «Reset statistics» wipes hours of maximums without confirming.
Ticker
A thin strip with up to 11 sensors scrolling past (or standing still). Right-click → «Sensors» picks which ones; «Static (don't scroll)» stops the scrolling. A sensor with no reading drops out of the strip instead of showing “N/A”.
Profiles
Layout profiles save the whole arrangement — positions, styles, theme and merges. There's always a factory DEFAULT profile to go back to the start. And game profiles switch the layout by themselves when that game opens: turn them on with the «Profiles» button in the Panel footer, or under «Game profiles» — in the menu of the icon next to the clock, or in right-click → Application.
OLED protection
For OLED screens, three defenses against burn-in: the gauges shift ±2 px every 90 seconds; after 5 minutes with no keyboard, mouse or controller input, opacity drops to 70% of what it was (and the Panel dims with them); at 15 minutes it drops to 12%. When you touch the mouse, the keyboard or the controller again, everything goes back to normal within 30 seconds. Playing with a controller (Xbox or compatible) counts as activity: the gauges no longer dim in the middle of a game. (Since version 1.1.47.) It's off by default — turn it on with the «OLED» button in the Panel footer, from the menu of the icon next to the clock, or in right-click → Application → «OLED protection (anti burn-in)».
05The look: themes, styles and shapes
There are three different catalogs, and they're easy to confuse. This section separates them.
| What changes | How many | Where |
|---|---|---|
| Face of the Panel | 6 themes | Settings → Appearance → Panel theme |
| Design of a gauge | 26 entries | Right-click → «Gauge» |
| Art of a card | 15 styles | Right-click → «Card style» |
| Art of a merge | 19 looks | Right-click the merge → «Style» |
| Color of a gauge | 20 palettes | Right-click → «Theme / Color» |
| Shape of the box | 4 | Right-click → «Shape» (not on cards, Chip Pro, Ticker or Monitor) |
| Light / dark for the app | 3 options | Settings → Appearance → Menu theme |
The 8 components (GPU, CPU, RAM, FPS, network, disks, fans, power) combine freely with the 15 card styles: 120 combinations.
The Panel's six faces
| Theme | What it is |
|---|---|
| Classic | The original, understated. It's the default and the only one that shows the «Previous session» line |
| Sentinel | An eye in the center that speaks in the first person (“I am watching”), with a rotating iris |
| Command Cockpit | A car dashboard, with warning lamps and an odometer of time without a restart |
| Living Headline | A magazine cover about your PC — every day the story is different |
| Command Center | Dense, for people who want numbers: four instruments with real history |
| Aura | Luxury through empty space; the window's color breathes with the state |
Switching theme closes and reopens the window — you'll see a flicker. That's normal.
Light and dark
The option is called «Menu theme» but it drives the whole app: Panel, Health, Memory, Timeline, reports, menus. It has three values — Follow Windows (the default), Light and Dark.
Setting the app to «Light» doesn't lighten the gauges or the merges: that's art drawn for a dark background, with its own color system. To lighten the gauges, go to each one → «Theme / Color» → the «Light» group (Pérola or Nuvem). They're two independent systems, on purpose.
Matrix (green), Synthwave (pink), Vintage VU (wood), Holograma (cyan) and Minimal Swiss (neutral) have their own identity color. On those, the «Theme / Color» submenu doesn't appear — so it doesn't promise a color that won't change. Since the default style of the 8 cards is Holograma, on a fresh install the 20 palettes are invisible until you change a card's style.
Transparency
Ten levels, from 0% (solid) to 90% (nearly invisible). On a gauge, up to 50% only the plate fades and the numbers stay sharp; on a merge everything fades evenly from the first level, numbers included.
Even though it sits in the menu of one gauge, transparency applies to all gauges and all merges. There's no per-gauge transparency.
06What the app measures
Twenty-two metrics, six reading sources, and one rule worth knowing.
A zero means “I measured and got zero”. “N/A” means “I couldn't measure”. The app never swaps the two: it prefers an honest gap to an invented number. That's why you see “N/A” instead of “0 °C” when a sensor doesn't answer.
| Group | Metrics |
|---|---|
| Processor | Usage · Temperature · Clock · Power — and one gauge per thread |
| Graphics | Usage · Temperature · Hot Spot · Memory temperature · VRAM · Clock · Power |
| Integrated graphics | Usage · Temperature · Clock · Power (only appears if there's a second graphics adapter) |
| Memory | Usage |
| Network | Ping · Download · Upload |
| Performance | FPS · 1% Low · Frametime |
| Devices | Disks (temperature, space, activity) · Fans (RPM, load) |
Colors
Each number is colored by its state. The factory values:
| Metric | Yellow | Red |
|---|---|---|
| Usage | 85 % | 97 % |
| Processor | 85 °C | 95 °C |
| Graphics | 83 °C | 90 °C |
| Graphics Hot Spot | 88 °C | 95 °C |
| Graphics memory | 95 °C | 104 °C |
| Disk | 60 °C | 70 °C |
| Ping | 60 ms | 120 ms |
| FPS and 1% Low | ≤ 60 | ≤ 30 |
| Frametime | 16.7 ms | 33.3 ms |
On the processor and the graphics, red is the limit you choose in right-click → Application → «Alerts», and yellow follows it (10 °C below on the processor, 7 °C below on the graphics). On the Hot Spot, both are fixed. When the metric turns critical, the gauge gets a pulsing red frame.
Note: the Power and Fans cards never flash, on purpose — high power draw isn't danger.
The temperature alert
It watches three parts, each against its own limit: the processor and the graphics, against the «Alerts» limits (by default 95 °C and 90 °C), and the graphics Hot Spot, against a fixed 95 °C. When a part reaches its limit and doesn't drop below it for 4 seconds in a row, the app plays the Windows warning sound — just the sound, no balloon. If you've muted it in Windows, you hear nothing. Until that part drops more than 2 °C below the limit, the sound repeats once a minute. With two or three hot parts, each gives its first sound when it completes its 4 seconds, and from then on it's one sound per minute for all of them.
If the part drops more than 2 °C below the limit, it stops counting, and staying near the limit doesn't bring it back: it only comes back if it reaches the limit again and stays there 4 seconds in a row — and, even then, the sound waits until a minute has passed since the last one. After 20 seconds in a row down there, that part's warning ends, and the next heat starts fresh: it sounds as soon as it completes the 4 seconds.
Usage doesn't trigger the alert, however high: a graphics card at 99% in a game is working, not in danger, and it only turns red on the gauge. The sound is turned on and off in «Sound alert», in the same menu (in Settings it's called «Sound alerts (temperature)»). It's on in a fresh install; if you update, you keep what you had. When it's off, heat only shows in what you see: the color of the gauges and the Panel's state. If you had the processor at 90 °C or the graphics at 87 °C (the factory limits up to version 1.1.44), the update moves them once to 95 °C and 90 °C; any other value stays as it was. The alarm for a stopped fan or pump is the exception: it always shows a balloon and always sounds, even with sound alerts off (see section 10). (Since version 1.1.45.)
Reading rate
By default the sensors are read once per second. You can choose 250 ms (smoother), 500, 1000 or 2000 ms (lighter) in Settings. With the HUD hidden and no second screen, the interval doubles by itself to save resources — but only when no session is being recorded with the game on screen. While a session is being recorded (automatic, with the game in the foreground, or manual) it always reads at the rate you chose, with or without gauges, so the report is the same. (Since version 1.1.42.)
When a sensor is missing
The app names the cause, instead of showing a silent dash. The three reasons:
| Notice | Cause | Fix |
|---|---|---|
| Limited mode | The app wasn't elevated to administrator | Close and reopen, accepting the Windows prompt |
| Temperatures unavailable | The sensor driver is missing | The app installs it; if that fails, reinstall |
| Board fans: no reading | The motherboard chip didn't answer | The app retries at 5, 20 and 45 seconds; then it gives up |
In Settings → Sensors you see, with the real name of your hardware, whether each source is answering. And Help → Export sensor diagnostics… saves a text file with every raw sensor the machine exposes — that's what you send to support.
07Sessions
You don't have to press anything. You open a game and the app starts recording.
When it starts and when it ends
| Moment | Rule |
|---|---|
| Starts | 2 seconds after a game comes to the foreground |
| Warms up | The first 15 seconds don't count toward the grade — the loading screen isn't gameplay |
| Survives | An Alt+Tab: the session doesn't split. A session is one sitting |
| Gives up | After 15 minutes out of focus with the game still open |
| Ends | When the game's process disappears (plus 5 seconds of tolerance) |
| Discards | Sessions with less than 30 seconds with the game in front, fewer than 20 samples, or average FPS below 8 |
A session has two durations, and they aren't the same thing:
- Duration — the sitting: from start to end, including the time you spent in another window. This is the one shown, and the one that matches energy and cost.
- “… in front” — the time the game was actually in front of you. It only appears when it's different — in about 5 sessions out of 100.
For example: “Duration 1h38 · 1h05 in front” — you spent an hour and thirty-eight minutes at the computer, and the game was in front of you for an hour and five.
The grade
At the end, the session gets a grade from S to D. It isn't an opinion — the calculation is shown on screen:
(1% low ÷ average)
(how close to the limit)
(minimum ÷ average)
The scale: S from 90, A from 75, B from 60, C from 40, D below that. Heat only costs points in the last 10 °C before the limit — 75 °C on the graphics in a game costs nothing.
A session with low FPS can't get a high grade, however consistent it is. The ceiling steps down with the average FPS: below 55 the maximum grade is A (85 points), below 40 it's B (70), below 30 it's C (55) and below 20 it's D (35). Without that, a steady 4 FPS would earn an “S”. When the ceiling bites, the app says so: “grade capped by low FPS”.
If the session wasn't really gameplay, there's no grade — and the app says so: “No grade — there was no gameplay in this session. Temperatures, energy and cost remain.”
Game or not a game?
The app decides by looking at the process's 3D engine, not by its name. There's also a list of 63 processes that are never a game (the Windows explorer, video players, seven browsers, game launchers, remote-access and video-call apps).
Recording by hand
Icon next to the clock → «Game sessions» → «Record session (manual)». It records whatever is happening, even without FPS — useful for stress tests. The same item turns into «Stop & save session». If an automatic session is already recording, the item already shows that way, and clicking it closes and saves that session on the spot. A manual recording is always saved and always opens the report.
Every so often the app writes a checkpoint to disk. If the computer goes down — blue screen, power cut, the process killed by force — the session isn't lost: it's recovered at the next startup and marked “This session has no ending”. The measured promise: you never lose more than 30 seconds or 10% of the session, whichever is larger.
The 200 most recent sessions are kept; the last 15 appear in the icon's menu.
08The session report
It opens by itself when you close a game that was worth it. It's the session's cover sheet.
It opens automatically if the session had at least 3 minutes with the game in front of you, 20 FPS on average and 15% average graphics load. It doesn't open, even with FPS, when the app measured that the program wasn't a game — the process's 3D engine almost idle. (Since version 1.1.47.) Weak sessions are saved silently — you can open them by hand from the «Game sessions» menu or by clicking a bar in the Timeline.
What's in it
- The grade, with the calculation shown.
- The summary line — duration, resolution and refresh rate of the monitor, average FPS, 1% low, graphics peak, energy in Wh and cost.
- The session chart, with problems marked by colored bands.
- Recent sessions in this game — up to 10 bars: this session and the previous automatic sessions of that game with at least 5 minutes with the game in front.
- The table — Avg, Min, Max, 1% low and 0.1% low, per metric.
- 💡 Insights — up to four sentences written from the numbers. The first, when it appears, compares the session with your recent normal in that game (see below).
For example: “FPS 12% below your recent normal in this game”. It only speaks up with a difference of at least 5% in FPS or 3 °C on the graphics, when that game's normal has already gathered at least 3 sessions, and only if this session had 2 minutes or more with the game in front of you. The normal only learns from automatic sessions that also reached 2 minutes in front.
It's a recent normal, not an all-time average: the last three sessions weigh about two-thirds. (The 2-minute minimum applies since version 1.1.44.)
The chart's bands
| Color | Means |
|---|---|
| Amber | The processor was saturated and the graphics had room to spare |
| Red | Thermal throttling — the graphics cut its power with the chip hot |
| Cyan | A stutter with no identified cause |
Energy and cost
The app integrates the watts over the session and converts them into Wh and the cost in your currency, at the rate you set. From that also come the cost per hour — the cost divided by the session's duration (the sitting, not just the time in front) — and FPS/W — how many frames per watt the machine delivered.
The Wh and the cost are the processor's and the graphics'. The rest of the system — memory, disks, fans, motherboard, monitor — isn't included. The real figure at the wall is higher, typically by 25 to 40%. The app writes this caveat in Health, Memory and the Monthly recap; in the session report and the share card it doesn't appear — keep that in mind when you share a number.
When one of the power readings — the processor's or the graphics' — is missing for part or all of the session, the report keeps the Wh and the cost and tells you what was missing in a line below the summary — for example “Scope: processor only — no graphics power reading in this session.” What would be a wrong figure, the app leaves out: FPS/W disappears if the watts don't cover the whole session, or when the “… in front” appears, and the share card stops carrying energy and cost.
If the graphics card didn't give its power in this session because the driver refused it from start to finish, the report explains it below the summary and the «Show me where» button appears: it opens the Windows Power Options page where Fast Startup is turned off. In other sessions the button doesn't appear.
Taking the data out
- Export CSV… — a file with 46 columns, separated by semicolons, to open in a spreadsheet. It includes both clocks, so the numbers can be checked against each other.
- Share PNG — a 1200×675 image copied to the clipboard, ready to paste into Discord. See section 11.
Comparing two sessions
«Compare sessions (A/B)…» puts two recordings side by side, with the differences colored, the FPS lines overlaid and a verdict on which one won. It's how you answer “did the new driver give me FPS?” or “did the undervolt lower my temperatures?”. The app preselects a comparable pair and warns you if the two sessions ran at different resolutions.
09The machine's memory
Five windows that answer questions about the past. It's what grows in value over time.
Machine timeline
A map of 7 days × 24 hours — 168 cells. Each cell is one hour, colored by the maximum temperature the graphics reached in that hour (cold → green → amber → red).
| Mark | Means |
|---|---|
| Cell background | The heat of that hour |
| Colored ring | A session was recorded — the color is the grade's. Clicking opens the report |
| Dashed ring | The hour had more than one session |
| Dots at the top | Sentinel warnings in that hour |
| Cyan bars | The sessions drawn on the calendar |
| Number on the right | The day's energy, in kWh |
The dots are Sentinel warnings and can't be clicked. What opens on click is a session — and there's only a ring on an hour that had a session recorded and finished. A session still running has no ring and doesn't open: it only becomes a report when it closes.
Hovering over a cell shows that hour's detail. With the mouse outside the grid, the pill below shows the week's summary.
Logbook
The written list of what happened to the machine in the last 90 days, one card per event: programs installed and removed, drivers updated, BIOS, Windows updates, disks that appeared, Sentinel warnings. Warnings get an amber ring. There are 27 kinds of event.
There's no search, sorting, grouping or export. It's a running list, newest first.
Machine memory
The accumulated portrait of this PC:
- Hours watched, sessions, hours of gaming and for how many days — “guarded since 06 Jul 2026 · 68 days”.
- Thermal heartbeat — the graphics maximum per day, up to 30 days.
- ID card — motherboard and BIOS with date, processor, graphics, each RAM stick with its XMP/EXPO profile and CL, the motherboard battery, every disk with its wear.
- Records, with dates.
- Where you spend your time — your top apps.
- Unexpected endings, always with a denominator: “2 unexpected endings in 140 watched runs”.
If your RAM is running below what the kit can do, if a stick is in the wrong slot, if the motherboard battery is weak, if a disk has passed 90% of its life — the ID card says so and explains. And the advice disappears by itself when you fix the problem.
Machine health
The monthly bulletin: hours watched, energy measured and what it cost, how hot the machine got, on which days it sweated, what went wrong, whether the PC shut down cleanly or crashed — and, at the end, one concrete thing to do. It compares with the previous month, and with the last six months in bars.
The month gets a name: Ironclad, Cool-Headed, The Survivor, Under Watch, Steady or Early Days.
Instead of showing a zero, it writes the reason: “Not comparing power: this month some hours weren't measured end to end.” A comparison needs at least 7 days with readings in both months.
Monthly recap
The celebration: hours of gaming, a named archetype (The Marathoner, The Loyal One, The Explorer, Cold-Blooded, The Balanced One), the podium of your three games, the energy used, the best session and your favorite day.
10The Sentinel
It runs on its own from the moment the app starts. It only interrupts you when hardware is at risk.
The Sentinel looks at cooling and temperatures on every reading. Almost everything it sees is recorded silently — in the Logbook, the Timeline and the monthly report. From the Sentinel, only one thing interrupts you: a processor fan or a pump that has stopped while the processor is hot.
There's also the temperature alert — sound only, no balloon — described in section 6; it isn't part of the Sentinel.
| What it watches | When it speaks |
|---|---|
| Stopped fan / pump | ≤ 60 RPM on a processor fan or a pump (a sensor with “CPU”, “Pump” or “AIO” in its name) that has already spun, with the processor above 60 °C, confirmed for 15 s. A balloon in the tray, once a minute, with sound — even with sound alerts off. “Has already spun” also covers one that spun in a previous session and was already stopped when the app started: besides the alarm, the Panel asks whether it's still there. (Since version 1.1.47.) |
| Fan losing speed | Steps of 15%, 25% and 50% compared with what that fan has already proven it can do |
| Fan recovered | When it's back to normal — and the old advice is removed |
| Warning withdrawn | When the app can no longer compare a fan it had flagged for losing speed — 15 days without being able to measure it, or an update that throws out the old yardstick. The speed-loss advice goes; a stopped fan's stays |
| Thermal warnings | Processor and graphics at the «Alerts» limits (by default 95 °C and 90 °C) and hot spot at 100 °C, when they stay there 10 seconds in a row. Recorded silently. Note the numbers aren't the temperature alert's (section 6): here the hot spot counts from 100 °C, there from 95 °C; and here it takes 10 seconds in a row, there 4 are enough |
| Processor-limited | Graphics below 70% with the processor above 90%, for 30 s in a row |
| Above your normal | +8 °C above your recent normal in that game, for 5 minutes |
The Sentinel learns what each fan in your machine has already proven it can do at each control level, and stores that on disk. There's no cloud, no account, and it doesn't need to know which fans you have in there. The same goes for temperatures: “above normal” is your normal, game by game.
11Sharing
Four images the app draws from your history and copies to the clipboard.
Each one comes from a window, with the same «Share PNG» button in the bottom-right corner: the session report, Machine memory, the Monthly recap and Machine health. They're all 1200×675, ready for Discord.
The image is born and dies on your machine: it's drawn and copied to the clipboard. No file is saved, it goes through no server. The confirmation “Copied — paste it in Discord! ✓” lasts two seconds.
Every card carries the “✔ VERIFIED BY INTERACTIVE HUD” seal. Since that puts the brand behind the numbers, the cards follow stricter rules than the rest of the app:
- Without a game, the card doesn't talk about games.
- Energy only goes out if the measurement covered the whole session, and if the energy/duration pair is arithmetically possible.
- A session with no ending gets a “≥” in front of its duration.
- The trophy doesn't go to anyone who hasn't earned it — it requires zero incidents, zero unexpected endings, no record on the yardstick, and temperature measured on both sensors.
- An empty period isn't shared.
What goes out and what never does
| Goes out | Never goes out |
|---|---|
| Processor, graphics and memory model; FPS, degrees, watts, hours watched, games played | User name, machine name, license identifier, file paths, IP address |
12Settings
Four tabs, sixteen options. Everything applies instantly — there's no “OK” or “Apply”.
It opens four ways: right-click the icon next to the clock → «Settings…», right-click a gauge → Application → «Settings…», the Settings button in the Panel footer, or the «Show me the setting» on a warning band.
General
| Option | Values | Default |
|---|---|---|
| Update interval | 250 · 500 · 1000 · 2000 ms | 1000 ms |
| Animation FPS | 30 · 60 | 30 |
| Language | Português · English · Español · Français · Deutsch · Italiano | the system's |
| Start with Windows | on / off | on |
| Show the Panel at startup | on / off | on |
| Start with the HUD hidden | on / off | on |
| Sound alerts (temperature) | on / off | on in a fresh install (if you update, you keep what you had) |
| Auto-record game sessions | on / off | on |
| Discord status (game + session grade) | on / off | off |
| Second screen (phone on your local network) | on / off | off |
| Currency | € · $ · £ · ¥ · R$ · kr · zł · Fr · custom | € |
| Electricity rate | 0.10 · 0.15 · 0.20 /kWh + custom | 0.15 |
Appearance
Gauge transparency (0 to 90%), Menu theme (Follow Windows · Light · Dark) and Panel theme (the six).
Sensors
The list of what's answering, with the real name of your hardware. And the Per-game VRAM & 3D engine switch (on by default), which reads memory and the 3D engine only for the game process in focus.
Help
Check for updates · Export sensor diagnostics · Licenses (those of third-party components) · Terms of Use (EULA) · Privacy · About.
Shows your main numbers — CPU and GPU temperature, RAM, FPS, CPU and GPU power, VRAM, fan speed and ping — in the browser of a phone, tablet or laptop on your local network: the QR code is here — scan it with the camera, or type the address — and there's nothing to install. It's off by default, uses port 8517 and has a code you can regenerate. The app creates and removes the firewall rule itself, and tells you.
Your network has to be set to Private, and the app needs administrator rights to open the port; if either is missing, it tells you.
There's no button that puts everything back to factory state. For the gauge layout there's the DEFAULT profile; for the rest, you'd have to delete the settings file (see section 14).
13Shortcuts and gestures
| Shortcut | What it does | Where it works |
|---|---|---|
| Ctrl+Alt+Z | Hides and shows the whole HUD | Inside the game, without leaving it |
| Ctrl+Alt+X | Click-through: clicks pass through the HUD | Inside the game, without leaving it |
| Ctrl+Alt+drag | Moves all the gauges as a block | Over any gauge |
| Left-click the icon | Opens the Panel | Next to the clock |
| Right-click a gauge | Opens the menu with everything | On the HUD |
| Double-click the Panel's corner | Restores the natural scale | On the Panel |
They can't be changed — they're fixed. If another app has already taken them, they don't work and the app doesn't warn you.
And with click-through on, the right-click menu can't be reached (the HUD stops receiving the mouse). The way out is Ctrl+Alt+X again, or the icon next to the clock. The first time you turn it on, the app warns you about this.
14Where the files live
Everything the app knows about your machine lives in a single folder, in your user profile:
%APPDATA%\Interactive Hud\
| Folder / file | What it holds |
|---|---|
settings.json | The settings. Written atomically, with a .bak copy |
sessions\ | One session per file. Median 18 KB; the size doesn't grow with duration |
history\ | The hours, the events and the system state. ~300 bytes per hour |
profiles\ | The layout profiles, including DEFAULT |
themes\ | Custom themes in JSON |
license.dat | The activated license |
History is kept for 24 months, which comes to about 2.6 MB per year with the PC always on. The sensor census takes more — about 3.5 MB per month.
The app installs into %LOCALAPPDATA%\InteractiveHud\ — on an installation from before the rebrand the folder may still be called MMMonitor, and it keeps receiving updates. But when you accept the administrator prompt, that isn't where it runs from. Since version 1.1.41, the first time the app starts as administrator, the Interactive Hud launcher (InteractiveHud-Lancador.exe) puts a verified copy in %ProgramFiles%\ValenorEye\Interactive Hud\, where only an administrator can write: it checks each file against the catalog signed by ValenorEye and only then runs it; if the check fails, the app runs from your profile folder, and the reason goes into the launcher's log. The same folder holds the downloaded updates (the folder ending in .pacotes) and the launcher's log, lancador.log.
When you uninstall, Windows asks for administrator permission once more: that's the launcher closing the app and deleting the Program Files copy and the start-with-Windows entry. The %APPDATA%\Interactive Hud\ folder is not deleted.
15Troubleshooting
I don't see the HUD
- Out of the box it starts hidden. Click «Show HUD» in the Panel footer, or Ctrl+Alt+Z.
- The game is in “exclusive fullscreen”. In that mode Windows hides any overlay. Switch to “borderless window” in the game's options.
- Was it left on a monitor that no longer exists? The app re-centers it by itself at startup and whenever the screens change.
Temperatures say “N/A”
Administrator elevation is missing. Close the app and open it again, accepting the Windows prompt. If the notice says «Temperatures unavailable», the sensor driver is missing — reinstall the app.
Graphics power says “N/A” but everything else works
When Windows boots with fast hibernation, the graphics driver refuses the power reading for the whole session. Load, temperature and fan answer; only power fails. Shutting down and turning it back on doesn't fix it — only «Restart» does. To avoid it for good, the Panel's band takes you to the right Windows page.
The board fans don't show up
The motherboard chip didn't answer the first time. The app retries at 5, 20 and 45 seconds and then gives up. Closing and reopening the app gives it another chance. Not every board exposes these sensors.
Clicking the HUD takes focus away from my game
That's how it works: any gesture on the overlay (dragging, resizing, opening the menu) takes focus from the game. That's why the two shortcuts are global — so you can tidy the HUD without leaving the game.
FPS stays at “N/A”
The measurement follows the window in the foreground and expires after 2.5 seconds without new frames. Outside an app that draws, it stays “N/A”. Note the opposite is also true: if you have any app in front that's drawing, it is measured.
I want the file to send to support
Help → Export sensor diagnostics… — saves everything the machine exposes, with names and values.
16What this version doesn't do
We'd rather you know before you go looking. This list is from the 1.1.51 code.
| Limitation | Detail |
|---|---|
| Stopped-fan alarm | It only watches sensors with “CPU”, “Pump” or “AIO” in the name. On a board that calls its fans “Fan #1”, “Fan #2”…, there's no stop alarm. The speed-loss warning covers all of them, but only when the board shows the percentage it drives the fan at, and above 20% |
| Exclusive fullscreen | No overlay appears in that mode. It can't be worked around |
| Energy | It counts only the processor and the graphics — it isn't the figure at the wall |
| Shortcuts | Fixed, not configurable, and no warning if another app took them |
| “Always on top” | Can't be turned off |
| Transparency | It's global, never per gauge |
| Light mode | Doesn't reach the gauges or the merges |
| Restore defaults | Doesn't exist |
| Monitor statistics | Only in memory — lost when you close |
| Trend chart | 64 readings, lost when you close |
| Frametime | It's 1000÷FPS, not the real time of each frame |
| 1% low and 0.1% low | They come from the moving average of the last 50 frames, not from each frame: a short stutter shows up diluted, and the value shown can sit well above what a frame-by-frame measurement would give |
| Two dedicated graphics cards | Detailed telemetry is always from the first card |
| Laptops | No battery reading and no system power |
| Creating themes | Only by writing JSON by hand; there's no editor |
| Style names | The names of the 15 card styles, 19 merge looks and 20 palettes aren't translated |
| Logbook | No search, filters or export |
| Merges | Only cards merge; a merge is split, not deleted |
| Trial version | Doesn't exist |
Supported hardware
| Component | Support |
|---|---|
| Processor | Intel and AMD |
| Graphics | NVIDIA (most complete reading), AMD and Intel integrated |
| Memory | DDR4 and DDR5, with the XMP/EXPO profile and CL read |
| Disks | SATA and NVMe, with wear |
| Board fans | Only on boards whose chip answers |
| Hot Spot / graphics memory temperature | Only on cards that expose those sensors |
On integrated graphics there's no thermometer of its own: the app uses the processor's temperature — that's correct, because they live on the same chip, but you'll see the same number on two lines. The temperature alert counts it only once, against the processor's limit.
17Privacy
The app was built to work without telling us anything.
What leaves your machine, and only this:
- License activation and revalidation — the key, the PC's identifier and the motherboard's (both already transformed — we never see the original numbers), and the app version. At startup and then every 12 hours.
- The update check — two requests to our catalog (the catalog and its signature), carrying the version you have installed and the Windows architecture (x64). If you choose to install, the update downloads from the same server.
- Ping — one request per second to 1.1.1.1, to measure latency. It always runs, even with no network gauge open.
- Discord status — only if you turn it on. It's off by default.
- The second screen — only if you turn it on, and only inside your local network. It's off by default.
About once a minute, the app reads the raw values of every sensor in the machine and stores on disk a summary of each hour (average, minimum and maximum of each sensor) — that's what lets it tell you, months later, that “your RAM has been running at 4800 since Tuesday's BIOS”. It stays on your computer and is never sent. It takes about 3.5 MB per month and is deleted after 24 months. In this version it has no switch in the interface.
If you want to delete everything the app knows about your machine, delete the %APPDATA%\Interactive Hud\ folder.