VALORANT Raw Input Buffer: Missing Toggle & Input Checks
Raw Input Buffer is always enabled on VALORANT PC. Riot removed its configurable toggle in patch 11.06 on September 16, 2025. A missing switch is therefore expected; it is not, by itself, evidence of a broken installation.
Reviewed October 12, 2026 against Riot’s patch history, including 13.06. This is a source-based diagnostic guide, not a measured mouse-latency benchmark.
The three changes that explain conflicting guides
| Official patch | Change | How to read an older guide |
|---|---|---|
| 3.07 · October 5, 2021 | A beta Raw Input Buffer option was introduced. | An On/Off screenshot can be historically accurate. |
| 7.12 · December 5, 2023 | Beta label removed; default changed to On. Existing values were unaffected. | A new default did not force every existing account to change its saved choice. |
| 11.06 · September 16, 2025 | PC toggle removed; buffering enabled at all times. | An instruction to switch it On or Off no longer describes this control. |
Raw input and the buffer option were not the same launch event. Riot’s 3.07 notes say the game already used raw input; buffering changed the processing APIs. Its historical performance description distinguished standard mice from 8,000 Hz devices. That description is not a benchmark of your current hardware or a promise of a particular FPS increase.
Why searching for the old switch cannot diagnose stutter
There is no current On/Off comparison for this removed PC control. Do not make a troubleshooting session depend on finding it in an old screenshot. First name the symptom: changed turn distance, intermittent motion, uneven frame delivery, or a problem restricted to one aiming mode. Those observations require different comparisons.
| Observation | Record first | Controlled next step |
|---|---|---|
| Same hand movement turns farther | Active DPI and hip-fire sensitivity | Restore the previous known values before testing anything else. |
| Problem appears during rapid mouse movement | Polling rate, scene, graphics settings | Compare two supported mouse polling settings with everything else fixed. |
| Both camera and scene feel uneven | When it happens and available frame-time/FPS readings | Repeat the same scene to separate scene load from mouse movement. |
| Only ADS or scope feels different | Hip-fire, ADS and scoped values | Compare the affected mode separately. |
| Intermittent disconnect or freeze | Connection, battery if applicable, receiver/cable position | Test the connection independently of sensitivity changes. |
A baseline → comparison → baseline worksheet
Use this as a troubleshooting record rather than a recommended polling-rate preset. Choose two rates your device officially supports. Keep the game scene, resolution, sensitivity, DPI, running applications and test duration the same. Save a screenshot of the starting values so you can restore them.
- Baseline A: run the same short sequence of camera movement and idle observation. Note when stutter appears and record available performance readings.
- Comparison B: change only the selected mouse setting. Repeat the sequence for the same duration. Note improvement, worsening or no clear difference.
- Return to A: restore the original value and repeat. If the behavior does not return, the first difference may have come from another changing condition.
- Repeat before concluding: a single smooth run is not enough to attribute the result to a mouse option. Keep the record and distinguish a repeatable difference from a subjective impression.
| Run | Mouse rate | Same scene/duration? | Symptom and performance notes |
|---|---|---|---|
| A: baseline | Fill in | Yes / No | Fill in |
| B: one change | Fill in | Yes / No | Fill in |
| A: restored | Original rate | Yes / No | Fill in |
A change in this worksheet is a device-setting comparison, not a test of disabling Raw Input Buffer. If several variables changed, label the run inconclusive and repeat rather than recommending a value to everyone.
DPI is a separate decision
Keep sensitivity changes outside the stutter comparison. To preserve a numerical sensitivity relationship when changing DPI, use the eDPI calculator and 800 versus 1600 DPI worked examples. Those pages address arithmetic; this page addresses the missing control and how to investigate a symptom.
Can a config edit restore it?
The reviewed Riot notes describe the control as non-configurable. This guide has no verified supported procedure for restoring the old switch and does not supply a file-edit workaround. If a problem persists, give Riot Support your actual symptom, hardware, reproduction steps and baseline/comparison record rather than reporting only that the old option is missing.
Sources and review scope
Riot 3.07 · Riot 7.12 · Riot 11.06 · Riot 13.06. The always-on change is explicitly PC-only in 11.06; it should not be repurposed as a console controller setting. No native-client or mouse latency measurements were performed for this review.