Steam Every other shooter asks for speed. Siege asks your hand to disagree with itself
Swinging an angle means strafing right while leaning left — two directions at once, held, while you aim and usually crouch. No other game on this site demands opposed inputs like that, and it has two consequences nobody tells you about: your keyboard may not physically deliver the chord, and on a controller the lean button is also the knife.
Pick a peek and hold every key in it at once, exactly as you would in a round. A keyboard matrix has limits, and when it hits one it does not warn you — the key simply never arrives. This is not a general key test; each chord below is a thing you do in Siege, and the verdict is in those terms.
Click here first so the page receives your keys, then hold them all together.
—
Pick a peek above and hold every key in it at once.
Reversing a swing means letting go of one opposed chord and building the other: D+Q becomes A+E. Everything in between is time spent in the open holding no lean at all. Under 180 ms it reads as one movement; much over and it reads as a stop.
Click here, hold one side, then switch to the other as fast as you can.
Hold one peek, then switch to its mirror as fast as you can. Three attempts before the number means anything.
Everything above is a keyboard problem and a controller player does not have it — there is no matrix to drop a key. What they have instead is stranger, and it is right there in the shipped binds: lean is the right stick pressed while aiming, and melee is the right stick pressed. One physical input, separated by whether a trigger happened to be down.
On a controller, lean and melee are the same physical input. Lean is the right stick pressed while aiming; melee is the right stick pressed. Nothing separates them except whether the aim trigger was already down when the press landed — which is why leaning a fraction early swings a knife instead.
| Lean state | Keyboard | Controller | What it costs on a pad |
|---|---|---|---|
| Lean while aiming | Q or E, at any time | Press the right stick, pushed toward the side you want | The same thumb is holding your aim, so the press and the aim share one input. |
| Lean without aiming | Q or E, at any time | Not available | Pressing the stick without the aim trigger down is melee, not lean. This is the shipped behaviour, not a mistake you are making. |
| Lean and turn at the same time | Separate finger, separate hand — free | Not really | Choosing the lean side is done by pushing the aiming stick, so the side you lean and the direction you look are the same control. |
| Switch lean side mid-peek | Release one key, press the other | Push the stick the other way and press again | Each switch is another stick press, and each press is another chance to get melee instead. |
Leaning without aiming is not harder on a controller — it does not exist. A keyboard player leans while walking down a hallway for free; a pad player pressing the same button there swings a knife. Worth separating from anything you might be doing wrong.
You choose the lean side by pushing the aiming stick toward it, so the direction you lean and the direction you look cannot be separated. On a keyboard those are different hands entirely, which is why PC peeks look the way they do.
Options › Controls has separate Hold and Toggle settings for lean, crouch, prone and aim. Toggle lean removes the chord entirely — you are no longer holding two opposed keys, you are pressing one — which is a genuine fix for a board that fails the bench above.
Read from the verified entry behind /controls/rainbow-six-siege/. These six are the ones that end up in a chord together.
| Action | Default key | In a chord with |
|---|---|---|
| Move | W / A / S / D | Swing right, lean left · Swing left, lean right · Crouch-swing left · Run-out, then lean · Gadget while strafing |
| Sprint | Left Shift | Run-out, then lean |
| Crouch | C | Crouch-swing left |
| Prone | Left Ctrl | Lean while going prone |
| Jump / vault | Space | Not part of a tested peek |
| Lean left / right | Q / E | Swing right, lean left · Swing left, lean right · Crouch-swing left · Lean while going prone · Run-out, then lean |
| Walk | Left Alt | Not part of a tested peek |
The bench above tests the chords Siege asks for. These test the hardware underneath them.
Q leans left and E leans right on keyboard, held by default. On a controller you press the right stick while aiming and push it toward the side you want — which matters, because pressing the same stick without the aim trigger down is melee, not lean.
Two different causes and they need different fixes. If it fails only in one direction, your keyboard is probably dropping a key: holding a strafe and the opposite lean together is a demand on the keyboard matrix, and cheaper boards silently discard one of them. The bench on this page tests exactly those chords and tells you which key never arrived. If it fails in both directions, check whether sprint is being held — sprinting cancels lean in this game by design.
Hold is the default and keeps the lean tied to your finger, which is what most players want. Toggle is worth a serious look for one specific reason: it removes the chord. You are no longer holding two opposed keys at once, you are pressing one — so if the peek bench on this page shows your keyboard dropping a key during a crouch-swing, toggle lean is a genuine fix that costs nothing.
Because they are the same input. Lean is the right stick pressed while aiming; melee is the right stick pressed. Nothing separates them except whether the aim trigger was already down when the press landed, so leaning a fraction early swings a knife. It is shipped behaviour rather than something you are doing wrong.
On keyboard yes — Q and E work at any time, walking down a hallway included. On a controller no: there is no input for it, because the button that would do it means melee when the aim trigger is up. This is one of the few genuine capability differences between the two platforms in this game rather than a difference in difficulty.
A keyboard can only report a limited number of simultaneous keys, and which combinations fail depends on how the board is wired rather than on how many keys you press. Siege finds those limits faster than other shooters because a normal peek holds a strafe, a lean, an aim and often a crouch at the same time. When the matrix hits its limit it does not warn you — the key simply never reaches the game.
No. Nothing in the browser can see the game. The bindings shown are the verified defaults from the in-game settings screen, and everything measured is your own keyboard as the browser receives it.
I answer from this site only — the 28 browser tests, the controls library for 46 games, the sensitivity converters and the two games. I can tell you which page to open, how a tool works and what its result means.
I will not guess. If something is not on the site, I will say so.
Answers come from this site's pages.