Diagnosis
Explains the result and identifies a priority instead of returning only a score.
Tester guide
FPS Performance Lab documentation
Learn how the application works before your first test. This guide explains the workflow, Windows Raw Input measurement, score interpretation, data quality, training and comparable retests.
01 · Before you begin
Purpose and safety
FPS Performance Lab is a standalone offline environment for diagnosing and training aim control. It measures movement initiation, target stopping, tracking and repeatability, then proposes one training priority and a comparable retest.
A local, standalone tool
The application does not read game memory, analyse game video, run as an overlay, communicate with
game processes, control the mouse or keyboard, or automate aiming. Measurement and training take
place only inside the application window.
Training
Prepares short sessions focused on reaction, flick, tracking, precision or recoil control.
Verification
Uses equivalent conditions to distinguish progress from a configuration change.
User control
Recommendations are informational and must be applied manually.
02 · Current closed test
Changes available in version 1.3.8
A new measurement baseline
Version 1.3.x Raw Input results should not be directly compared with measurements captured by the
older WPF-input generation. The first complete test after updating establishes a new baseline.
03 · Initial setup
First launch and language selection
- Launch FPS Performance Lab.exe and select Polish, English or German.
- Enter the known context: target game or profile, DPI, sensitivity and display information.
- Select your current mouse. Use the custom option when the model is not in the catalogue.
- Open Aim Control Test and confirm the conditions before starting.
- Complete the stages without changing DPI, sensitivity or hardware.
- Review ControlIndex, data quality, recommendations and the training plan.
The selected language is stored locally and can be changed later in Settings.
04 · Navigation
Application modules
05 · Input acquisition
Windows Raw Input and measurement conditions
Version 1.3.x receives mouse movement and buttons through Windows Raw Input (WM_INPUT) with a high-resolution clock. Data is processed only while the FPS Performance Lab window is active. The application never moves the pointer and never sends input to Windows or a game.
| Recorded context | Purpose |
|---|---|
| Input acquisition method | Separates Raw Input results from older WPF measurements. |
| Sampling quality and gaps | Identifies interruptions and unreliable streams. |
| Active-window state | Rejects or labels trials affected by focus loss. |
| Anonymous device identifier | Recognises a changed device without storing its device path. |
Raw Input is not a game integration
It is a Windows input API used inside the application window. FPS Performance Lab does not attach
to or communicate with a game process.
06 · Interpretation
ControlIndex, supplementary scores and data quality
ControlIndex combines four pillars: target switching, target stopping, target tracking and trial repeatability. Reaction and recoil control are supplementary results and do not automatically lower the main score.
| Area | Meaning | Role |
|---|---|---|
| Target switching | Movement time, path and corrections. | Main-score pillar |
| Target stopping | Deceleration and final position near the centre. | Main-score pillar |
| Target tracking | Time on target, proximity, continuity and recovery. | Main-score pillar |
| Repeatability | Consistency across consecutive trial blocks. | Main-score pillar |
| Reaction | Time to detect and initiate a response. | Supplementary |
| Recoil control | Burst grouping and manual compensation. | Supplementary |
A report also includes measurement quality and conclusion confidence. Warnings remain visible but are not silently deducted from ControlIndex. Insufficient data is labelled as such instead of being presented as a zero score.
07 · Progress
Comparable tests and trend analysis
Progress is meaningful only when the input method, application and algorithm versions, device, sensitivity, display context and test length are comparable. History retains older records, but the active trend excludes incompatible sessions and explains the difference.
- Keep the same mouse, DPI, sensitivity and profile.
- Use the recommended equivalent test form and similar conditions.
- Complete at least three comparable tests for expanded trend analysis.
- After changing the mouse, establish a new baseline before interpreting the trend.
08 · Configuration context
Game Profiles and the popular-game catalogue
Game Profiles store the target context, FOV, sensitivity, ADS and notes. Version 1.3.8 includes popular titles and neutral Tactical, Tracking and Arena FPS categories. Recommendations show values, instructions, confidence and warnings for manual application; the application does not edit game files.
09 · Output
Recommendations and reports
The final view explains the score, data quality, strongest area, training priority and retest plan. Settings recommendations cover DPI, sensitivity, eDPI, estimated cm/360 and ADS when enough data is available. Mouse guidance describes functional parameter ranges rather than forcing a product purchase.
- PDF and TXT reports use the active application language.
- Report comparison can include a previous comparable result.
- Values are recommendations and must be applied manually.
10 · Storage
Local files, backup and privacy
Application data is stored in:
%LOCALAPPDATA%\FPSPerformanceLabSettings provide access to the data folder, export, backup, restore and history reset. The product website does not read these files. Data reaches the owner only when the user exports and sends it.
Local by default
The application stores training sessions, tests, profiles, settings and reports on the user's device.
11 · Closed-test procedure
How to report a reproducible issue
- Record the application version, Windows version, display resolution and scaling.
- Describe the module, stage and exact click sequence.
- State the expected and actual result.
- Attach a screenshot and an appropriate exported report only when you choose to share it.
- Confirm whether the issue can be reproduced.
Tester contact: m.rupinski@mrserwis.net.
12 · Frequently asked questions
Tester FAQ
Does reaction 0/100 always mean an error?
No. If valid trials and a measured time are present, zero can mean the result is beyond the upper descriptive threshold. Missing data is labelled separately.
Why did the recommendation keep my DPI unchanged?
The application prefers training and a comparable retest before recommending sensitivity changes. A change requires a repeated pattern and sufficient data quality.
Can I compare results after changing the mouse?
Both results remain in history, but they belong to different hardware contexts. Establish a new baseline on the new mouse before interpreting a trend.
Does the application change game settings?
No. Every recommendation is applied manually by the user.
What is the status of Setup Optimizer?
Windows Raw Input measurement is active. Setup Optimizer remains a separate development feature and does not automatically change game or system settings.