The primary goal for optimizing RawInput in Siege is Input Linearity and Polling Stability. Rainbow Six Siege features a “Raw Input” toggle in the menu, but manual adjustments in the configuration file allow for deeper control over the MouseAccumulation and RefreshRate synchronization. This configuration focuses on stripping away any software-side smoothing that could cause “mouse floatiness,” especially in high-stress gunfights.
Hardware & System Prerequisites
- High Polling Rate Mouse: These settings work best with mice capable of 1000Hz or 8000Hz.
- NVIDIA Reflex / AMD Anti-Lag: Ensure these are enabled in-game to complement the RawInput tweaks, as they reduce the “Click-to-Photon” delay.
- Windows Settings: Go to “Mouse Settings” > “Additional Mouse Options” > “Pointer Options” and ensure “Enhance pointer precision” is unchecked.
File Location
Rainbow Six Siege stores its configuration files in your Windows Documents folder, categorized by your unique Ubisoft account ID:
%USERPROFILE%\Documents\My Games\Rainbow Six - Siege\[Unique-ID]\GameSettings.ini
Technical Configuration (Code Block)
Open the GameSettings.ini and look for the [INPUT] section. Modify the following lines to achieve the most responsive aiming experience:
[INPUT]
# 1 = Enabled (Mandatory for Zero Latency)
RawInputMouseKeyboard=1
# Disable any legacy smoothing/acceleration
MouseAcceleration=0
MouseSensitivityMultiplierUnit=0.020000
MouseYawSensitivity=50
MousePitchSensitivity=50
# Advanced Latency & Polling Settings
# 0 = No accumulation (Prevents input "clumping")
MouseAccumulation=0
# Ensure the game logic updates as fast as your sensor
HighPrecisionMouseMode=1Strategy for RawInput Optimization
To achieve “Pixel-Perfect” aim in Siege:
- MouseAccumulation = 0: This is a “hidden” setting for many players. When enabled (1), the engine “collects” mouse movements over a few milliseconds before rendering the frame. Setting this to 0 forces the engine to process every single movement packet immediately as it arrives, which is vital for high-resolution sensors.
- Sensitivity Multiplier: Many pro players change the
MouseSensitivityMultiplierUnitfrom 0.02 to 0.00223. This allows for a much wider range of “Low Sens” adjustments, giving you more granular control over your micro-flicks. - High Precision Mode: Enabling
HighPrecisionMouseModetells the game engine to utilize the latest Windows APIs for input handling, which specifically improves the stability of mice with high polling rates (2000Hz+), preventing the “stuttering” camera movement some users experience.
Key Performance Parameters
| Parameter | Recommended Value | Impact |
| RawInputMouseKeyboard | 1 | Bypasses Windows’ mouse settings entirely. |
| MouseAccumulation | 0 | Removes the tiny buffer between movement and action. |
| HighPrecisionMouseMode | 1 | Improves stability for 1000Hz+ polling rate mice. |
| MouseAcceleration | 0 | Ensures a 1:1 physical-to-virtual movement ratio. |
Frequently Asked Questions (FAQ)
Does RawInput affect my Windows sensitivity?
No. When RawInputMouseKeyboard=1 is active, Siege ignores your “6/11” Windows slider and the “Enhance Pointer Precision” box. The game only cares about your mouse’s DPI and the in-game sensitivity value.
Why does my mouse feel “jittery” after these changes?
If you have a very high DPI (above 3200) and low in-game sensitivity, you might feel jitter. Try lowering your DPI to 400 or 800 and increasing the in-game sensitivity to compensate; this often results in a smoother input curve.
Is there a difference between the UI toggle and the .ini file?
The UI toggle changes the same primary setting, but the .ini file allows you to verify that MouseAccumulation is truly disabled, which is often hidden from the standard in-game menu.
Should I use 8000Hz polling with these settings?
Yes. Siege is one of the better-optimized games for high polling rates. However, ensure your CPU can handle the extra interrupt load, as 8000Hz can increase CPU usage significantly during rapid movements.
Conclusion and Expected Results
By manually refining your GameSettings.ini to prioritize direct sensor data and disabling input accumulation, you are removing the final software barriers between your hand and the game engine. You can expect instantaneous flick response, the elimination of “aim drift,” and a much more consistent feel when tracking fast-moving targets like Ash or Scout.