Windows exposes multiple layers that all multiply together, which is why changing any of them changes how the mouse feels even if DPI in Logitech G Hub is fixed.
- Why there are “two bars” in Windows 11
In Windows 11 mouse settings there are mainly two relevant controls:
- Mouse pointer speed slider (1–20)
- Enhance pointer precision (EPP), which turns Windows pointer acceleration (ballistics) on or off
The 1–11 scale seen in many guides is the older representation of the same pointer speed setting; internally Windows uses a small set of discrete multipliers. The “middle” value (commonly referred to as 6/11 in older UIs) is the neutral point where Windows applies a 1.0 multiplier to raw counts (with EPP off).
So effectively:
- Logitech G Hub DPI = hardware counts per inch from the mouse sensor
- Windows pointer speed slider = OS multiplier on those counts
- Enhance pointer precision = non‑linear acceleration curve on top of that
Games may then apply their own sensitivity multiplier and may or may not use raw input.
- What each layer does and how to get “true” DPI
“True DPI” in this context means: how many on‑screen pixels the pointer moves per inch of physical mouse movement, after all multipliers.
Conceptually:
Effective sensitivity = Mouse DPI (G Hub) × Windows pointer speed multiplier × (pointer acceleration curve, if EPP on) × Game sensitivity
Details from the platform behavior:
- High‑definition mice report high‑resolution raw data (800+ DPI) through the HID stack.
- WM_MOUSEMOVE messages are scaled to screen pixels and have Windows pointer acceleration and speed applied; they are limited by screen resolution and do not expose full high‑DPI precision.
- WM_INPUT (raw input) delivers unscaled, unaccelerated counts directly from the HID stack, preserving full DPI precision.
From this:
- If a game uses WM_MOUSEMOVE, it is affected by Windows pointer speed and EPP.
- If a game uses WM_INPUT (raw input), it bypasses Windows pointer speed and EPP and sees only the hardware DPI and the game’s own sensitivity.
Therefore, “true DPI” for raw‑input games is simply the DPI set in Logitech G Hub. For non‑raw‑input apps, “true DPI” is DPI × Windows pointer speed multiplier (and acceleration if enabled).
- Why changing Windows sliders still changes feel
Because many games and desktop apps do not use raw input; they rely on WM_MOUSEMOVE. As documented:
- WM_MOUSEMOVE applies pointer acceleration and is limited to screen resolution.
- WM_INPUT is raw and unfiltered.
So when a game does not explicitly use raw input, Windows pointer speed and EPP absolutely matter, and changing those sliders changes the effective sensitivity even though the mouse DPI is fixed.
- How to get stable sensitivity across games
To make sensitivity as consistent as possible across different titles:
- Fix hardware DPI in Logitech G Hub
- Choose one DPI value (for example, 800, 1200, or 1600) and disable DPI cycling or extra stages.
- Normalize Windows settings
- Set Mouse pointer speed to the neutral middle value (the classic “6/11” equivalent).
- Turn Enhance pointer precision Off to remove OS acceleration.
- This makes Windows act as a 1.0 multiplier for apps that do not use raw input.
- Prefer games that support raw input
- In each game, enable options like “Raw Input,” “Raw Mouse Input,” or “Direct Input from mouse.”
- Then tune only the in‑game sensitivity slider; Windows settings no longer affect these games.
- For games without raw input
- They will still be affected by Windows pointer speed and EPP.
- With pointer speed at neutral and EPP off, at least the scaling is linear and consistent; adjust only the in‑game sensitivity to match feel.
- Why not just set DPI in Windows and ignore vendor software
Windows does not control the physical DPI of the mouse sensor. It only scales the counts it receives. Logitech G Hub (or similar vendor software) configures the device firmware to report a specific DPI. That is the base resolution; Windows then optionally scales it.
So:
- Vendor software: sets actual sensor DPI.
- Windows: multiplies or accelerates the counts it receives.
To avoid “inconsistent bars,” the most stable approach is:
- Configure DPI once in Logitech G Hub.
- Set Windows pointer speed to neutral and disable Enhance pointer precision.
- Use per‑game sensitivity (and raw input where available) to match feel.
This aligns with the platform guidance that WM_INPUT (raw input) is the best method to receive high‑definition mouse data, while WM_MOUSEMOVE (affected by Windows sliders) is better only for typical pointer control.
References: