Horizontal and Vertical Mouse Sensitivity
Horizontal and vertical camera movement can feel different when an application uses separate axis controls or another view-related modifier. That possibility should be checked before diagnosing hardware.
A practical approach
Use a stable scene and compare deliberate movements in each direction. Inspect the application settings for separate axes, inversion or aiming modifiers. Record the original values before testing a change. A desktop drawing test can provide a separate observation, but it does not reproduce every game camera rule or prove the cause of a difference.
Separate axis settings can change movement geometry
Some software offers different horizontal and vertical scaling. When those values differ, the relationship between physical movement and output can change by direction. That may be intentional for a particular workflow, but it should not be mistaken for a sensor defect without checking the configuration.
Record any separate axis settings supported by the exact device or application. Compare ordinary horizontal, vertical and diagonal movements under a stable setup. Do not assume every mouse or game provides the same options. If the behavior appeared after a profile change, restore the documented baseline before investigating hardware. Keeping the configuration visible is a simpler first step than replacing a device because diagonal movement feels unfamiliar.
Raw input is a software path, not a complete latency guarantee
Applications can obtain mouse movement through different input paths. Raw input exposes device movement information in a way that differs from ordinary cursor handling, but the application's own processing still matters. A raw-input option should not be interpreted as a promise that every setting, delay or compatibility issue disappears.
Check the documentation for the specific game or application and record the selected mode. Keep desktop pointer behavior separate from the movement observed in that application. When troubleshooting, change one relevant option and compare the same task. Avoid assuming that a similarly named option behaves identically in every title or software version. The practical goal is to understand the actual input route rather than use a label as a substitute for testing.
Sensor specifications do not describe the whole mouse
A sensor name or maximum setting can provide useful product information, but implementation, firmware, shape and the rest of the device still matter. Two mice sharing a sensor family should not automatically be assumed to behave identically in every respect. A specification is not a substitute for suitable testing.
For ordinary use, begin with reliable tracking on a known surface and stable supported settings. Separate motion behavior from button response or connection problems. When comparing published measurements, check the method and exact model. Avoid buying solely on a maximum DPI number or treating a familiar component name as a complete quality guarantee. The device should be evaluated as an integrated tool for the tasks it will actually perform.
An example to work through
For example, an accidentally changed vertical multiplier may make upward corrections feel unusually strong while horizontal turns remain familiar. Replacing the mouse would not address that setting.
What to check
- Inspect axis and inversion options.
- Compare movements in a stable scene.
- Keep application behavior separate from device diagnosis.
Sources and further guidance
Microsoft Learn: raw mouse input