KeyCast v1.2.0

This release makes the mouse movement indicator work inside games, answering the most common question about v1.1.0.

New

• In-game movement capture. The movement indicator now reads the Windows Raw Input stream, the same source games read mouse motion from. Games that lock the pointer in place used to leave the indicator flat because the on-screen cursor never moved; the indicator now sees exactly what the game sees and keeps working while you play. Nothing to configure, the indicator simply works where it previously did not.
• The privacy story gets stronger, not weaker: the raw input stream carries only relative movement counts, so on this path no cursor position exists anywhere in KeyCast. Only the direction of movement is ever sent to the overlay. The capture is active only while a profile shows the indicator, exactly as before. The reader is a small auditable C file in the repository (native/rawinput).
• The diagnostics report now names the active movement capture path, so a support thread can tell instantly whether in-game movement should work on a given setup.

Notes for running from source

The in-game capture is a small native module that the installer ships prebuilt. Running from source, build it once with "npm run build-native" (requires the Visual Studio Build Tools C++ workload). Without it the indicator falls back to following the cursor, which pointer-locking games limit; everything else is unaffected.

Installation

Download the installer below and run it. Windows SmartScreen may warn on first launch because the app is not code-signed; choose More info, then Run anyway. Requires Windows 10 or 11 (64-bit). Installed copies can update from within the app.