<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel><title>The RigSight log</title><link>https://rigsight.app/blog/</link><description>Notes from building RigSight, a free PC monitor for Windows.</description><language>en</language><item><title>A year in review from your own PC, not only Steam</title><link>https://rigsight.app/blog/pc-year-in-review</link><guid>https://rigsight.app/blog/pc-year-in-review</guid><pubDate>Tue, 17 Nov 2026 12:00:00 +0000</pubDate><description>Steam Replay arrives in mid-December and covers your Steam games. RigSight&#x27;s year Rewind is made from your own PC&#x27;s history once the year ends, with every game, the hottest moments and what went wrong. What goes in it, and what my October looked like.</description></item><item><title>What my own chats with RigSight AI got wrong</title><link>https://rigsight.app/blog/fixing-the-ai-from-my-own-chats</link><guid>https://rigsight.app/blog/fixing-the-ai-from-my-own-chats</guid><pubDate>Thu, 12 Nov 2026 12:00:00 +0000</pubDate><description>For two weeks I asked RigSight AI about my own PC like anyone would, then read every answer. It assumed a 144 Hz screen, suggested the same fix three times, and blamed a September crash on a November update. What I changed after each.</description></item><item><title>Why opening RigSight from the tray waited up to a second</title><link>https://rigsight.app/blog/tray-open-speed</link><guid>https://rigsight.app/blog/tray-open-speed</guid><pubDate>Thu, 12 Nov 2026 12:00:00 +0000</pubDate><description>Every time you opened RigSight from the tray, a notification or a widget, it waited 290 ms to over a second before the window even started. The tests never saw it, because they started the window another way. How 1.11.0 cut it to tens of milliseconds.</description></item><item><title>Two numbers from my own PC that couldn&#x27;t be true</title><link>https://rigsight.app/blog/numbers-that-couldnt-be-true</link><guid>https://rigsight.app/blog/numbers-that-couldnt-be-true</guid><pubDate>Wed, 11 Nov 2026 12:00:00 +0000</pubDate><description>Writing these guides from my own history, I found a game using 146 GB of a 12 GB GPU and a 16 GB PC using 20.8 GB of RAM. Neither was real. Where each came from, and what 1.10.0 changed.</description></item><item><title>Rebuilding RigSight&#x27;s widgets as boxes of tiles</title><link>https://rigsight.app/blog/widgets-from-tiles</link><guid>https://rigsight.app/blog/widgets-from-tiles</guid><pubDate>Wed, 11 Nov 2026 12:00:00 +0000</pubDate><description>RigSight 1.9.0 turned every widget into a box you fill with tiles, your readings next to a clock, notes, a to-do list or the weather. Getting there meant centring clocks by their ink and making a picture on the desktop take clicks and typing.</description></item><item><title>Should RigSight be rewritten in Rust? I measured first</title><link>https://rigsight.app/blog/rewrite-in-rust</link><guid>https://rigsight.app/blog/rewrite-in-rust</guid><pubDate>Sat, 07 Nov 2026 12:00:00 +0000</pubDate><description>RigSight felt slow to open, and I wondered whether parts of it should be rewritten in Rust. Measuring every part said no. The slow parts were drivers, Windows and the way the window started, and fixing those made it open in about 1.1 seconds instead of 1.9.</description></item><item><title>Rewriting all 5,445 sentences RigSight shows</title><link>https://rigsight.app/blog/plain-words</link><guid>https://rigsight.app/blog/plain-words</guid><pubDate>Thu, 05 Nov 2026 12:00:00 +0000</pubDate><description>On 5 November I wrote down how RigSight should talk, then checked every one of the 5,445 texts the app shows against it. The rule that mattered most was to say what happened and never guess at why.</description></item><item><title>Checking ping without asking anyone&#x27;s server</title><link>https://rigsight.app/blog/ping-without-a-server</link><guid>https://rigsight.app/blog/ping-without-a-server</guid><pubDate>Wed, 04 Nov 2026 12:00:00 +0000</pubDate><description>The rebuilt Network page checks your ping every 5 seconds, and it doesn&#x27;t ask any outside server to do it. How RigSight finds your provider&#x27;s first router, the router that ignored empty pings, and the colour rule the page follows.</description></item><item><title>Taskbar tiles worked on my taskbar, not on theirs</title><link>https://rigsight.app/blog/taskbar-tiles</link><guid>https://rigsight.app/blog/taskbar-tiles</guid><pubDate>Tue, 03 Nov 2026 12:00:00 +0000</pubDate><description>A GitHub issue asked for more colourful taskbar readings. RigSight 1.2.0 gave every reading a tile and a look of its own, and a bug report 94 minutes later showed a fallback I had never told anyone about.</description></item><item><title>Testing an AI on PCs that don&#x27;t exist</title><link>https://rigsight.app/blog/testing-ai-on-fake-pcs</link><guid>https://rigsight.app/blog/testing-ai-on-fake-pcs</guid><pubDate>Sun, 25 Oct 2026 12:00:00 +0000</pubDate><description>To check the helper&#x27;s advice on games, I built pretend PCs with known problems. Most of what went wrong wasn&#x27;t the AI. It was what I was feeding it.</description></item><item><title>Picking an AI model blind, and not picking my favourite</title><link>https://rigsight.app/blog/choosing-a-model-blind</link><guid>https://rigsight.app/blog/choosing-a-model-blind</guid><pubDate>Wed, 21 Oct 2026 12:00:00 +0000</pubDate><description>Six AI models answered the same questions about my PC, hidden behind letters A to F. Gemini 3.8 Flash won my vote. Claude Haiku 5.5 got the job.</description></item><item><title>Three ways to ask, including one that never leaves your PC</title><link>https://rigsight.app/blog/three-ways-to-ask</link><guid>https://rigsight.app/blog/three-ways-to-ask</guid><pubDate>Tue, 20 Oct 2026 12:00:00 +0000</pubDate><description>The helper can run on your own PC, on your own AI account, or through RigSight. Why there are three, and what each one sends.</description></item><item><title>Putting RigSight into Spanish, all 3,097 lines of it</title><link>https://rigsight.app/blog/rigsight-in-spanish</link><guid>https://rigsight.app/blog/rigsight-in-spanish</guid><pubDate>Mon, 19 Oct 2026 12:00:00 +0000</pubDate><description>People asked for Spanish. Translating the words was the easy part. Sentences built from English pieces, and a history stored in English, were the hard part.</description></item><item><title>Bringing AI back, with rules this time</title><link>https://rigsight.app/blog/bringing-ai-back</link><guid>https://rigsight.app/blog/bringing-ai-back</guid><pubDate>Sat, 17 Oct 2026 12:00:00 +0000</pubDate><description>Nine days after removing Riggy, I started on a real AI helper. Before writing any of it, I wrote down what it would never be allowed to do.</description></item><item><title>Teaching crashes to say how sure they are</title><link>https://rigsight.app/blog/how-sure-is-it</link><guid>https://rigsight.app/blog/how-sure-is-it</guid><pubDate>Wed, 14 Oct 2026 12:00:00 +0000</pubDate><description>Every crash now says what most likely caused it and how sure that is. Getting there meant one big feature, and cutting most of the next one.</description></item><item><title>Making RigSight work without admin rights</title><link>https://rigsight.app/blog/standard-accounts</link><guid>https://rigsight.app/blog/standard-accounts</guid><pubDate>Tue, 13 Oct 2026 12:00:00 +0000</pubDate><description>On a standard Windows account RigSight asked for an admin password at every start and recorded nothing without one. Here&#x27;s how it learned to do what it can, and say what it can&#x27;t.</description></item><item><title>The tests said 15 milliseconds. The app froze.</title><link>https://rigsight.app/blog/tests-passed-app-froze</link><guid>https://rigsight.app/blog/tests-passed-app-froze</guid><pubDate>Thu, 08 Oct 2026 12:00:00 +0000</pubDate><description>Switching pages felt slow, but every test passed. Made-up history was too tidy to show the problem. Real history showed it at once.</description></item><item><title>The driver update that knocked RigSight out</title><link>https://rigsight.app/blog/driver-update-crash</link><guid>https://rigsight.app/blog/driver-update-crash</guid><pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate><description>An NVIDIA driver update crashed RigSight&#x27;s recorder ten seconds after the new driver started, and nothing brought it back.</description></item><item><title>Three ways my temperature chart was lying</title><link>https://rigsight.app/blog/honest-charts</link><guid>https://rigsight.app/blog/honest-charts</guid><pubDate>Wed, 07 Oct 2026 12:00:00 +0000</pubDate><description>Peaks that moved every second, a 74° high that never showed on the line, and a gap that looked exactly like a cool PC.</description></item><item><title>Riggy, the helper I shipped and removed two days later</title><link>https://rigsight.app/blog/riggy</link><guid>https://rigsight.app/blog/riggy</guid><pubDate>Tue, 06 Oct 2026 12:00:00 +0000</pubDate><description>The first try at letting you ask RigSight questions. It was clever, it was careful, and it wasn&#x27;t really AI. So it went.</description></item><item><title>Bugs that make no noise</title><link>https://rigsight.app/blog/quiet-bugs</link><guid>https://rigsight.app/blog/quiet-bugs</guid><pubDate>Tue, 06 Oct 2026 12:00:00 +0000</pubDate><description>Internet use that silently stopped being recorded, an app &#x27;updated&#x27; 45 minutes early, and a game &#x27;installed&#x27; ten minutes into a 55 GB download.</description></item><item><title>My PC wasn&#x27;t losing power in its sleep</title><link>https://rigsight.app/blog/power-loss-while-asleep</link><guid>https://rigsight.app/blog/power-loss-while-asleep</guid><pubDate>Thu, 01 Oct 2026 12:00:00 +0000</pubDate><description>RigSight said my PC kept losing power while asleep. It didn&#x27;t. I had misread a number in Windows&#x27; own crash record.</description></item><item><title>How light is light? Measuring an app that never closes</title><link>https://rigsight.app/blog/how-light</link><guid>https://rigsight.app/blog/how-light</guid><pubDate>Wed, 30 Sep 2026 12:00:00 +0000</pubDate><description>Someone suggested rewriting RigSight&#x27;s sensor reading in C++. Measuring first showed where the time really goes, and that I had read the wrong memory number.</description></item><item><title>The day RigSight told me my healthy fan was clogged</title><link>https://rigsight.app/blog/like-for-like</link><guid>https://rigsight.app/blog/like-for-like</guid><pubDate>Tue, 29 Sep 2026 12:00:00 +0000</pubDate><description>A warning that compared a resting PC with a gaming one, and the rule it left behind. Compare like with like, or say nothing.</description></item><item><title>Getting numbers inside a fullscreen game</title><link>https://rigsight.app/blog/overlay-in-fullscreen-games</link><guid>https://rigsight.app/blog/overlay-in-fullscreen-games</guid><pubDate>Sun, 27 Sep 2026 12:00:00 +0000</pubDate><description>Why a normal window can&#x27;t draw over some games, how RivaTuner gets around it, and the see-through panel that turned solid black.</description></item><item><title>Day one, and 25 versions before midnight</title><link>https://rigsight.app/blog/day-one</link><guid>https://rigsight.app/blog/day-one</guid><pubDate>Wed, 23 Sep 2026 12:00:00 +0000</pubDate><description>The first public day of RigSight, what it set out to do, and the first mistake it shipped, which counted the page file as RAM.</description></item></channel></rss>
