InputLab v1.3.0 — Home, what else ran during a mouse run, a fairer mouse score, an interrupt layout you can edit, and a window that fits any display scaling

InputLab v1.3.0 — Home, what else ran during a mouse run, a fairer mouse score, an interrupt layout you can edit, and a window that fits any display scaling

The biggest InputLab release so far. It also carries the fixes prepared for 1.2.1, which was never published.

What's new

• Home: your PC at a glance. The app now opens on a new first tab. The hardware in six tiles; the Windows settings
  that matter for gaming, low latency and InputLab's measurements (power plan, Energy Saver, USB and PCIe power saving,
  Game Mode, Game Bar recording, GPU scheduling, display rate, mouse acceleration, Memory Integrity, the Windows clock,
  a timer test and more), each rating with its source; the BIOS points Windows cannot read, said plainly; your mouse's
  way into the PC, the cores and your last runs. Copy summary puts it on the clipboard without your PC or user name.
  Home only reads.
• "Before you measure". A short guide when you open a device tab: the BIOS (the developer's recommendation from
  building and testing about 50 PCs, with what each setting costs), Windows (the Gaming Power plan, linked) and how to
  measure on that tab. One tick turns it off; the amber button in the top bar opens it any time.
• Mouse › Result: "During this run". What else ran on your PC at the same time — CPU, DPC and interrupt time, the
  busiest programs, a program that started during the run (also marked on the interval plot) — and InputLab's own
  share. Read right before and right after the run, never during it; context, never a cause, never part of the score.
  A check with and without it found no visible effect on the measurement.
• A fairer mouse score (v2) for new runs. A gap where your mouse had nothing to send — it moved too slowly for its
  rate and DPI — no longer counts against the mouse; every other gap counts by its length. A run that moved too slowly
  says so and tells you how fast to move. Runs saved before keep their score and are never ranked against new ones.
• The report rate and the gaps, named. "8,000 Hz class · 7,995 reports/s · 99.93 % of the slots"; the plot shows the
  1st–99th percentile as a band and the gaps by kind (late, slow movement, other).
• System › Interrupts: edit the layout yourself. Drag your USB controllers, graphics card, audio and network onto
  the cores, see right away whether the layout follows the rules, write it (the current values are saved first, all
  devices together) and restart after your confirmation; Undo the change puts every device back. Suggest a
  layout fills it by the rules with a reason for every device, and a layout check under the core map says how your
  mouse's controller sits today.

Fixed

• Mouse: "Delivery rate (host)" is the USB rate the reports arrive on (8,000 Hz at 8 kHz), not 1 ÷ the most
  common interval, which on some PCs fell on one of two peaks beside 125 µs (8,403 Hz);
  gaps are counted against that slot. Runs saved before keep their values and scores.
• Display scaling: nothing is cut off any more. At 125–200 % pages lost parts and text was cut inside its own box.
  Every size now follows the display's scale, a page with too little room scrolls instead of squeezing, dialogs never
  reach past the screen, and the score breakdown scrolls instead of dropping its last rows. At 100 % nothing changes.
• A mouse at its target rate no longer "differs" from it, USB timing's Export CSV asks where to save, the
  "fix is not active any more" message says what happened, and Interrupts lists an analog keyboard as a keyboard.

Honest limits

Display scaling is laid out and checked for 1920 × 1080, 2560 × 1440 and 1366 × 768 at 100–200 %; on real hardware it
was looked at on one 2560 × 1440 screen at 100 and 150 %. The interrupt layout's write and undo are checked on one PC;
a full cycle — a measurement before, write, restart, a measurement after — has run once, on a PC whose mouse was not
held up before either (no measurable change there). Everything from 1.2
still applies — see the README (Known limitations, Is it safe?).

System requirements

• Windows 11 or Windows 10, 64-bit (x64); tested on Windows 11 only. Self-contained: the .NET 10 runtime is
  included — unzip the whole folder and run InputLab.exe.
• Unsigned. On the first run Windows SmartScreen may say "Windows protected your PC" — click More info → Run
  anyway. With Smart App Control switched on, Windows blocks the app (there is no "Run anyway").
• USB timing, the interrupt measurement, the interrupt fix and writing a layout need administrator rights (Windows asks
  each time); everything else runs without.

Verify the download

• The zip's SHA-256 is on the release page. Check it in PowerShell:
  Get-FileHash .\InputLab-v1.3.0-win-x64.zip -Algorithm SHA256
• Inside the zip, SHA256SUMS.txt lets you check every file — in git-bash or WSL: sha256sum -c SHA256SUMS.txt
• BUILDINFO.txt names the source commit, the .NET SDK, the bundled .NET runtime and the pinned obfuscation-tool
  version.
• SHA-256 of InputLab-v1.3.0-win-x64.zip:
  af491b31010b6cdfcb44c638c7aeeb7bb7e0f96f13324e18b59bb00cc91b9b90