Lookout FPS, CPU usage and mouse-stutter checks

Available CPU evidence

Approximate reconstruction of 360 saved match-phase samples from before 0.1.14, on one i7-12700F PC with 20 logical processors. This is not a before/after FPS comparison.

Median

≈ 6.2%

95th percentile

≈ 7.8%

Maximum

≈ 9.6%

Lookout share of total machine CPU. Rounded saved values cannot be reconstructed exactly. These figures cannot be converted into FPS or mouse latency.

Changes in 0.1.14

Unused mouse-movement forwarding was removed. The 15-second window-list enumeration while connected was replaced by a separate window watcher. F10 hiding also pauses screen capture and OCR. CPU underreporting was corrected.

0.1.14 release notes

Compare under the same conditions

1. Keep resolution, graphics options, frame cap and the scene consistent. Record the game update and PC specs.
2. Compare Lookout fully closed, running with overlay shown, and hidden with F10. Hidden and fully closed are different conditions.
3. Where available, record low FPS and frame times as well as average FPS. Repeat the same scene to distinguish transient combat load.

If stutter remains

Disable unused elements in Settings and compare CPU usage. In feedback, describe the situation, shown-versus-hidden behavior and any FPS you measured. Review diagnostics and screenshots before consenting to send.

Measurement evidence and limits (JSON)

Related reading